The real changes
WordPress 7.0 brings real changes on several fronts. The admin interface has been updated: a more modern color palette, improved typography, sharper contrast. Not a radical redesign, but if you spend hours in the editor you'll notice.
The command palette (Cmd+K on Mac, Ctrl+K on Windows) is now accessible from any screen in the dashboard, not just the editor. Moving between content, settings and actions without redundant clicks is a real time saving.
Revisions finally have a usable visual interface: highlighted changes, color coding for additions and deletions, block preview instead of raw HTML. Anyone who has managed WordPress content for years knows how much that was missing.
The rest: extended font library for classic themes (where it didn't reach before), per-block custom CSS, conditional block visibility by device, two new native blocks (Breadcrumb and Icon), improvements to the Heading, Gallery and Paragraph blocks. This is not routine maintenance.
The AI API: what it actually is
The most discussed feature in WordPress 7.0 is the new native API for connecting AI models to the CMS. Pay attention to the word "connecting": nothing automatic is included. You go to Settings > Connectors, enter your OpenAI, Google or Anthropic API key, and enable access for plugins and themes.
It's infrastructure, not a user-facing feature. Before, every AI plugin built its own integration system. Now there's a shared standard in core: less redundancy, more consistency across tools. That makes sense.
Real-time collaboration was on the roadmap for this release. It's not there. It was postponed. If your editorial team was waiting for it, the wait continues.
The AI functions: useful, not revolutionary
The functions plugins will start offering through this API revolve around content: generating titles, writing summaries, drafting posts, suggesting layouts, creating alt text. Useful for anyone producing content daily.
This is not an architectural shift. It's intelligent autocomplete with a cleaner integration channel. The pattern in the more enthusiastic posts is always the same: UI with AI suggestions, labeled as "revolution". But the actions shown are always the same limited set: generate text, fill fields, vary headlines.
On simpler sites, most of this was already doable with external tools. The only real difference is that it now happens inside core with less friction. Useful, yes. A discontinuity? No.
Who is actually facing a real change
The part of the market that shifts most is the part that was already shifting: brochure sites, repetitive SEO content, standard page builder setups. They commoditize further. The trend isn't new, but the pace picks up.
Those who work on more complex systems — structured content architectures, external system integrations, custom frontends, bespoke business logic — aren't looking at a different situation than six months ago. The problems that make those projects hard remain unchanged: legacy content to migrate, specific technical requirements, accumulated debt, performance under load.
AI is good at producing fragments: drafts, snippets, boilerplate, placeholders. It struggles with systems that have consolidated logic and years of layered changes. WordPress itself, with its twenty-year ecosystem, is a clear example of that kind of complexity.
Is it worth updating?
Yes. The real improvements in WordPress 7.0 are solid, especially for anyone who works heavily in the editor or manages classic themes. The AI API is infrastructure that will make more sense in a few months, once mature plugins use it reliably.
The practical advice is the same as always: backup first, test on staging if you have particular configurations, then update. Compatibility issues exist — rare with well-maintained plugins, but they do exist.
WordPress 7.0 is a good update, probably one of the more coherent releases of recent years. It's not the revolution some posts describe. That distinction matters, because someone has to manage the wrong expectations.
Frequently asked questions
Does the AI in WordPress 7.0 work without configuration?
No. To use it you need to manually connect an AI provider (OpenAI, Google or Anthropic) from Settings > Connectors and enter your API key. Without configuration, no AI function is active. The API is infrastructure for plugins, not a ready-to-use feature.
Did real-time collaboration ship with WordPress 7.0?
No, it was postponed. It was planned on the roadmap for this release but didn't make it through the stabilization phase. It will arrive in a later update.
Should I update to WordPress 7.0 right away?
Backup first, then test on staging if you have specialized plugins or complex builds. For most sites with updated plugins the migration is straightforward. The release was originally planned for April 9th but slipped to May 20th specifically to allow more stabilization time.
Next step
Working on a WordPress 7.0 upgrade for a complex site?
If you're evaluating the update on a more complex setup, let's look at what it brings and what it requires.
Get in touch