This week I had one of those conversations that anyone who looks after websites will recognise instantly.
A client’s site had started misbehaving. The contact form wasn’t sending emails, parts of the site felt unreliable, and from their point of view it all seemed to come out of nowhere.
Their response was completely fair:
“But I haven’t changed anything.”
And honestly, they were right. They hadn’t.
But the world around the website had.
This post isn’t a rant and it’s definitely not about pointing fingers. It’s about explaining, in plain English, why websites can and do break even when you haven’t touched them, and why updates aren’t optional extras, they’re basic maintenance.
Most people think of a website as something static. You build it, you launch it, and it should just sit there quietly doing its job. In reality, a website is a living thing. It’s closer to a car than a brochure.
You might not change the engine every week, but you still expect it to start in the morning. That only happens because someone, somewhere, is keeping things serviced and up to date. When that doesn’t happen, the car doesn’t slowly warn you, it just refuses to cooperate one day.
Websites behave the same way.
One of the biggest misunderstandings I see is the idea that “nothing has changed”. Even if you never log in, your website doesn’t exist in a bubble. It lives on a server owned by a hosting company, and those servers are constantly evolving.
Hosting providers upgrade infrastructure, improve security, retire old systems and move everyone forward. They have to. Leaving old software running indefinitely would be a security nightmare. Most of the time these changes are good news, faster and safer servers benefit everyone. The catch is that your website needs to be able to keep up.
This is where PHP usually enters the conversation, and I know the moment I mention it, eyes glaze over. Stick with me.
PHP is the language WordPress runs on. You can think of it as the engine under the bonnet. Older versions of PHP don’t just become unfashionable, they become unsupported and insecure. Eventually, hosting companies stop offering them altogether.
If a site is still relying on plugins or themes written for older PHP versions, things start to creak. Forms stop sending. Admin pages throw errors. Sometimes the whole site just falls over. From the outside, it feels random. From the inside, it’s entirely predictable.
You didn’t change anything. The engine did.
Plugins add another layer to the mix. A typical WordPress site isn’t one piece of software, it’s a collection of parts built by different developers, all moving at different speeds.
Some plugins are actively maintained. Some are updated occasionally. Some are quietly abandoned. When a site has a mix of updated and outdated plugins, running on an old PHP version, or suddenly forced onto a newer one, it’s only a matter of time before something disagrees with something else.
Contact forms are usually the first thing to show it.
They sit right at the intersection of PHP, email, JavaScript and sometimes third-party services. When something upstream changes, forms often stop working quietly, with no big error message to wave a flag. They just stop delivering messages. Which means enquiries can disappear without anyone noticing for far too long.
A phrase I hear a lot is, “But it was working before.”
Absolutely. It was.
So was your old phone.
So was your old laptop.
Until support ended and the world moved on.
Websites don’t usually break because someone did something wrong. They break because technology doesn’t stand still, and ignoring that reality eventually catches up with you.
Updates tend to make people nervous, and I get that. There’s a fear that clicking “update” will somehow wreck everything. Ironically, not updating is far more dangerous.
The trick isn’t avoiding updates, it’s doing them properly. In the right order. With backups in place. With an understanding of what’s connected to what. Randomly updating everything on a live site with no safety net is risky. Controlled, routine updates are just maintenance.
There’s a big difference.
When people hear “website maintenance”, they sometimes think it’s upselling or unnecessary admin. In reality, it’s about keeping the foundations solid so problems don’t appear at the worst possible time.
A well-maintained site doesn’t shout for attention. It just works. Forms send. Pages load. Emails arrive. And nobody has to deal with an urgent fix because something quietly broke weeks ago.
Doing nothing often feels like the safest option. It’s also the most expensive in the long run.
Missed enquiries, lost sales, emergency repairs and avoidable stress all tend to cost far more than a bit of ongoing care. Most website disasters aren’t sudden. They’re slow problems that were ignored until they became urgent.
So if you ever catch yourself saying, “But I haven’t changed anything”, you’re probably telling the truth.
Your server has changed.
PHP has changed.
Security standards have changed.
The internet has changed.
Your website just needs a bit of help keeping up.
A healthy website isn’t one that never changes. It’s one that changes quietly in the background so it never has to break loudly.
And if you’d rather not think about any of that, that’s fine too. That’s literally what I’m here for.
