Updates without fear: a release routine for client sites
Agencies often avoid updates because something might break. A practical routine for updating many WordPress sites safely, with backups, staging and auto-updates.
Every agency has a site it is afraid to update. Usually it is a large one, with a page builder, a shop and a few custom snippets nobody remembers writing. So updates wait, then wait some more, and eventually the site is running a plugin with a known hole in it.
Fear of updates is reasonable. A routine is what makes it go away.
Why waiting is the bigger risk
As we wrote in our piece on WordPress vulnerabilities, the overwhelming majority are found in plugins, and fixes usually arrive quickly. Attackers watch the same disclosures you do. The gap between a fix being published and automated attacks starting can be short, so a site that updates monthly is exposed for weeks after most fixes exist.
The routine
1. Backups that you have tested. The well-known 3-2-1 rule, three copies on two kinds of storage with one off site, comes from long-standing government guidance on data backups. For WordPress that usually means the host's daily backups plus an independent off-site copy. A backup you have never restored is a hope, not a backup. Test a restore every quarter.
2. Sort plugins into two groups.
- Safe to auto-update: small, well-maintained plugins that rarely affect layout, and every security release. WordPress has supported automatic plugin and theme updates since version 5.5.
- Update by hand: page builders, WooCommerce and its big extensions, anything with custom code built on top of it.
3. Use staging for the hand-updated group. Copy the live site to staging, update there, click through the pages that matter: home page, a product, the cart, the contact form, any page with a complex layout. Then repeat the update on live. Staging copies must not email real customers or appear in search results.
4. Update on a fixed day, early in the week, never on a Friday afternoon, and never right before a client's launch or sale.
5. Read the changelog for major versions. A jump from 7.x to 8.0 deserves two minutes of reading; a 7.4.1 to 7.4.2 security fix does not.
6. Keep a record. Which site, which plugins, which versions, who did it, what was checked. When something breaks next week, the log tells you where to look.
When an update does break something
- Roll back the single plugin, not the whole site, if you can.
- Report the problem to the plugin author with the versions involved.
- Set a reminder to try again. A rollback is a pause, not a decision.
Doing it across many sites
The routine is the same for five sites or fifty; the difference is tooling. Agencies need one view of which sites have pending updates, which have known vulnerabilities, and which have not been checked in weeks.
In Ironhelm
The vulnerability check installs security fixes automatically and warns about abandoned plugins. The staging guard detects staging and copied sites, keeps them out of Google and stops them emailing real customers. The activity log records every update with who did it, and the email reports tell clients what was updated without them logging in.
Sources
- CISA (US-CERT), Data Backup Options
- WordPress.org, Plugin and theme auto-updates
- Patchstack, State of WordPress Security in 2026
Ironhelm Suite is one WordPress plugin for security, speed, SEO and analytics. See plans or tour the features.