How long does it take to build a website?

Most business websites are live within 7-14 days. No waiting months like with a traditional agency.

How much does a business website cost?

Pricing is transparent and fixed. No surprise fees, no monthly retainers unless you want ongoing support. Get a free quote by getting in touch.

What is AI automation for businesses?

AI automation means using software to handle repetitive tasks automatically — things like following up with leads, sending emails, booking appointments, and onboarding new customers — so you can focus on running your business.

What is an AI voice agent?

An AI voice agent is a smart phone system that answers your calls automatically, day or night. It can take messages, book appointments, answer common questions, and capture customer details — so you never miss a lead even when you're busy.

What is AI integration?

AI integration means connecting automation, chatbots, and voice agents into the systems a business already runs on — its website, inbox, calendar, and CRM — so they work as one system instead of a bolt-on gadget that needs managing separately.

FAQ · 2026-04-12

Why your WordPress site keeps breaking after updates

If your WordPress site keeps breaking after updates, the issue is usually poor maintenance, plugin conflicts, or a fragile setup, not WordPress itself.

If your WordPress site keeps breaking after updates, the problem usually is not WordPress itself. It is a mix of neglected plugins, theme conflicts, outdated PHP, poor hosting setup, or a site that has been left without proper maintenance for too long. The fix is not to stop updating everything. The fix is to handle updates properly, test them, and keep the site in a state where one plugin change does not knock the whole thing over.

A lot of small businesses end up in the same cycle. The website gets built, it works fine for a while, then nobody touches it apart from the odd content change. Months go by. WordPress core moves on, plugins release updates, the server changes, forms start acting strangely, and then one day someone clicks update and the site falls over.

That is usually the moment I get the message.

Sometimes the issue is obvious. A plugin has not been updated in a year and no longer plays nicely with the current version of WordPress. Sometimes the theme is built in a messy way and depends on old code. Sometimes the hosting environment has been upgraded and the website was already fragile before that happened. Sometimes a contact form still appears on the page but has quietly stopped sending emails. That last one is especially bad, because the site looks fine while you are losing enquiries.

This is why ongoing WordPress support matters. Not because websites need constant drama, but because they need someone keeping an eye on the boring bits before they become expensive bits.

The business consequence is simple. When a WordPress site breaks, you do not just have a technical problem. You have a sales problem, a trust problem, and often an admin problem too.

If your homepage is down, people assume the business is inactive or careless. If your forms stop working, leads disappear without anyone knowing. If your booking plugin glitches, people give up and ring a competitor instead. If the site becomes slow after a bad plugin update, conversion drops even if traffic stays the same. Most businesses do not notice straight away either. They notice later, when enquiries have dried up or a customer points it out.

That is why "we will just update it when we remember" is not really a plan.

What proper WordPress support actually involves

Updates handled with a bit of sense. Not every site needs every update installed the second it appears, but leaving everything untouched for six months is asking for trouble. Core, plugins and themes need reviewing regularly. Critical security updates should be dealt with quickly. Bigger changes should be checked properly rather than fired through blindly.
Basic testing after updates. That means checking the pages that actually matter, not just seeing whether the homepage loads. I am talking about contact forms, booking forms, checkout steps, quote requests, mobile layouts, speed, and any integrations running in the background. If a plugin update breaks a lead form, that matters far more than whether the footer spacing looks slightly off.
Backups that exist and are usable. Plenty of businesses think they have backups because the host mentions them somewhere in the dashboard. Then something breaks and restoring it turns into a mess. A backup is only useful if it is recent, available, and part of an actual recovery plan.
Someone spotting problems early. That includes plugin conflicts, spam issues, SSL problems, email delivery issues, or warning signs that the site is getting bloated and slow. Most websites do not explode all at once. They get worse in small ways first.

This is also why I do not think every business needs a full rebuild when a WordPress site starts misbehaving. Quite often the better move is to clean up the setup, remove rubbish plugins, fix the update process, tighten the forms and email handling, and make the site reliable again. That is faster, cheaper, and less disruptive than rebuilding from scratch for the sake of it.

Of course, some sites are too far gone. If the theme is badly built, the plugin stack is a mess, and every change risks breaking something else, then a rebuild can be the sensible option. But that should be a decision based on the state of the site, not a default sales line.

What's usually behind it: plugin conflicts, theme conflicts, or hosting

Most breakages fall into one of three buckets. A plugin conflict, where two plugins (or a plugin and the theme) start fighting over the same function or hook, is the most common. A theme conflict shows up when the theme depends on old code that a core or PHP update no longer supports cleanly. And a hosting-side issue, usually a PHP version bump or a resource limit, breaks things that were already fragile and just hadn't been tested against the new environment yet. Working out which bucket you're in is most of the fix.

What to do if your site is broken right now

Deactivate plugins one at a time, starting with whichever was updated most recently, and check the site after each one. If deactivating everything clears the error, you're dealing with a plugin conflict and can narrow it down from there. If the site is still broken with every plugin off, look at the theme or the hosting environment next, PHP version mismatches are a common cause. Turning on WordPress debug mode briefly (`WP_DEBUG` in `wp-config.php`) will usually name the exact file causing the error, which saves a lot of guessing.

Why a staging site stops most of this happening in the first place

A staging site is a private copy of your website that isn't visible to the public, used to test updates before they touch the live site. Instead of clicking update and hoping, updates go to the staging copy first, get checked against the pages that actually matter, and only go live once they're confirmed safe. If something does break, it breaks on a copy nobody can see, not on the site your customers are looking at. Most hosts that take WordPress seriously offer staging as standard, so this usually isn't an extra cost, it's a step that gets skipped because nobody's set it up or nobody's using it consistently.

For most small businesses, what they actually need is a web guy who can keep the site healthy, fix issues when they appear, and improve things over time. Not just someone who built it three years ago and vanished.

That support can include WordPress updates, plugin checks, backup management, form testing, email troubleshooting, speed fixes, security basics, content edits, and small conversion improvements along the way. It is less about "maintenance" as a vague idea and more about making sure the website keeps doing its job.

If your WordPress site has broken after updates, or you are nervous to update it because that has happened before, that is usually a sign the site needs proper support rather than more guesswork. A website should not feel fragile.

If you want the full picture on what proper cover actually costs, how much does WordPress maintenance cost in the UK? breaks it down. If you want to know exactly what a retainer should include so this stops happening, what does a WordPress support retainer actually cover? is the next read.

If you want someone to sort out a WordPress site that keeps breaking, or keep it maintained properly month to month, have a look at monthly website support.

Frequently asked questions

Why does my WordPress site keep going down after an update?

Usually it's a plugin or theme that hasn't kept pace with WordPress core, a PHP version mismatch, or a hosting environment that changed underneath the site. It's rarely WordPress itself, and it's almost always fixable without a rebuild.

What should I check first if my site just broke after an update?

Start with the contact form, any booking or checkout flow, the mobile layout, and page speed. Then check the error log or turn on WordPress debug mode briefly to see which plugin or theme file is throwing the error.

Is it a plugin conflict, a theme problem, or a hosting issue?

Deactivate plugins one at a time (starting with anything updated recently) to isolate a plugin conflict. If deactivating everything doesn't fix it, suspect the theme or the hosting environment (a PHP version bump is a common culprit).

Do I need a full rebuild if my WordPress site keeps breaking?

Usually not. Most sites just need the update process cleaned up, rubbish plugins removed, and proper testing put in place after each update. A rebuild only makes sense if the theme is badly built or the plugin stack is genuinely beyond saving.

Topics: Web Development, Website Tips, Guide

By Lee Day · leeday.uk · UK-wide support

Get in touch