WordPress 7.0 for Agencies: What the Armstrong Update Means
If you have a web design agency, you’ve likely spotted the update notice in a few of your client’s dashboards. The WordPress 7.0 update agencies are now working on, dubbed “Armstrong,” arrives on May 20, 2026 and is a much larger update than WordPress communities had feared. It’s not a small patch! The Gutenberg update has altered the way agencies will build websites, handle plugins and present projects to their clients in the future.
Key Takeaways
- WordPress 7.0 “Armstrong” consists of a new crop of AI features and a new feature called Visual Revisions, which is replacing real-time editing collaboration for now.
- PHP 7.4 is the new minimum; agencies should confirm client hosting before upgrading.
- Custom JavaScript and older plugins need testing on staging first, since the editor now runs inside an iframe.
What Is New in WordPress 7.0?
The most distinctive update is that it now uses AI to handle the text. It is now included in core and comes with a Connectors screen in wp-admin to enable site owners to connect accounts for Claude, Gemini or ChatGPT directly from the sites. It has been built in core and now includes a Connectors screen in wp-admin by which site owners can connect accounts for Claude, Gemini or ChatGPT. No longer will all plugins have their own individual AI integration, and now each can use a single system.
The admin area also underwent the first proper redesign since 2013, apart from the addition of the AI features. Faster transitions between pages, a new command palette (Ctrl+K) that allows you to quickly switch to any page without having to rummage through menus, and smoother editing of your post history: instead of side-by-side comparisons, you can browse through your post history like you would browse through a film on Vimeo with a slider. The Font Library also got extended to support all block, hybrid and classic themes, and Breadcrumbs and Icons will now be part of the core blocks.
One big feature that was hoped for but missing was a real-time collaborative edit. A schizophrenia diagnosis was obtained, which was pulled just before launch and deferred for a future release.
WordPress Armstrong Update: What Changed for Developers
For teams handling white-label development, the WordPress Armstrong update introduces a few technical shifts worth flagging early. PHP 7.2 and 7.3 support is gone. The new optimum PHP version is 7.4, but PHP 8.3+ is recommended for WordPress.org installation. Any client still on outdated hosting needs a PHP upgrade before upgrading to WordPress 7.0.
The block editor also now runs inside an iframe, which means custom JavaScript that references the global document object may stop working and needs review. Custom HTML blocks may need a re-save. Mobile navigation styling can shift slightly depending on the theme. None of these are deal breakers but it’s things like this that slip through the cracks when the agency runs a bulk update on dozens of sites without even checking on each before performing them.
It’s the ideal time to slow down and test in a good way – not to do the updates at one time in the middle of the night following a white label WordPress development framework – if you’re maintaining numerous clients with a white label.
WordPress 7.0 Development Changes Agencies Should Check First
Before pushing this update live on any client site, here’s what to verify:
- Staging first, always. Never update production directly, especially on sites running WooCommerce, page builders, or heavy custom code.
- Audit plugin compatibility. Older or unmaintained plugins are the most common source of conflicts with major WordPress releases.
- Check PHP version. Confirm hosting supports at least PHP 7.4, ideally 8.3+.
- Review custom scripts. Anything touching the editor’s DOM directly needs a second look because of the iframe change.
- Test forms and checkout flows. These are where broken JavaScript shows up fastest.
These WordPress 7.0 development changes are manageable, but only if agencies treat this like the major release it is, not a routine minor update.
FAQs
Is WordPress 7.0 safe to update right away?
For simple sites, usually yes. Always test on staging if your site has custom code, older plugins or WooCommerce. If you prefer, leave
Does WordPress 7.0 affect site security?
Indirectly. Any major update can expose plugin conflicts, so it’s a good time to review your setup alongside our WordPress Security guide.
Should agencies offer WordPress 7.0 upgrades as a service?
Yes. It’s a natural upsell for agencies already offering White Label WordPress Development.
Handled carefully, the WordPress 7.0 update agencies are rolling out now can be a smooth, low-drama upgrade for clients, and a good excuse to check in on sites that haven’t had a maintenance pass in a while.