Oxyforge
On This Page
  1. Is It Safe To Bulk Update WordPress Sites?
  2. What Should Never Go In A Bulk Run?
  3. Should You Update By Plugin Or By Site?
  4. What Order Should The Sites Go In?
  5. What Does A Real Bulk Run Look Like?
  6. How Do You Bulk Update From The Command Line?
  7. What Do You Do When A Plugin Refuses To Update?
  8. Where Does WP Manager Fit?
  9. What To Do Next
  10. FAQ

How To Bulk Update WordPress Sites Without Breaking One

How To Bulk Update WordPress Sites Without Breaking One

One site with nine updates waiting is a ten-minute job you keep putting off. Fifteen sites with nine updates each is 135 updates, and at that point most people do one of two things. They press Update All everywhere and hope, or they stop looking.

Both are how sites get broken. The first breaks them on the day. The second breaks them six months later, when a plugin with a known hole is still on the version that has it.

You can bulk update WordPress sites without gambling, and you don’t need a developer to do it. You need four conditions true of every site in the run, a short list of things that never go in it, and an order of work that finds a bad update on one site instead of fifteen.

That’s what this guide sets out, for any tool or none. The weekly routine it fits into is in our guide to managing multiple WordPress sites.

Key Takeaways

  • A bulk update is safe when each site is backed up first, checked afterwards, restored if it fails, and one failure doesn’t stop or hide the rest.
  • Major WordPress versions, major page builder and shop versions, and anything on a live checkout stay out of the bulk run.
  • Update by plugin, not by site. One change across many sites is one thing to verify.
  • Run one or two low-risk sites first, look at them, then the rest.
  • A premium plugin that refuses to update usually has a lapsed licence. Retrying won’t fix it.

Is It Safe To Bulk Update WordPress Sites?

Yes, when four conditions hold for every site in the run. If any one is missing, you aren’t doing a bulk update. You’re doing fifteen unprotected updates quickly.

  1. Each site has its own fresh backup. Taken minutes before the update, not last month.
  2. Each site is checked afterwards. Something fetches the site and confirms it still answers properly.
  3. A site that fails is put back. By the tool, or by you with a restore you’ve done before.
  4. One failure is contained and reported. A plugin that refuses on one site shouldn’t stop the other fourteen, or pass silently.

Most management tools have a mode that does this. On their own sites on 13 November 2026, ManageWP described its Safe Updates (a restore point first, an automatic roll back on an error) as part of its premium Backup add-on, and WP Umbrella listed bulk updates “with built-in checks and automatic rollback” in its per-site price.

If your tool offers a plain bulk update and a safe one, use the safe one. The plain one saves a minute per site and costs a morning when it goes wrong.

What Should Never Go In A Bulk Run?

Anything where “the site still answers” isn’t enough proof that it still works. A bulk run checks that pages load. It can’t check that a booking goes through.

  • Major WordPress versions. They change the editor, the bundled libraries and sometimes what a theme relies on. Do them on a staging copy, one site at a time.
  • Major versions of a page builder or a shop plugin. These change the data they store. A move from 3.x to 4.0 is a different kind of update from 3.4 to 3.5.
  • Anything on a live checkout or booking flow during trading hours. Update those when the business is closed, and place a test order afterwards.
  • Sites that are already far behind. Forty updates waiting needs bringing forward in stages.
  • Sites with custom code tied to a plugin. Those get updated by hand.

Minor WordPress versions are the opposite case. They carry fixes and security patches and belong in the weekly run. On most sites WordPress installs them by itself anyway, and WordPress’s own guide to automatic updates says installs made since version 5.6 take major versions automatically too. Check each site’s setting before you assume a major jump will wait.

Write down which sites and plugins are held out, and why.

Should You Update By Plugin Or By Site?

By plugin. Take one plugin that’s out of date on many sites, update it everywhere it’s installed, then move to the next.

By pluginBy siteEverything, everywhere
What changesOne plugin on many sitesEvery waiting update on one siteEvery update on every site
If something breaksYou know which update did itYou know the site, not the causeYou know neither
Reading the changelogOnceOnce per pluginNot realistic
Best forThe weekly runCatching up one neglected siteNothing

The reason is diagnosis. When a form plugin goes from 5.8 to 5.9 on eleven sites and one breaks, you know that version clashes with something on that site. When eleven sites take nine updates each and one breaks, you know nothing.

A good tool lists waiting updates this way: one row per plugin, with the number of sites.

What Order Should The Sites Go In?

What Order Should The Sites Go In? - Oxyforge

One or two low-risk sites first, then everybody else. Engineers call the first one a canary, after the birds miners once carried underground. The order inside a single site, with staging, is in how to run WordPress plugin updates safely.

  1. Pick the canary. A simple site with no shop and a forgiving owner. Your own site is a good one.
  2. Update the plugin on the canary only, with a backup first.
  3. Look at it properly. Home page, one inner page, the contact form, the admin login.
  4. Run the rest in batches of ten or so, and read each result before starting the next.
  5. Spot-check two or three sites per batch. The tool confirmed they answer. You’re confirming they look right.

Look signed in, or ask your host how to see an uncached page. A page cache will happily show you last night’s working copy of a page that’s now broken.

If a site shows “Briefly unavailable for scheduled maintenance. Check back in a minute.” after a run, an update was cut off part-way. WordPress puts that notice up while it updates, using a .maintenance file in the site’s main folder, and ignores the file once it’s ten minutes old. If the notice outlasts that, delete the file over SFTP and find which update didn’t finish.

What Does A Real Bulk Run Look Like?

Say you’re a freelance developer with twelve small-business sites. The list shows a form plugin out of date on nine, an SEO plugin on all twelve, a gallery plugin on four, and a major page builder version on five. The minutes are illustrative.

  1. Read the list, three minutes. The page builder’s major version comes out of today’s run and onto next week’s staging list.
  2. Read two changelogs, four minutes. The form plugin fixes a security issue, so it goes first.
  3. Canary, five minutes. Update the form plugin on your own site. Send yourself a test message. It arrives.
  4. The other eight sites, five minutes. Tick them, update, read the result: eight succeeded.
  5. Spot-check, four minutes. Open two of the eight signed in and submit one test form.
  6. The SEO plugin and the gallery, ten minutes. One gallery site reports that the plugin refused to update. The other three are done.
  7. Write it down, three minutes. A note to the client whose gallery licence has lapsed, and a line in your log.

About half an hour for roughly twenty-five updates, with a restore point behind every one. Nobody pressed Update All.

How Do You Bulk Update From The Command Line?

With WP-CLI, if you have SSH access and are comfortable in a terminal. It gives you the mechanics. The safety is yours to add.

  • wp plugin list --update=available shows what’s waiting on a site.
  • wp plugin update contact-form-7 updates one plugin by its folder name.
  • wp core update --minor applies minor WordPress releases only.

WP-CLI can group your sites as aliases so one command runs on all of them, but it takes no backup, checks nothing and restores nothing. So run wp db export and copy the plugin’s folder before each update, then fetch the home page after it.

What Do You Do When A Plugin Refuses To Update?

Stop retrying and find out why, because it’s nearly always a licence.

A premium plugin checks its licence before it hands over an update. If the licence has lapsed, or the key was never entered on that site, WordPress may still show the new version with “Automatic update is unavailable for this plugin”, or the update fails with “Update package not available.” The site keeps working on the old version, so nobody notices.

That matters because the refused update is often the one that closes a security hole. Our guide to reading WordPress plugin vulnerabilities shows how to tell.

  1. Check who holds the licence. Often it’s the developer who built the site, on their own account.
  2. Tell the client plainly that the plugin can’t be updated until it’s renewed, and whether a security fix is waiting.
  3. Renew, or replace it with a plugin that’s maintained.
  4. Don’t leave it on the list as noise. A refusal you’ve seen ten weeks running is one you’ve stopped seeing.

Where Does WP Manager Fit?

WP Manager, in the Oxyforge members area, is built around the four conditions above. Its Safe Update backs a site up first, unless it has a backup from the last hour, and puts that backup back if the site stops answering. Plain Update skips the backup and the revert. Either way, a refusing plugin is reported and the rest carry on. Major WordPress versions are never part of a bulk update. A Hold button keeps one plugin out of every update on a site, automatic ones included.

The limit is plain: it only covers sites hosted on Oxyforge. If your sites are spread across hosts, a connector tool such as ManageWP or MainWP fits better. Our comparison of WordPress management tools sets them side by side.

What To Do Next

  1. Check your tool for the four conditions: backup first, check after, restore on failure, failures reported.
  2. Write the held-out list: major versions, checkout plugins, sites with custom code.
  3. Pick your canary site and a day of the week.
  4. Run this week’s updates by plugin, security fixes first.
  5. Chase every refusal to a named person and a date.
  6. If your sites share a host, see whether it does this without a separate tool. WP Manager is free on every plan on the Oxyforge pricing page.

FAQ

Can I update all my WordPress sites at once?

Yes, with a management tool or WP-CLI, as long as every site is backed up first, checked afterwards and restored if it fails. Start with one or two low-risk sites, then run the rest. Keep major WordPress versions and shop checkouts out of the run.

Should I update by plugin or by site?

By plugin, for the weekly run. One plugin across every site that has it is a single change, so if something breaks you know the cause. Update by site only when one site has fallen far behind.

What happens if a bulk update breaks one site?

With a proper tool, that site is restored from the backup taken just before the update and the others aren’t affected. Without one, restore last night’s backup or rename the plugin’s folder over SFTP so WordPress switches it off. Then find out why before you try again.

Why does a plugin refuse to update on some sites?

Usually because it’s a premium plugin whose licence has lapsed or was never entered on that site. Retrying won’t help. Renew the licence, enter the key or replace the plugin, and treat it as urgent if the update fixes a security hole.

Should major WordPress versions be part of a bulk update?

No. A major version belongs on a staging copy, one site at a time, with somebody clicking through afterwards. Minor versions are fine when you bulk update WordPress sites, with a backup first.