What Website Maintenance Actually Involves (And What It Costs)
"The site is finished" is where the real timeline starts. What maintenance covers, what happens when you skip it, and what a fair price looks like.
Websites are not furniture. They sit on software that updates, servers that change, browsers that ship new versions every six weeks, and a security landscape that moves daily. Maintenance is not an upsell — it is the difference between an asset and a liability with your logo on it.
What it actually covers
Monthly
- Core, plugin, theme, and dependency updates — applied on staging, then live.
- Verified off-site backups, and a restore test that proves they work.
- Uptime and error monitoring reviewed, not just installed.
- Broken links, 404s, and form submissions checked end to end.
- Security scan and a look at access logs.
Quarterly
- Performance audit against your budget — the checks in the common performance mistakes.
- Database cleanup: revisions, orphaned rows, expired transients.
- Image and asset review as content accumulates.
- Dependency audit for packages that are now unmaintained.
Annually
- Domain and SSL renewal, checked rather than assumed.
- Accessibility review — see why accessibility is not optional.
- Content audit: what is out of date, what should be merged, what should go.
- Major framework or platform upgrade planning.
What skipping it looks like
It is never gradual. It is a contact form that stopped sending three months ago and nobody noticed, or a plugin vulnerability that turns your site into a spam relay, or a checkout that breaks after a browser update. Recovery from any of those costs more than a year of maintenance, and the lost enquiries do not come back. The security half of this is covered in WordPress security.
Why platform choice changes the bill
A WordPress site with thirty plugins has thirty update paths and thirty possible breakages. A statically generated site with a handful of dependencies has a fraction of that surface — one of the practical arguments in static vs dynamic websites. The cheapest maintenance decision is made at build time, not at renewal time.
What a fair price looks like
Small brochure sites sit at the low end, content-heavy or e-commerce sites considerably higher — an online store carries payment flows, tax rules, and inventory integrations that all need watching. What matters more than the number is what is included: does it cover backups with tested restores, staging updates rather than live ones, actual monitoring, and a stated response time when something breaks? A cheap plan that only runs updates blindly is worse than none, because it creates a false sense of coverage.
Questions worth asking a provider
- Are updates applied on staging first, and who checks the site afterwards?
- Where are backups stored, how long are they kept, and when was the last restore test?
- What is the response time for a site being down, in writing?
- Do I get a report, and does it include what changed?
- Who owns the code, the domain, and the hosting account? (It should be you.)
The minimum if you handle it yourself
Automated off-site backups, uptime monitoring with an alert to a phone, a monthly calendar reminder to apply updates and click through your own key journeys, and a quarterly performance check. That is an hour a month and it prevents most of the disasters.
Not sure whether your site is actually being maintained or just hosted? Ask me to take a look.
