Website Maintenance: What It Covers and Why It Matters

Websites are not finished; they are deployed. Everything after launch is maintenance, and the difference between sites that improve for years and sites that quietly rot is whether maintenance is a real service with real contents — or a monthly debit that merely hosts the rot. Here is what the honest version contains.

The non-negotiables

Updates. The platform, the framework, and every dependency ship security and compatibility fixes on their own schedule. Applied promptly, they are routine; ignored for a year, they become a migration project. Static-heavy architectures like ours shrink this surface dramatically — few moving parts, little to patch — but "fewer" is not "none," and the discipline of applying updates is the same either way.

Backups, tested. A backup that has never been restored is a hypothesis. Real maintenance keeps them on schedule, off-site, and periodically verified by restoring something from them. The day you need a backup is a very bad day to discover it was writing empty files.

Monitoring. Uptime checks that alert a human when the site is down, form-delivery checks that alert a human when enquiries silently stop, and certificate checks before the padlock expires in front of your customers. The failure modes are boring and predictable; catching them is simply a matter of looking.

The 404-and-redirect layer. Pages get renamed, campaigns get retired. Unmaintained sites accumulate broken links — found by visitors first and search engines second, at which point they cost ranking.

The compounding layer

Content edits. Prices change, services change, people change. The value of maintenance here is speed: small edits that ship in a day keep the site telling the truth, and a site that tells the truth converts.

Performance watch. New images get uploaded at original resolution; third-party scripts accrete. A quarterly performance pass keeps the speed the site shipped with — or catches the drift while it is still cheap to reverse.

Reporting. A short, honest monthly note: traffic, enquiries, what was changed, what was fixed. Maintenance without reporting is invisible by design, and invisible work has a way of becoming absent work.

How to tell real maintenance from hosting

The test question is simple: what did you do last month? A hosting bill answers "your site was online." Real maintenance answers with a list: updates applied, edits shipped, this form fixed, that backup verified. If the retainer cannot produce the list, you are paying for a server, not a service.

The second test: who answers when something breaks, and in what time? A maintenance agreement states response times in working hours. Anything vague here is the clause you will meet during your busiest sales week.

What maintenance costs, honestly

Priced as a fraction of the build — typically a modest monthly retainer against the original project cost — maintenance is the cheapest money a website owner spends, because it protects the expensive money already spent. The alternative is not saving the retainer; it is scheduling the rebuild for three years early, an event whose price is documented in the true cost of a cheap website.

When you do not need a retainer

Honesty cuts both ways: a small static site with content that changes twice a year can live on checklist discipline without a retainer — updates on a calendar you actually keep, backups verified quarterly, and a studio you can call when something needs eyes. We tell clients when they are in this category, because trust compounds better than retainers do.

For everything else, the question is not whether the site needs care — it does — but whether the care will be visible. Ask for the list.