WordPress 7.0, nicknamed "Armstrong" after jazz legend Louis Armstrong, shipped on 20 May 2026. It is the platform's first major release since WordPress 6.9 in December 2025, and the current stable version is 7.0.2, a security release dated 17 July 2026 (7.0.1 was a maintenance release on 9 July). If your accounting, legal, health or agency website runs on WordPress, this is a release worth understanding, because the changes touch how sites are built, secured and maintained.
What changed
The headline feature is artificial intelligence moving into the core software. WordPress 7.0 introduces an AI Client in core that lets WordPress talk to generative AI models, managed centrally through a new Connectors screen for wiring up external services such as OpenAI, Google Gemini and Anthropic Claude. Alongside it, the release expands the Abilities API (first introduced in 6.9), a standardised way to expose site functionality and workflow automation to plugins, tools and AI agents.
The other big story is design. Armstrong delivers the first admin redesign since 2013, with a refreshed dashboard, smoother view transitions, and a Command Palette you open with Cmd or Ctrl+K to jump between tools. There is also Visual Revisions, which lets you scrub through past versions of content to see what changed at a glance, plus new editor blocks including Breadcrumbs and Icon.
Under the hood, the minimum supported PHP version was raised (reported as PHP 7.4), which matters for older hosting setups. The release was built by more than 875 contributors across 70-plus locales.
One honest note: the long-anticipated real-time collaboration feature, which would have let multiple people edit the same content simultaneously, was pulled roughly 12 days before launch and deferred to a future version. If that capability was on your roadmap, it is not here yet.
What it means for your firm's site
The AI features are real and genuinely interesting, but for a professional-services firm they are not the point. Your website exists to be found, trusted and booked. That means the priorities are performance, security, accessibility, and not getting locked into complexity you cannot maintain.
On security, the fact that 7.0 already needed a security patch (7.0.2) within two months is a normal part of the WordPress cycle, not a red flag. It is a reminder that a WordPress site is only as safe as its update discipline. Every new core capability, and every plugin bolted on to use it, widens the surface that needs patching. For firms in Australia and the UK handling client financial, legal or health information, that maintenance burden is a real cost and a real obligation under privacy expectations.
On performance and accessibility, a fresh admin experience does not automatically make the public-facing site faster or more accessible. Those depend on your theme, your plugins and your build. Adding a core AI Client does not change your Core Web Vitals or your WCAG position on its own.
To be clear, none of this is a knock on WordPress. It powers a huge share of the web and Armstrong is a serious, well-supported release. Amina simply builds on a different, modern stack rather than WordPress, because for many professional-services firms a leaner performance-focused site is easier to keep fast, secure and genuinely yours over time. The deferred collaboration feature is a useful example of why: capable platforms carry ambitious roadmaps, and roadmaps slip.
What to do now
Book a Website Review. Before you rush to adopt (or ignore) WordPress 7.0, get an honest health check of your current site covering performance, security posture, accessibility and how much maintenance risk you are carrying. That one step tells you whether your site is genuinely built to be found and built to keep, or whether it is quietly accumulating cost.
FAQ
Do I have to update to WordPress 7.0?
If you run WordPress, you should stay on a supported, patched version, and 7.0.2 is the current stable release. Whether to jump to a new major version straight away is a judgement call. Test on staging, confirm your plugins and PHP version are compatible, and make sure someone owns the ongoing updates.
Does the new AI Client mean my site is now "built for AI search"?
No. The AI Client is about connecting your admin to AI models for content and workflow tasks. Being found in AI-powered search is a separate discipline: clean structure, fast pages, solid content and machine-readable markup. That is true on any platform.
We are not on WordPress. Does this affect us?
Not directly, and that is rather the point. A modern, performance-focused build sidesteps the plugin-and-patch cycle entirely. The principles still apply though: keep your site fast, secure, accessible and easy to maintain.
If you want your site built to be found, in search and in AI, and genuinely yours to keep, talk to Amina about a Website Review or a Web Build.
