Most WordPress releases get a polite round of applause and then quietly disappear into the update queue. WordPress 7.0 is different. Not because it ships a flashy new AI chat widget or a drag-and-drop magic button, but because it fundamentally changes what WordPress is as a platform. We’ve been tracking this release closely at what., testing it against our own workflows, and the honest conclusion is this: 7.0 makes the “is WordPress serious enterprise software?” question a lot easier to answer than it used to be.
If you’re running a business on WordPress, or evaluating it for a new project, here’s what actually matters – and what’s just noise.
Also relevant: How we approach modern WordPress development gives useful context on how these changes fit into the bigger picture of where WordPress is heading.
WordPress just stopped being a publishing tool
WordPress has always been extensible. But extensibility through plugins has a ceiling: every team ends up with a different stack, inconsistent API integrations, and no standardized way for AI tools or automation systems to actually interact with the site.
7.0 starts pulling critical capabilities back into core. The result is a platform that doesn’t just support AI – it’s structured so that AI can discover, understand, and act on a WordPress site in a controlled, predictable way.
That’s the strategic shift. It’s less “we added AI features” and more “we rebuilt the foundation so AI systems can plug in properly.”
Practically speaking, this release also marks the start of Gutenberg Phase 3, which moves the editor from a single-user publishing tool toward a genuine multi-user editorial environment. For content teams who’ve been copying drafts into Google Docs to collaborate, that’s a real operational change.
One heads-up if you’re on an older server setup: WordPress 7.0 requires PHP 7.4 as a minimum. Worth checking before you schedule the upgrade.
The AI framework that ships with 7.0 (it’s not what you think)
WordPress 7.0 does not ship a chatbot. It does not generate content for you out of the box. What it ships is infrastructure – and for enterprise teams and serious digital operations, that’s actually more valuable.
Three components make up the new AI framework:
- Connectors API and Connectors UI: There’s now a dedicated section in Settings called “Connectors” where you configure AI provider credentials once – OpenAI, Anthropic, Google – and every plugin built against the framework can use those connections. No more per-plugin API key chaos, no more duplicate credentials scattered across settings pages.
- WP AI Client SDK: A single, standardized interface for interacting with multiple AI providers. The big practical benefit: you can swap providers without rewriting your integrations. For organizations with data residency requirements (a common concern among Swiss finance and public sector clients) this vendor-agnostic design matters a lot. You’re not locked into one provider’s infrastructure.
- Abilities API: This is the piece that really changes things. The Abilities API describes, in a machine-readable format, everything a WordPress site is capable of doing. Think of it as WordPress finally exposing its own capabilities in a language that software can read and act on, not just humans. When combined with the MCP Adapter (which translates these abilities into the Model Context Protocol standard), external AI agents can connect to a WordPress site, understand what’s available, and execute actions directly.
WordPress 7.0 isn't asking how to add AI to WordPress – it's asking how to make WordPress a platform that AI can build on. That's a much more durable question.
The governance angle here is worth emphasizing. The Abilities API isn’t just about enabling AI, it’s about constraining it. Organizations can define precisely what AI tools are allowed to access or change. That’s essential for compliance-sensitive environments.
Related read: DDEV Setup & AI-Powered Development Workflow for WordPress shows how AI integrations fit into a real development workflow – including how we’re already using tools like WP-CLI and the Abilities API in day-to-day builds.
A real-world example from our team
We built a workflow that turns a spoken transcript into a fully structured WordPress blog draft and a LinkedIn announcement – all via Claude and the WordPress MCP Adapter.
The flow goes: three intake questions, analysis, outline approval, full draft approval, WordPress post creation (via the Abilities API and Yoast SEO’s ability layer), then a LinkedIn text draft. Posts always land as drafts, nothing publishes automatically. The whole process, from transcript to ready-to-review post, runs without anyone touching the WordPress backend manually.
This is the kind of workflow 7.0’s infrastructure makes possible in a structured, auditable way. The Connectors API handles credentials centrally; the Abilities API defines what the agent can and can’t do; the MCP Adapter is what lets Claude talk to WordPress in the first place. Without these building blocks in core, you’d be stitching together custom integrations for every project.
Real-time collaboration: useful, but temper expectations
Gutenberg Phase 3 brings live multi-user editing to the block editor – presence indicators, real-time sync, the ability for multiple people to work on the same page simultaneously. For marketing teams and distributed editorial operations, this is a genuine improvement over the current reality of emailed drafts and Google Doc workarounds.
The iframed editor also lands with 7.0. In practical terms, this means better style isolation between the editor and the admin interface – what you see while editing is closer to what visitors actually see. That reduces QA overhead on content-heavy projects.
One thing to flag: plugins that interact directly with the editor DOM may need updating. If your site relies on heavily customized editor tooling, it’s worth testing before upgrading. This isn’t a dealbreaker, but it’s a real consideration for existing sites with complex setups.
What this means if you’re a WordPress user
The honest summary: WordPress 7.0 raises the baseline. Here’s where that shows up in practice:
- Fewer external tools for editorial coordination: more workflow stays inside WordPress
- Standardized AI integrations: no more shadow integrations or scattered API key management
- Better design governance: expanded pattern and template controls give content teams more structure
- Improved performance out of the box: more selective asset loading and smarter caching reduce the need for heavy optimization plugins
For Swiss companies in regulated industries (finance, insurance, public sector) the combination of vendor-agnostic AI connections and governed Abilities API access is particularly relevant. You get AI-powered functionality without handing over control to a single provider or exposing your entire system.
That said, 7.0 raises the floor, it doesn’t eliminate bespoke work. Complex editorial workflows, custom approval chains, or specialized integrations will still need custom development. The platform is just better positioned to support that work cleanly.
At what., we’re already building AI-assisted content workflows on top of the 7.0 framework – the kind that let clients manage more with smaller teams, without sacrificing quality or governance.
Worth the upgrade?
Yes, but the value depends on how you use it.
For teams already on WordPress: plan your PHP check, review any editor-dependent plugins, and start thinking seriously about how the Connectors API fits your stack. The AI infrastructure is available now; the question is whether you have a use case ready to put it to work.
For teams evaluating WordPress for a new project: 7.0 makes WordPress a much more credible answer to enterprise requirements. The “it’s just a blogging platform” objection is harder to sustain when the platform ships governed AI infrastructure and standardized agent connectivity out of the box.
The biggest cost of staying on an outdated CMS (Content Management System) setup isn’t the license – it’s the opportunity cost of every workflow you can’t automate.
We’re not waiting for the ecosystem to catch up. If you want to explore what building on WordPress 7.0 looks like for your business, our WordPress services cover the full picture — from strategy and custom development to AI integrations and ongoing support.
