WordPress 7.0 shipped on May 20, 2026, and it’s being called the most significant release in over a decade.
Most major versions bring new blocks, editor tweaks, and performance gains. This one is different, and the reason is simple: AI is no longer something you bolt onto WordPress from the outside. It’s becoming part of WordPress itself.
But the story is more nuanced than the headlines suggest, and a few of those headlines are wrong. Here’s what actually arrived, what didn’t, and whether you should update.
The Headline: AI Moves Into Core
For years, using AI in WordPress meant installing separate plugins, wiring up multiple API connections, and managing different tools across different dashboards.
WordPress 7.0 takes a different approach. It builds a shared AI layer directly into the core, and crucially, it’s provider-agnostic. Instead of locking you into one company, it gives you a central place to connect services like OpenAI, Google Gemini, or Anthropic’s Claude through a single, consistent framework.
That sounds abstract. The next section makes it concrete, because this is the part most coverage gets wrong.
What’s in Core, and What Isn’t
Here’s the thing to understand before you update: there is no AI writing assistant built into WordPress 7.0.
Update your site, open the editor, and you won’t find an AI button. What you’ll find instead is a new Connectors screen under Settings, where you add an API key for a provider. That’s the shift. WordPress 7.0 ships the plumbing, not the taps.
What lands in the core is infrastructure:
- The AI Client — a single, standard way for WordPress to talk to any AI provider.
- The Connectors screen — one place to store your provider keys, so you’re not pasting the same API key into five different plugins.
- The Abilities API — a registry of what your site can do and what each provider can handle, so requests get routed correctly.
The visible tools generating titles, excerpts, summaries, alt text, and images come from a separate AI Experiments plugin you install yourself. They appear in the editor sidebar, and you trigger them manually. Nothing runs on its own. If you update and install nothing else, nothing about your editor changes.
I think that’s the right call. Baking a fixed set of AI behaviours into core would lock every WordPress site into one company’s idea of what AI should do. Shipping the foundation instead and leaving the features to plugins built on a shared standard keeps the control where it belongs: with the site owner.
Why the Foundation Matters More Than the Features
Many people think of AI in WordPress as generating blog posts.
I think that’s missing the bigger picture. The real opportunity isn’t AI writing articles for you; it’s reducing friction. Generating alt text. Creating summaries. Improving accessibility. Helping site owners maintain their websites. Automating the repetitive tasks nobody enjoys doing.
Used well, AI doesn’t replace expertise. It removes busywork.
That’s why the infrastructure matters more than any single feature shipping today. Before 7.0, every plugin that wanted to use AI had to build its own connection to every provider, resulting in duplicated effort, inconsistent behaviour, and your API key scattered across half a dozen settings pages. The AI Client and Abilities API replace that mess with one shared standard. Configure a provider once, and any compatible plugin can use it.
The features available right now are modest. The foundation underneath them is not.
What Else Shipped
AI grabbed the attention, but the rest of the release quietly modernises parts of WordPress that have looked the same for years.
The admin gets the biggest visible refresh. Legacy list tables are replaced by DataViews — dynamic, filterable views that make managing posts, pages, and media feel less like a spreadsheet from 2010. There’s a new Command Palette (Cmd/Ctrl + K) for jumping to actions without hunting through menus, visual revision scrubbing so you can actually see what changed between versions, and a dedicated font management page.
The block editor is also faster, particularly on long pages and complex layouts, alongside the usual round of new blocks, design controls, and developer tooling.
None of this is revolutionary on its own. Together, they’re the kind of housekeeping that makes daily work less tedious, which, over time, matters more than any single flagship feature.
What This Means
It’s worth being honest about what shipped. Real-time collaboration, the Google-Docs-style co-editing everyone was waiting for, didn’t make it. It was pulled shortly before launch over performance concerns and pushed to a future release. So if that was your reason to upgrade, it’s not here yet.
What arrived is quieter, and in the long run, probably more important. WordPress now has a standard, provider-agnostic way to connect AI to a site. That’s not a feature you’ll notice this week. It’s the groundwork for the next few years. It’s the layer on which future plugins, automation, and accessibility tools will be built.
WordPress isn’t trying to become an AI product. It’s making itself into a platform for AI tools to plug into, on the site owner’s terms. For anyone who works with WordPress daily, that’s the detail worth paying attention to, not the demo-friendly features, but the foundation they’re standing on.
Conclusion
I’ve been building websites with WordPress for years, and what interests me most about 7.0 isn’t the AI. It’s the reduction of friction. The best technology doesn’t make you work harder. It removes unnecessary work so you can focus on what matters. Whether that’s writing, design, marketing, or running a business, I think that’s where AI is most useful inside WordPress.
Not replacing people.
Helping them spend more time on the parts of the job that humans are actually good at.
Need Help With WordPress?
Whether you’re updating to WordPress 7.0, resolving plugin conflicts, or starting a new website, I help individuals and small businesses get more out of WordPress.
→ Fix My Site
→ Start a New Site
