Nothing broke. Everything just moved
A website goes live and, for about six months, behaves. Then the contact form stops delivering and nobody notices for three weeks. Or a plugin update fails at 2 am and the site serves a blank page. Or the certificate expires and every visitor gets a full-screen browser warning about security.
None of that is a bug in what was built. It is the ordinary consequence of running software in a world that keeps changing around it — browsers, gateways, frameworks, mail providers, all moving on their own schedules.
Maintenance is the work of noticing.
What breaks, roughly in order
- Forms, silently. The most common failure and the most expensive, because there is no error message. A mail provider tightens its rules, an anti-spam rule gets stricter, a third-party form endpoint changes, and enquiries simply stop arriving. Nobody complains, because the people who complain are the ones who never reached you.
- Certificates and renewals. SSL, the domain itself, API keys with an expiry, gateway credentials. Every one of them is a diary entry that somebody has to own.
- Dependencies. Plugins and libraries go unmaintained, or update in a way that breaks something subtle. This is where "we will update it when there is a problem" fails, because by then the jump is several versions wide and updating is a project.
- Content decay. A team member who left, a service you no longer offer, a price from two years ago, a broken link to a partner who redesigned their site. Cheap to fix, embarrassing to leave.
- Performance drift. Nobody makes a site slow deliberately. It happens one uncompressed image and one extra tracking script at a time.
- Search visibility. Pages that quietly return errors, a sitemap that lists URLs that no longer exist, redirects pointing at pages that have since moved. Search engines notice long before you do, and they respond by crawling less.
The one that costs real money
Security patching, and it is worth being blunt about the shape of the risk.
Small business websites are almost never targeted deliberately. They are found by automated scanners that check thousands of sites for one known vulnerability in one popular plugin. The fix was published months earlier. The site was compromised because nobody applied it.
The clean-up costs more than years of maintenance, and if customer data was involved it costs more again.
What website maintenance services should include
A quote should name four things, and their absence is the answer.
- A response time, in writing. "We will look at it" is not a commitment. A stated window for an outage, and a longer one for minor issues, is.
- What counts as included work. Most contracts include small content edits up to some monthly allowance, and quote separately for new features. That is reasonable. What is not reasonable is a contract where the boundary is undefined, because every request then becomes a negotiation.
- Who holds the keys. Domain registrar, hosting account, code repository, DNS. These should be in your company's name, with your agency holding access — not the reverse. This is the single most common way a business ends up hostage to a vendor it has outgrown.
- Whether monitoring exists at all. If the first line of the contract is that you should report problems, you are the monitoring.
What you can reasonably do yourselves
Content updates. Adding a team member, publishing a post, changing an address, replacing a photograph. If your site needs a developer for these, that is a build problem, not a maintenance one, and worth raising.
Also the weekly walk-through set out in the steps at the end of this post. Submitting your own contact form once a week is thirty seconds and catches the single most costly failure on the list.
What genuinely needs someone technical
Anything that can take the site down: dependency and platform updates, server changes, DNS. Restoring a backup, which is a stressful thing to attempt for the first time in an emergency. Payment or login changes, where an error is not cosmetic. And the periodic look at logs and Search Console, which needs someone who knows what normal looks like — a habit that overlaps with testing on a small team.
What to do next
Take the six steps below and ask, for each one, who does it in your business today. If the answer to three or more is nobody, your website is running unattended, and the failure will be discovered by a customer.
We take on maintenance for sites we did not build, and we will tell you first if the honest answer is that you need an hour a month rather than a contract. Send us the site. More on maintenance and support, and on keeping the hosting bill sane.



