WordPress 7.0 landed on May 20, 2026, and if you blinked you might have missed the most consequential change to the platform since the block editor. The release closed 419 core Trac tickets, shipped 76 enhancements, and squashed more than 300 bugs. That is a lot of code. But the thing that actually matters for the next five years of WordPress is not a new block or a fancy admin animation. It is a built-in AI client that treats language models as first-class infrastructure inside your dashboard.

Before 7.0, using AI in WordPress meant installing a plugin, trusting it with your API keys, and hoping the developer kept up with the latest model changes. Now the core itself provides a standardized interface for connecting external AI models. WordPress calls it the WP AI Client, and it comes with a Connectors screen where you can plug in API keys from OpenAI, Anthropic, and Google. Once connected, any plugin or theme that supports the new Client-Side Abilities API can call those models without rolling its own integration.

This is a bigger deal than it sounds. Plugin developers no longer need to build and maintain separate integrations for every AI provider. They write against one API, and the user picks their preferred model. If you switch from OpenAI to Anthropic next month, your plugins do not break. The abstraction layer handles it.

What the AI integration actually does today

The WP AI Client on its own does not generate content out of the box. It is plumbing. To see it in action, you install the official AI Experiments plugin from WordPress.org, which uses the new client to offer text generation, image creation, and content suggestions right inside the block editor. The plugin is a proof of concept, but it demonstrates the pattern that every serious WordPress AI tool will follow going forward.

The Connectors API is the part developers should study. It defines how API keys are stored, how requests are routed, and how responses are normalized. If you build WordPress plugins for a living, this is the API you need to learn before Q3 2026. The plugins that adopt it early will have a structural advantage over competitors still shipping their own curl wrappers.

The admin dashboard got a facelift

The other visible change in 7.0 is the modernized admin. WordPress has been gradually overhauling the dashboard since the Full Site Editing work started, and this release pushes it further. The new color scheme is cleaner, page transitions now animate smoothly, and the command palette (Ctrl+K or Cmd+K) lets you jump to any admin screen without clicking through menus.

None of this is revolutionary in isolation. But taken together, the dashboard finally feels like a modern web application instead of a PHP app pretending to be one. The iframed editor is now the default experience, which means the editing canvas actually matches what visitors see. Visual revisions let you compare content changes side-by-side with the previous version. The Font Library gives you native font management without a plugin.

For anyone who builds client sites, the practical impact is straightforward: you spend less time explaining the WordPress backend to non-technical editors. The interface is more discoverable, and the command palette alone saves a few clicks on every editing session.

Blocks got smarter

WordPress 7.0 adds a handful of new core blocks that fill long-standing gaps. The Breadcrumbs block gives you navigation breadcrumbs without a plugin. The Headings block is a wrapper that lets you manage heading hierarchy as a single unit. The Video Embed Cover block combines a video embed with a cover overlay, which is exactly the kind of thing that used to require custom CSS or a page builder.

More interesting for developers is PHP-only block registration. Until now, every custom block needed a React-based JavaScript component in addition to the PHP server-side render. WordPress 7.0 lets you register a block with PHP alone, which lowers the barrier for plugin developers who are comfortable with WordPress conventions but not with the JavaScript build toolchain. If you have been putting off building custom blocks because the editor JavaScript felt like too much overhead, that excuse is gone.

The Interactivity API also got another round of improvements. This is the framework that lets blocks add dynamic behavior (toggles, tabs, lightboxes) without shipping jQuery or custom JavaScript. It has been gaining traction since WordPress 6.5, and 7.0 extends it with better state management and more predictable hydration. If you are building anything interactive in WordPress, this is the API to standardize on.

The collaboration feature that did not ship

Every WordPress 7.0 preview article mentioned real-time collaboration as the headline feature. Multiple editors working on the same post simultaneously, Google Docs style. It was the crown jewel of Phase 3 of the WordPress roadmap.

It did not ship.

The beta testing revealed too many stability issues with the collaboration layer, and the core team pulled it before the release candidate phase. This is the right call. Shipping a half-baked collaboration feature to 40 percent of the web would have been a disaster. But it does mean that the "Phase 3" promise remains unfulfilled, and the next major release will need to pick it back up.

For now, if you need real-time collaboration in WordPress, you still need a third-party solution. CoBlocks, Multicollab, and EditFlow offer various collaboration features, but none of them are as seamless as native support would be. Watch WordPress 7.1 for the retry.

Should you update?

Yes, but test first. The 7.0 release is stable, but the admin redesign and the new editor iframe can cause issues with older plugins that assume the old DOM structure. Run the update on a staging copy, check your critical plugins, and then push to production. The performance improvements alone (client-side image processing, smoother transitions) make it worth the effort.

WordPress 7.0 is not the flashiest release the project has shipped. It does not have a single feature that makes you say "wow." But it lays infrastructure — especially the AI client — that will define how WordPress evolves for the next several years. The plugins that embrace the new APIs will pull ahead. The ones that ignore them will look outdated by Christmas.

Update your sites. Learn the Connectors API. And start thinking about what AI-powered WordPress workflows look like when the plumbing is built in instead of bolted on.