/michael abella
← All writing

WordPress 7: what business websites should upgrade—and what to test first

A practical WordPress 7 upgrade plan covering staging, plugins, performance, security, and launch checks.

Why WordPress 7 matters

WordPress 7.0 arrived in May 2026 with new AI abilities, an updated admin experience, new blocks, and a broader developer toolbox. WordPress 7.0.2 is now the stable maintenance release, while 7.1 remains in beta. Production sites should use the stable release and test beta features away from live traffic.

The upgrade sequence

Start with a restorable backup and a staging copy that mirrors production. Update the runtime, theme, and plugins deliberately, then compare critical journeys before and after.

  • Confirm PHP and hosting compatibility.
  • Test forms, checkout, search, login, redirects, and scheduled tasks.
  • Review custom blocks with the people who publish content.
  • Measure mobile LCP, INP, and CLS before and after.
  • Check logs and analytics again after launch.

Remove old drag

Use the upgrade to audit duplicate plugins, abandoned integrations, oversized media, and fragile theme overrides. Fewer moving parts usually improve security, editor confidence, and speed more than another optimization plugin.

When to bring in a developer

Get help when the site generates leads or revenue, contains custom PHP, or cannot tolerate an uncertain rollback. The deliverable is not simply “WordPress updated”; it is a verified site with a recovery path.