Skip to content

WordPress Updates: How to Run Them Without Breaking Your Site

A worker in a hard hat standing on scaffolding, repairing the upper facade of a city building.

Open the dashboard of a WordPress site nobody has tended in a while and it greets you with a number. Fourteen updates. Twenty-three. Sometimes a figure high enough that the owner has learned to look past it the way you look past a check engine light that has been on since spring.

There are two ways to handle that badge wrong, and they cost about the same.

The first is clicking “update all” on a Friday afternoon, because the number is annoying and the button is right there. The second is never clicking it, because the last time somebody did, the site went white and the afternoon disappeared into finding a developer.

I have been building WordPress sites since 2006 and taking over other people’s not long after that, and the second mistake is the one I find more often on an inherited install. It is also the more expensive one, which surprises people. A site that has skipped two years of updates is not sitting in a safe, frozen state. It has been drifting away from everything around it, quietly, the whole time.

Here is the procedure, and more importantly the reasoning behind the order.

Four different things hide behind one badge

“Updates” is a single number covering four categories with four very different risk profiles. Treating them as one pile is what makes update day feel like a coin flip.

WordPress core. Minor releases, the ones that go from 6.7.1 to 6.7.2, are security and maintenance fixes. They are tightly scoped and rarely break anything. Major releases, where the first or second number moves, occasionally change how the editor or the block system behaves. Minor core updates belong on automatic. Major ones deserve a look first.

Plugins. This is where the variance lives. Every plugin is a separate piece of software by a separate author with its own opinions about backward compatibility. A plugin that renders a single icon is almost risk free. A plugin that owns your forms, your checkout, your caching, or your page layout is not.

Your theme. If you are on a commercial theme, an update can shift layout and spacing. If you are on a custom theme that somebody edited directly instead of through a child theme, an update deletes that work. That is not a bug. The update replaces the files, and the edits were in the files.

PHP. The one almost nobody includes in the mental model, because it does not live in WordPress at all. It lives in your hosting account. Old PHP versions stop getting security fixes, and hosts eventually move you whether you are ready or not. Plugins that were abandoned years ago are usually the ones that cannot survive the jump.

Why waiting is the costly choice

The instinct behind skipping updates is reasonable. The site works. Changing something that works feels like the risk, and leaving it alone feels like the safe play.

The arithmetic runs the other way for three reasons.

Skipped updates compound. Updating a plugin across one version is a small change with a readable changelog. Updating it across fourteen versions is a different project, and the author stopped supporting the version you are on about a year ago.

Diagnosis gets harder, not easier. When you update three plugins and something breaks, you have three suspects. When you update twenty three at once because you finally got around to it, you have a mystery and no clean way back except a full restore.

And abandonment only shows up when you look. A plugin that has not seen a release in three years is not stable. It is unmaintained, and you will usually discover that on the day your host upgrades PHP and the plugin stops running.

The order of operations

This is the sequence I follow on client sites, and it is boring on purpose.

  1. Confirm you have a backup you have actually restored. Not a backup that exists. One somebody has put back at least once. If you have never tested yours, start there instead and come back to updates afterward.
  2. Work on a staging copy, not the live site. A staging copy is where update day stops being frightening, because the worst case is that you throw the copy away. If you do not have one, that is the first thing to set up.
  3. Write down what the site has to do. Three or four lines, in plain language, before you touch anything. The contact form submits and the message arrives in the inbox. Checkout completes with a test card. The booking widget loads and offers times. A member can log in. This list is how you will know afterward whether anything moved.
  4. Update in groups. Core minor first, on its own. Then the small, self-contained plugins in one batch. Then, one at a time, the ones that touch everything: forms, commerce, caching, security, and your page builder. One at a time is slower and it is the entire reason you will know what broke.
  5. Check after each group. Not a glance at the homepage. The list from step three.
  6. Promote to live, then run the list again. Staging and production differ in small ways: caching layers, payment keys in live mode, email routing. A pass on staging is strong evidence, not proof.

The ten minute check that catches most of it

After any update, on the live site, in this order.

Load the homepage while logged out, in a private window. A logged-in view hides caching problems and shows you an admin bar version of the site no visitor sees.

Submit the contact form and confirm the message lands in the inbox. The confirmation screen is not evidence. Form delivery is the single most common thing to break quietly after an update, because it depends on handoffs well outside WordPress.

Run one real transaction if you take money or bookings. Test mode if you can, a small live one you refund if you cannot.

Click every item in the main navigation, then open one interior page on a phone. Layout damage from a theme or builder update tends to show at small widths first.

Open one page carrying a slider, a map, a video embed, or a calendar. Third party embeds are the other reliable casualty.

Then look at your error log. A site can look perfect and be logging a fatal error on a page nobody visited yet.

Mistakes I keep finding

Updating the page builder and nothing else. Builders and their add-on kits ship in matched pairs. Moving one and not the other is how a layout that worked for two years suddenly stacks into a single column.

Direct edits to plugin or theme files. Somebody needed one small change in 2021 and made it in the file itself. Every update since has either erased that change or been avoided to protect it. Both outcomes are bad, and the fix is a child theme or a small custom plugin.

Automatic updates on everything. Excellent for core minor releases and security patches. A poor idea for the plugin that owns your checkout, where you want to be present and watching when it changes.

Trusting the badge. A cleared update count means the files were replaced. It says nothing at all about whether the site still works.

Keeping plugins you deactivated years ago. Deactivated plugins still sit on your server and still need patching. If you are not using it, delete it. Fewer moving parts is the cheapest reliability you can buy.

Where this fits

Updates are not a project. They are a routine, and the sites that stay boring are the ones where somebody owns that routine on a schedule. Care plans cover exactly this: updates run on staging first, backups verified rather than assumed, monitoring, and the unglamorous checks that keep a Tuesday from turning into an emergency. They are scoped and listed on the services page with pricing up front.

If you want to know where your own site stands before spending anything, send your host name and a screenshot of your plugins screen through the contact page and ask for an update review. We will tell you which of your plugins are still maintained, which ones will not survive the next PHP upgrade, and in what order they should be moved.

More insights

Fix Your Own Website, Up to a Point

November 19, 2026
A good deal of website work is genuinely yours to do. Here is what an owner can handle, the four signals that mean carrying on alone will cost more than stopping, and the one hour rule that keeps a small problem small....

What Is Running on Your Website, and What It Costs You

November 17, 2026
Most WordPress sites carry plugins and subscriptions nobody can account for. Here is the method we use to take inventory, price it, and remove what is dead without breaking the site....

AI Website Builder or Studio-Built Site: How to Choose

November 15, 2026
An AI website builder can produce a working site in minutes. What it can't do is make the decisions that determine whether the site works for your business. Where a generator is the right call, what it can't know, and five questions to decide....

We use cookies to understand how the site is used. Read our Privacy Policy.