Skip to main content
All Articles
WordPress Maintenance · · 7 min read

What to Do When a WordPress Update Breaks Your Site: A Step by Step Recovery Guide

Stop and take a breath. First, do not run any more updates. Work out whether your whole site is down or just one page looks wrong. If you have a backup from before the update, restoring it is the fastest safe fix. No backup? You can still recover by turning plugins off from your hosting file manager.

What should you do in the first five minutes?

The most common mistake is clicking more buttons. Do not run the update again, do not delete anything, and do not install new plugins hoping they will fix it. Every extra change makes the real cause harder to find.

Instead, work out what kind of “broken” you are dealing with:

  • The whole site is down. Visitors see an error message or a blank white screen.
  • One page looks wrong. The site loads, but a layout is scrambled, a form is missing, or a section vanished.
  • You are locked out of the admin area. The front of the site looks fine, but you cannot log in, or the dashboard shows an error.

Write down exactly what you see, including the exact words of any error message. If you recently updated something, note which plugin, theme, or WordPress version it was. That short note will speed up everything that follows, whether you fix it yourself or hand it to someone else.

How do you restore your backup, step by step?

If you made a backup before updating, restoring it is the quickest way back to a working site. Here is the general order:

  1. Find your backup. Look in your hosting control panel, or in the backup plugin you use. Choose the backup from just before the update, not an older one.
  2. Restore both files and database. A half restore can leave your site in a worse state. Most backup tools have a single restore button that handles both.
  3. Wait for it to finish, then check your site. Open your homepage, one key page, and your contact form. Log in to the admin area to confirm that works too.
  4. Do not update again yet. Your site is back on the older, working versions. That is fine for a few days while you figure out which update caused the problem.

One warning for online stores: restoring a backup rolls your site back in time, so orders placed after the backup was taken may not show. If your store is busy, export your recent orders first if you still can, or ask your host for help before restoring.

What if you have no backup?

Take a breath. This is recoverable in most cases. A broken update usually means one plugin or your theme is crashing the site, and you can switch things off from outside WordPress, even when you cannot log in.

  1. Open your hosting control panel and find the file manager. Every host has one. It shows the files that make up your website.
  2. Go to the plugins folder. The path is usually wp-content, then plugins. You will see one folder per plugin.
  3. Rename the folder of the plugin you just updated. Change it to anything else, for example by adding “-off” to the end. WordPress cannot load a plugin it cannot find, so this safely deactivates it without deleting anything.
  4. Check your site. If it loads again, you have found your culprit. If not, rename the whole plugins folder to deactivate every plugin at once, then check again.
  5. If the site is still down, suspect the theme. Rename the folder of your active theme inside wp-content, then themes. If a standard default theme is installed, WordPress will fall back to it and your site should load, plain but working.

Renaming is reversible, which is why this method is safe. Once your site loads, you can rename folders back one at a time, checking after each, to confirm exactly which piece caused the crash.

How do you find the plugin or theme that caused the break?

Now work like a detective. Reactivate your plugins one at a time, and reload your site after each one. The moment the site breaks again, the last plugin you switched on is your problem.

Once you know which one it is, you have a few options:

  • Leave it deactivated for now, especially if it is not essential.
  • Check for a newer version in a few days. Developers often release a follow up fix quickly when an update causes trouble.
  • Contact the developer with your WordPress version, your PHP version, and the error message you wrote down.
  • Replace it with a well maintained alternative if the developer does not respond.

If hunting down the culprit feels beyond you, that is a normal point to bring in help. Our guide on how to hire a WordPress developer explains what to look for and what it should cost. And once your site is back, if it feels slower than it did before, work through these WordPress site slow fixes to check nothing else was damaged.

How do you stop this from happening again?

A broken update is usually not bad luck. It is a missing routine. Three habits prevent almost every repeat:

  1. Back up before every update round, without exception. The backup is the difference between a scare and a crisis.
  2. Update on a fixed schedule, in small batches. Small, regular updates clash far less often than twenty at once. Our WordPress maintenance services checklist shows the full routine.
  3. Treat major updates with respect. For big changes, like a new WooCommerce or page builder version, update one at a time and check the site after each. If your host offers a staging copy of your site, test major updates there first.

If you would rather not carry this risk yourself, a maintenance routine handles the backups, the updates, and the recovery for you. That is what our WordPress maintenance service is for.

Frequently Asked Questions

It can. A restore rolls the whole site back to the moment the backup was taken, so anything created after that point may be lost. For a store, export recent orders first if you can still reach them, or ask your host to help you protect them.

Use the file manager method above. Renaming the updated plugin’s folder from your hosting panel deactivates it without needing the WordPress login, and that fixes most lockouts.

Yes, but not immediately, and not all at once. Update everything except the problem plugin, one at a time, with a fresh backup first. Wait for the developer to release a fixed version of the plugin that broke.

Restoring a backup is often a matter of minutes once you find the right one. Hunting for a problem plugin by hand takes longer, especially on a site with many plugins, which is why the backup matters so much.

If your site is broken right now and you would rather not dig through file folders yourself, send me a message through the contact page. I will take a free look, tell you honestly what I find, and we can go from there.