I hear it from a lot of business owners. You build the website once, pay for it, and check it off in your head: done, I have a website, moving on. You treat it like a billboard by the road, you put up the banner and it just hangs there. Nobody has to check on it every week, nothing happens to it until the wind tears it down.
Except a website doesn't work that way. And most of the problems people end up bringing to me come straight from this misunderstanding. So let's spell out why a website is fundamentally different from a billboard, and what exactly breaks when you leave it for years without care.
A billboard hangs. A website lives in an environment that keeps changing
A billboard is static. You print it and you're done, the world around it can change however it likes, the banner stays the same. A website, on the other hand, is plugged into a living, constantly shifting environment, and that environment pushes on it from every side.
What keeps changing around a website
- Search engines Google keeps adjusting the rules for who gets shown. What worked three years ago may not be enough today.
- Browsers Updates several times a year can break a button or a page layout on an older site.
- Phones and screens New models have different dimensions, and an untouched site can render broken on them.
- Attackers Automated programs scan for sites with known holes. It is enough that the site is vulnerable.
So a website isn't a finished picture on the wall. It's more like a car: without regular servicing it ages, starts breaking down, and one day leaves you stranded. I went into this in more detail in the article on what website maintenance actually covers.
What breaks on a website when you leave it alone
Neglect doesn't show up right away. A site can keep looking fine for months, sometimes even years. But problems pile up quietly in the background, and when they finally surface, it usually hurts more than if they'd been handled as they came. Here are the most common ones.
Broken links (404 errors). A "404" is the message a visitor sees when they click a link or type an address that no longer exists on the site. You rename a page, delete an old product, change the menu structure, and links that used to work suddenly lead nowhere. For a customer it's a dead end. Fix the internal link. If a page was removed without a replacement, 404 is correct and does not itself harm other pages.
Outdated content and prices. The most embarrassing kind of error, because everyone sees it. Last year's opening hours, prices that no longer apply, a promotion that ended six months ago, the name of someone who left the company long ago. None of it takes the site down, but it chips away at customer trust: if this doesn't add up, what about the rest?
Security holes. This is the least visible and most dangerous category. An unupdated website is like a house with unlocked doors. Bots find it on their own, and a compromised site can start sending spam, redirecting visitors to fraudulent pages, or end up with its content encrypted. And once Google notices the compromise, it can flag the site as unsafe and stop showing it altogether.
Slow loading. Age alone does not slow a website down. Added images, scripts or hosting changes can affect performance. Measure after changes; see how to speed up your website.
An expired domain or certificate. Domains need renewal. TLS certificates can be free and renewed automatically, but renewal can fail. Expiry may cause downtime or a warning; see my website is down.
Worked example: The button stayed, its target disappeared
illustrative example
| Layer | Finding | Next step |
|---|---|---|
| Visitor | Clicks "Request servicing" | Gets an error page |
| Link | Still targets /old-contact | Find every occurrence |
| Correct destination | Now /contact | Fix link and old URL |
| Verification | Use the button again | Check loading and form |
A button’s appearance does not reveal whether the enquiry journey works.
Google Search Console: crawling and visibility
Google Search Console is a free Google service for crawling, indexing and search performance. It flags selected issues, not every website fault.
Here's what you can learn from it:
What you can learn in Search Console
- Indexing A page that isn't indexed can't show up in search results.
- Clicks and queries Which words people find you by and how many times they click through.
- Problems Selected indexing issues, Core Web Vitals and security warnings. The standalone mobile report was retired, so test layout on actual phones.
That last part is the most important and the most often overlooked. Google doesn't flag problems just as a curiosity.
What it means not to ignore those warnings
Search Console can send you an email or an alert along the lines of "we found a problem on your site." Plenty of people dismiss it as spam or tell themselves they'll look at it sometime later. That's a mistake, because those warnings have a real impact on whether customers can find you in search.
Not every notification is a fault or ranking loss. A deliberately removed URL may correctly return 404. Prioritise important pages with accidental blocks, server errors or security issues. Check the URL and intended behaviour before choosing a fix.
Put practically: Search Console is like the warning light on your dashboard. When it comes on, it's telling you something. You can tape over it and keep driving, but the fact that you can't see it doesn't mean the problem is gone. I've summarized the basic technical errors it flags in my technical SEO checklist.
What regular website maintenance actually does
Care can reduce risks and recovery time; it cannot guarantee zero outages. Regular website maintenance is nothing mysterious, it's four habits that together keep a site in shape:
Four habits of regular website maintenance
- Monitoring An automatic check that the site is up and isn't loading slowly. Alerts can reduce outage detection time.
- Updates Patching security holes in time, the cheapest insurance against getting hacked.
- Small fixes A broken form, a 404 error, an outdated price, swapping a photo.
- Measurement Search Console and traffic stats: what works and where a new problem appeared.
None of it is a one-off event. It's more like regularly turning a key in a lock, boring, quiet, but that's exactly why it works.
Worked example: A backup needs a recovery procedure
recovery worksheet
| Item | Record | Status |
|---|---|---|
| Backup file | web-2026-10-03.zip | Verify existence |
| Restore target | Isolated staging copy | Prepare |
| Restored content | Contact + latest article | Compare |
| Functional test | Test enquiry reaches inbox | Not performed |
This worksheet does not prove a successful restore; it shows what to record.
Honestly: not every website needs an expensive retainer
And now the important part that a salesperson usually won't tell you. Not every website needs an expensive monthly plan. If you have a simple few-page business card of a site that barely changes, you may well get by with a check a couple of times a year and renewing the domain and certificate on time.
What holds true without exception, though: every website needs at least minimal watching. The gap between "an expensive retainer" and "nothing at all" is enormous, and most companies needlessly sit at the zero end. Even the smallest site benefits from someone occasionally checking whether it's running, whether the domain has been renewed, and whether Search Console is flagging a problem.
It's not about paying for features you won't use. It's about the site not being left completely unsupervised.
Summary
A website needs an accountable maintainer and proportionate checks of pages, forms, domains, backups and content. Search Console helps with search visibility; it does not replace uptime monitoring or functional tests.
You don't have to pay for an expensive retainer right away (what retainers include and cost is in how much website management costs). But leaving a website completely unsupervised is like parking a car for ten years and expecting it to start. If you're not sure what state yours is in, take a look at regular website maintenance, or, if something's already on fire and you need one-off help, at express website help. I'm happy to just look at what Search Console is reporting first and tell you straight whether anything needs handling.