WordPress Site Broke After an Update? A Safe Order of Checks
If your WordPress site broke after an update, you will probably have seen something like this: a few seconds after clicking “Update”, the site shows a white screen, a “critical error” message, a broken layout or a form that no longer sends. It is stressful, especially if the website is how customers find and contact you. The good news is that most update problems are recoverable if you stay calm and work in a sensible order. The bad news is that several common instincts, such as updating everything again or deleting plugins at random, can make recovery harder.
This guide explains why a WordPress site can break after an update, the safest order of checks, and where the line sits between a job you can do yourself and one that needs a developer.
Why a WordPress site broke after an update
A WordPress site is a combination of WordPress itself, a theme and usually several plugins, often written by different people. An update to one part can stop working with another. Typical reasons include:
- A plugin or theme update that is not compatible with the version of PHP your hosting runs.
- Two plugins that rely on the same feature and now conflict.
- A theme or plugin that is no longer maintained and does not work with newer WordPress versions.
- An update that was interrupted halfway, leaving files in an inconsistent state.
- Custom changes made directly inside a theme or plugin, which an update then overwrites.
Step 0: stop and do not make it worse
Resist the urge to run more updates, reinstall everything or restore a very old backup without thinking. First, write down what happened:
- What exactly did you update, and roughly when?
- What do you see now: a white page, an error message, a broken layout or a single feature that fails?
- Is it the whole site, only the dashboard, or one page?
Backups come first. WordPress’s own troubleshooting documentation says that before upgrades, both the files and the database should be backed up. If you do not have a backup from before the update, ask your host whether they keep one, and take a copy of the current state before changing anything so you can always go back.
Step 1: check your email for the recovery link
Since WordPress 5.2, a fatal error can trigger a built-in recovery mode. WordPress emails the site’s administrator address with a secret link. According to the WordPress core announcement, following that link places a cookie on your browser and pauses the plugin or theme that caused the fatal error, for you only, so you can reach the dashboard. From there you can deactivate the faulty plugin, fix it if you are able, or contact its author with the error details.
Check the spam folder as well, and remember the email goes to the address set as the administrator email, which may be an old one.
Step 2: work out whether it is one plugin, the theme or something else
| Symptom | Common suspect | Safe first step |
|---|---|---|
| White screen or “critical error” after updating a plugin | That plugin, or a conflict with another | Use the recovery email link, or pause that plugin |
| Layout looks broken, styles missing | Theme update, caching, a page builder plugin | Clear the cache, then check whether the theme and builder versions match |
| A form stopped sending | Form plugin update, or email delivery settings | Send a test message and check spam; review recent plugin changes |
| Only the dashboard fails | A plugin that runs in the admin area | Recovery link, or ask the host for help |
| Everything broke right after changing PHP version | An older plugin or theme not supporting that PHP version | Ask your host to switch the version back temporarily |
Step 3: what you can safely try yourself
- Clear every cache. That means your browser, any caching plugin and your host’s cache. Old cached files can make a working site look broken.
- Look at what updated. Check the plugin and theme list, and any update log your host or a maintenance tool provides.
- Restore from the backup you took before the update, if you have one and the site is badly broken. A restore replaces changes made since the backup, such as new orders or form entries, so check what you would lose first.
- Update one thing at a time in future, and check the site after each one.
What needs more care
The official troubleshooting documentation describes deactivating plugins by renaming the plugins folder through your host’s file manager, or by editing a value in the database. Both work, and both are easy to get wrong. Renaming the folder switches off every plugin at once, which is a blunt step, and editing database values by hand can leave a site unreachable if a character is wrong. If you are not comfortable with either, it is reasonable to stop here.
Debugging is another area to be careful with. WordPress’s debugging documentation explains that WP_DEBUG_LOG saves errors to a debug.log file and that WP_DEBUG_DISPLAY controls whether errors appear on the page, and it states that these tools are meant for local testing and staging, not for live sites. Turning on error display on a live website can show visitors technical details they should not see. Reading the error log is often the quickest way to find the real cause, but it is best done on a staging copy or by someone who will switch it off again afterwards.
How to update more safely next time
- Take a backup first, and check that you know how to restore it.
- Use a staging copy for major updates, new plugins and PHP version changes, when your hosting offers one.
- Update in small batches. One plugin at a time makes the cause obvious if something fails.
- Check the important functions afterwards: the contact form, any booking or checkout flow, and the main pages on a phone.
- Remove what you no longer use. Every plugin you keep is something that can conflict or become outdated.
- Keep an eye on abandoned plugins. If a plugin has not been updated for a long time and the site depends on it, plan a replacement before it fails.
When to get help
Bring in a developer if the site is down and you cannot restore it, if you do not have a usable backup, if the problem affects bookings, payments or enquiries, or if you have already tried the recovery link and it did not help. Be wary of anyone who promises a fixed repair time before looking at the site. The cause decides the work involved, and an honest answer needs a look at the error first.
If something on your WordPress site has stopped working, such as a plugin conflict, a layout that shifted after an update, a form that does not send or a critical error, I can track down the cause and fix it, whoever built the site. I will explain what I plan to change before I change it. If you would also like one regular point of contact for updates and small changes, that can be agreed too.
If the site was also slow before the update, the guide to finding the cause of a slow WordPress website may help you separate the two problems.