How to update WordPress plugins safely across many sites
Michal
Author
Updating one WordPress site is easy: click Update, reload the homepage, done. Updating sixty is a different job. The same plugin behaves differently on every site because every site has a different theme, a different PHP version and a different set of other plugins, and the one that breaks is always the one you did not check.
This is the process we settled on after breaking enough client sites to want a process. It is boring on purpose. Every update follows the same four steps, the order of updates is decided by risk rather than by the order they appear in the list, and nothing goes to the whole fleet before it has gone to one site.
Why plugin updates break sites
It helps to know what you are protecting against, because the failures fall into a handful of patterns.
- Major versions. A jump from 3.x to 4.x usually means changed hooks, removed functions or a new settings format. The changelog will say "breaking changes" somewhere near the top.
- Template overrides. WooCommerce, Elementor, form plugins: anything whose templates themes commonly copy and modify. The plugin updates its template, the theme's old copy stays, and the two drift apart until checkout stops working.
- PHP version. Plugins raise their minimum PHP version in minor releases. On a site still on PHP 7.4, the update installs and then fatals on the first request.
- Database migrations. Some updates alter tables on first load. If the migration times out on a big site, the plugin can end up half-upgraded.
- Plugin pairs. A core plugin and its add-ons (WooCommerce and its payment gateways, ACF and its extensions) need updating together, or in the right order.
The four steps
1. Snapshot
Before anything changes, take a copy of the plugin directory and a database dump. One snapshot per site per batch is enough; you do not need one per plugin. Store it off the web server if you can, and keep it until the batch has been verified. A snapshot that lives in wp-content/upgrade is gone the moment the next update runs.
2. Update
Apply the update the way WordPress does it, through its own upgrader, so hooks fire and the plugin's own upgrade routine runs. Direct file replacement over SFTP skips those routines and is the source of a surprising number of "it updated but nothing works" tickets.
3. Verify
This is the step most people skip, and it is the one that matters. Two checks, both automated:
- Visual. Screenshot two or three key pages before the update and the same pages after, and compare them pixel by pixel. The homepage, one content page and, on a shop, the checkout. A threshold of a few percent changed pixels catches a broken layout while ignoring a rotating banner.
- Functional. Does the site return 200 on the homepage, with no PHP fatal in the log, and does a form submit? For a shop, does add-to-cart still work? These take seconds and catch the failures a screenshot cannot.
4. Roll back, automatically
If verification fails, put the snapshot back without waiting for a human. The person reviewing the batch in the morning should see "updated, verified, failed check, rolled back, here are the two screenshots" rather than a client email. A rollback that needs someone to log in and do it is a rollback that happens after the client noticed.
Decide the order by risk
Not every update deserves the same caution, and treating them all the same is how teams end up with a backlog of two hundred pending updates. Score each one, then handle each score differently.
- Security fixes go first, today, on every affected site. The risk of the update is almost always lower than the risk of the vulnerability.
- Patch releases (1.2.3 to 1.2.4) with no database or template changes are low risk. These are the ones to automate: snapshot, update, verify, done, in a maintenance window, no human involved.
- Minor releases with new features go in the weekly batch, after a look at the changelog.
- Major releases wait. Update one site first, ideally a low-traffic one on the same theme as the others, leave it a day, then roll out.
Reading the changelog and the code diff for every update is the right thing to do and nobody has time for it. This is one of the few places where an AI summary earns its keep: given the changelog and the diff between the two versions, it can tell you "this release changes the checkout template and adds a database table" in a sentence, which is exactly what you need to pick the risk level.
Roll out to the fleet in rings
Even a low-risk update should not hit sixty sites in the same minute. Run updates in batches with a concurrency limit, five sites at a time is plenty, so a bad update is caught by the verification on the first ring before it reaches the rest. Group the batch by client, so if something does need a human, the explanation goes to one client rather than ten.
Maintenance windows matter here too. Overnight for the site's own timezone, outside the client's trading hours, and never on a Friday afternoon. The window is also when the host is least busy, which makes timeouts on big sites less likely.
When an update fails
Failures cluster into categories, and each has a different fix:
- Permission denied. The web server cannot write to the plugin directory. Fix the ownership; nothing else will work until you do.
- Disk space. The host is full. Usually a log file or a forgotten backup in the wrong place.
- Download failed. The site cannot reach WordPress.org, often because of an outbound firewall at the host.
- Version unchanged. The update ran but the version did not change, which usually means a cached copy of the old plugin or a must-use plugin pinning it.
- Verification failed. The update worked and the site broke. This is the one the snapshot is for.
Record every outcome, including the rollbacks. The history is what tells you that a particular plugin breaks a particular theme every other release, and it is the list of work done that goes into the client's monthly report.
The checklist
- Security updates first, everywhere, today.
- Snapshot plugin files and the database before each batch.
- Update through the WordPress upgrader, never by copying files.
- Verify with screenshots and a functional check, automatically.
- Roll back automatically when verification fails.
- Automate patch releases; review minors; stage majors on one site first.
- Roll out in rings of about five sites inside a maintenance window.
- Keep the history, and put it in the client report.
If you would rather not build this yourself, it is what the safe updates feature in WP Admin Online does: one snapshot per site per batch, visual and functional verification, automatic rollback, AI risk notes per update, auto-apply rules for low-risk releases, and bulk runs with a concurrency limit. The free plan shows every pending update across unlimited sites, flags the ones with a known vulnerability and runs quick bulk updates; the paid plans add safe updates with snapshots and rollback, AI risk notes and auto-apply rules.