What does website maintenance actually involve

Website maintenance covers security updates, backups, software and platform updates, performance and uptime monitoring, fixing things that break, and small content changes. It costs roughly nothing to a few hundred a year for a builder site, and a few thousand a year for a custom build. The alternative to maintenance is not free. It is a larger, more painful bill later, when the neglected site finally fails or has to be rebuilt.

Most people think of a website as something you build once. It is closer to a car. It works fine for a while, then quietly needs attention, and the cost of ignoring that attention compounds. Here is what maintenance actually involves, what it costs, and why the businesses that skip it usually pay more in the end.

Security updates and patches

Every website runs on software, and software has vulnerabilities that are discovered continuously. Platforms, plugins, and dependencies release security patches, and an unpatched site is an open door. This matters most on self-hosted platforms like WordPress, where an out-of-date plugin is the most common way sites get hacked. On managed platforms like Framer or Squarespace, much of this happens for you, which is part of what you pay for.

Backups

If something goes wrong, a recent backup is the difference between a bad afternoon and a catastrophe. Maintenance means backups happen automatically and, crucially, that someone has checked they can actually be restored. An untested backup is not a backup. Managed platforms handle this. Self-hosted sites need it set up deliberately.

Software and platform updates

Beyond security, the software a site runs on evolves. Frameworks release new versions, dependencies change, platforms deprecate old features. On a custom build especially, keeping the underlying technology current prevents the site from slowly rotting into something no developer wants to touch. Skip this for long enough and a routine change becomes a rebuild.

Performance and uptime monitoring

Sites slow down over time as content, images, and third-party scripts accumulate. Maintenance means watching performance and keeping it fast, and being alerted if the site goes down rather than finding out from a customer. Uptime monitoring is cheap and the peace of mind is worth more than it costs.

Fixing things that break

Things break without anyone touching them. A payment integration changes its API, a form stops sending, a browser update breaks a layout, an embedded tool changes. Maintenance is having someone who notices and fixes these before they cost you enquiries. On an unmaintained site, these breakages can sit undiscovered for months.

Content updates and small changes

The ongoing small stuff: updating copy, swapping images, adding a new team member, publishing a post, changing prices. Some of this you can do yourself if the site was built with a good CMS. Some needs a developer. Either way it is part of keeping a site alive rather than frozen at launch.

What it costs by type of site

• Builder or template site (Squarespace, Framer, Wix): the platform handles security, backups, and updates. Your maintenance is mostly the subscription plus your own time. Call it a few hundred a year.
• Webflow: similar platform coverage, plus occasional help with changes and new pages. Roughly one to three thousand a year if you use a studio for updates.
• Custom build (Next.js and similar): you own the maintenance. Dependency updates, security, hosting, monitoring, and fixes. Realistically three to fifteen thousand a year depending on complexity. This is the ongoing cost people forget when they choose custom.

DIY, retainer, or ad-hoc

Three ways to cover it. Do it yourself, which works for a builder site and simple changes but not for a custom build. A monthly retainer with a studio or developer, which is predictable and means someone is watching. Or ad-hoc, calling someone when something breaks, which is cheaper until the thing that breaks is urgent and expensive. For anything business-critical, a retainer is usually the honest answer.

The false economy of skipping it

Skipping maintenance feels like saving money because the cost of doing it is visible and the cost of not doing it is hidden until it arrives all at once. A hacked site, a week of downtime, a security breach that exposes customer data, or a platform so out of date that a small change requires a full rebuild. The businesses that treat a website as build-once-and-forget are the ones that end up paying for an expensive emergency, then paying again for the rebuild. Maintenance is the cheaper path, it just does not feel like it until the day it saves you.

See also: When should you redesign your website, The hidden cost of custom build, Should you self-host or use a managed service.