The short answer
Most update breakage is a plugin or theme conflict, and most of it is recoverable without losing anything. The two rules: work methodically — one change at a time, testing after each — and don't keep pressing update hoping the next one fixes it. If the site earns money, you're locked out of wp-admin, or you've already tried two things without improvement, stop experimenting and get a proper diagnosis; every further click on a live business site raises the cost of the fix. Our WordPress help and repair service sees this exact situation every week, and asking about it is free.
What usually breaks
Updates fail in predictable ways. A plugin updated for a newer WordPress than you're running — or vice versa — throws errors. A theme fights a plugin that updated around it. Your hosting runs a PHP version the new code doesn't like, which became stricter after the update. The update itself was interrupted — a dropped connection mid-copy leaves half-old, half-new files. Or the permalinks configuration got mangled, so every page but the homepage 404s. Knowing which family your problem belongs to shortens the fix considerably, and the error message in front of you is the best clue you have.
Want a professional pair of eyes on your own site? Request a free website review — plain-English findings, no obligation.
First: read the actual error
'Broken' covers several distinct symptoms. A white screen with nothing on it is the classic white screen of death — our white screen guide walks through that specific one. A page saying the site is 'briefly unavailable for scheduled maintenance' means an update stalled and left its lock file behind — often the quickest fix of all. A 'critical error' message usually comes with an email from WordPress containing a special recovery link — check the admin inbox, including spam. Pages loading but looking scrambled points at the theme or its styling. Write down the exact wording of what you see; it changes the diagnosis.
Recovery mode: the built-in lifeline
Since WordPress 5.2, a fatal error triggers an email to the site admin address titled something like 'Your site is experiencing a technical issue'. That email contains a recovery-mode link that logs you into a protected admin area where the broken plugin or theme is paused — letting you deactivate the culprit without touching files. Two practical notes: the link expires, so use it promptly, and if the email never arrived it usually means the site's email was already unreliable — worth fixing properly afterwards, because it's the same email route your contact form probably uses.
A safe troubleshooting order
Work down this list, one step at a time, testing the site after each: 1) Note what was updated — the update screen or your email receipts tell you. 2) Clear any caching plugin and your browser cache; stale cache mimics breakage. 3) If you can reach admin normally or via recovery mode, deactivate the most recently updated plugins, starting with the prime suspect. 4) If you can't reach admin at all, renaming a plugin's folder via your host's file manager or FTP disables it — rename, test, rename back if innocent. 5) Switch temporarily to a default theme (Twenty Twenty-Four or similar) to rule the theme in or out. 6) Check your hosting PHP version against what WordPress currently recommends. 7) Re-save permalinks under Settings → Permalinks if inner pages 404.
When not to experiment further
There's a point where DIY troubleshooting turns into damage. Stop if the site is taking orders or bookings right now — every minute of experimenting is a minute of broken trading. Stop if customer data or accounts are involved. Stop if you have no recent backup, because the next wrong click could remove your safety net. Stop if you've made two changes and things aren't clearly improving — the odds now favour someone who can read the error logs directly. And stop if you find yourself editing files you don't understand, particularly functions.php or wp-config.php: a single mistyped character there takes a site from 'partially broken' to 'completely blank'.
Backups and rollbacks
If you have a backup from before the update, restoring it is a legitimate route — but treat it as buying time, not as the solution. The update that broke things still needs to happen eventually, because skipping updates indefinitely is how sites get hacked. The sensible sequence is: restore to get trading again, then re-apply updates one at a time with a fresh backup first, testing between each, so you learn exactly which component fights your site. Rolling back a single plugin to its previous version can also work short-term. Your host may offer one-click restores — check before assuming you're on your own, and keep a downloaded copy of any backup you care about.
Testing after the fix
'The homepage loads' is not 'fixed'. After any repair, check the pages that make you money: the contact or enquiry form — actually submit a test message and confirm it arrives — the checkout or booking flow if you have one, the login page, and the whole thing on a phone, not just a desktop. Then finish the job properly: apply the remaining updates one at a time, with a backup before you start, so next month's update day is boring instead of dramatic. Our guide to updating your own website without breaking it covers the safe routine in more detail.
Common mistakes that make it worse
Updating everything at once on a live site, late on a Friday, with no backup — the classic. Dismissing the PHP version notices WordPress has shown for months; they become errors after an update, not before. Using 'nulled' or pirated themes and plugins, which can't be updated safely and often arrive pre-infected. Editing theme files directly instead of using a child theme, so the next update overwrites your changes. And the quietest mistake: never testing the contact form, so the first person to discover it's broken is a customer who didn't get through.
When to call in help — and what it costs
If you're locked out, the site is trading, or the safe steps above haven't pinned it down, this is a routine rescue for someone who does it daily. Most single repairs are quoted from £95, depending on the cause and complexity. You approve a fixed written quote before any work begins, and the initial enquiry is free — tell us the symptoms, including what was updated and what the error says, and you'll get an honest assessment. Not sure how bad it is? Start with a free website check and we'll tell you plainly whether it's a ten-minute fix or something deeper.
Common questions
Should I turn off automatic updates? We wouldn't — the security risk of never updating outweighs the occasional breakage, and the safer answer is updates applied deliberately with a backup first, or handled for you through a maintenance plan. How do I know which plugin broke it? The error message or recovery-mode screen usually names it; otherwise deactivating the recently updated ones in turn finds the culprit quickly. Will I lose my content? Update conflicts almost never touch your content — pages, posts and images live in the database, which updates rarely damage. How quickly can it be fixed? Most single-plugin conflicts are quick once identified; the honest answer depends on what the investigation finds, and you'll get that assessment before any paid work.
Want this handled for you?
Get a free, plain-English review of your website — what's working, what isn't, and what's worth fixing first.
Get a Free Website ReviewRelated services: WordPress Development · Website Repairs