WordPress 7.0 - "Armstrong" - named (as WordPress releases are, after the jazz artist Louis, not the astronaut Neil) landed on 20th May 2026, and if you've been waiting for the big-ticket feature that was promised - real-time collaborative editing, à la Google Docs - we've got some bad news. It got pulled. Again. What did make it into the release, however, is something arguably more significant, and certainly more contentious : a brand new Web Client AI API, baked into core, sitting there ready and waiting for any plugin or theme to plug an AI model into your site.
That's a big deal. And not necessarily a good one.
What's actually in the release
Let's get the housekeeping out of the way first. WordPress 7.0 brings:
A new Web Client AI API in core - a standardised way for plugins and themes to talk to external AI providers (OpenAI, Anthropic, Google, whoever)
A Client Side Abilities API, which lets developers register browser-side capabilities that AI assistants can then use
PHP-only block registration with auto-generated inspector controls (meaning developers can ship functional blocks with far less JavaScript)
A refreshed admin dashboard
Notes with real-time syncing and inline comment shortcuts
Various improvements to the Block and Site Editors
What didn't make it : true real-time co-editing. It was the headline feature for the best part of a year, got demoted to "beta-quality", and was eventually shelved for a later release. The release was also pushed back from 9th April to 20th May to give the core team time to sort out architectural stability. Hold that thought.
So what's the AI bit, exactly?
WordPress hasn't built its own AI. What it's done is build the plumbing. Think of it as the equivalent of how WordPress handles, say, payment gateways - core doesn't process your payments, but it gives Stripe, PayPal, GoCardless and the rest a standardised way to slot in.
The Web Client AI API does the same for AI. The model providers stay external. WordPress just gives plugins a clean, consistent way to register them and call them. The Abilities API then lets developers tell those AI models what your site can do - so an AI assistant doesn't just generate text, it can theoretically take actions on your behalf.
In practice, what you'll see over the coming months is a flood of plugins offering AI-powered everything. Write me a product description. Generate alt text for these images. Suggest a meta description. Translate this page. Draft a reply to this comment. Some of it will be genuinely useful. A lot of it won't be.
Where we think this gets uncomfortable
Here's our concern, and it isn't really a technical one.
WordPress powers somewhere north of 40% of the web. When a platform that big makes AI a first-class citizen, it normalises something that, frankly, a lot of small businesses haven't really thought through yet. Namely : do you actually want AI writing your website?
We've spent a lot of time over the last year talking to clients about how AI platforms are sending them traffic (we wrote about measuring that here) and about whether they should be writing for AI readership (we're yet to be convinced). But that's about AI reading your site. WordPress 7 makes it trivially easy to have AI writing your site too. And that's a different conversation.
The reason it's a different conversation is that the value of your website - the bit that actually makes someone pick up the phone, or fill in the contact form, or buy the thing - is almost never the boilerplate. It's the voice - the bit that sounds like a human who knows what they're talking about, not a confidently bland summary of fifty competitors' websites mashed together.
If every WordPress site on the internet starts pumping out AI-generated copy via the path of least resistance - and the path of least resistance is exactly what core integration creates - then the average quality of web content is going to drop. And the sites that don't do that are going to stand out more, not less.
The practical bit
So, what does this mean if you're running a WordPress site for your small or medium business?
A few things, in roughly the order we'd think about them.
First, don't rush to update. This isn't us being technophobic - we update sites all the time. But WordPress 7.0 is a major release with significant architectural changes, and the team themselves pushed the release back by six weeks because of stability concerns. If you're on a managed host with staging, test there first. If you're not, give it a fortnight and let other people find the bugs.
Second, be very deliberate about which AI plugins you let near your site. The new API is going to bring a Cambrian explosion of plugins offering AI features. Most of them will be free, will demand an API key, will need access to your content, and may or may not be maintained six months from now. Treat them like any other plugin - fewer is better, well-maintained is non-negotiable, and "does it actually save me time or money" is the only question that matters.
Third, think about what you want AI to do, not what it can do. There's a meaningful difference between using AI to draft alt text for two hundred product images (sensible, time-saving, low-risk) and using it to write your About Us page (please don't). The former is the kind of grunt work that AI is genuinely good at. The latter is the bit that should sound like you.
Fourth, if you're going to use it, edit it. Treat AI-generated content as a first draft, never as a final one. Read it out loud. Does it sound like you? Would you say it to a customer in person? If not, change it until you would.
Our take
WordPress 7.0 is a competent release. The technical work is solid, the developer APIs are well thought through, and the decision to ship without real-time collaboration rather than ship a broken version was the right one.
But the broader direction of travel is one we'd urge a bit of caution about. Making AI a core feature of the world's most popular CMS will, inevitably, make AI-generated content the default rather than the considered choice. And for the small and medium-sized businesses we work with - whose websites live and die on sounding like real humans with real expertise - the default is rarely where you want to end up.
Update when you're ready. Use the AI when it genuinely helps. But don't let the path of least resistance write your website for you.
If you want a hand thinking through what AI should and shouldn't be doing on your site, get in touch - we'd be happy to talk it through with you.