WordPress 7.0: Building AI Infrastructure
WordPress 7.0 ships on May 20, and it is being talked about as the platform’s biggest step into AI.
That is accurate, but the way AI shows up in this release is not what most people picture when they hear the word. There is no chatbot. There is no content generator. What WordPress has built instead is the plumbing: the standardized connections, protocols, and shared infrastructure that allow AI tools to work with a WordPress site in a structured, reliable way.
Think of it less as WordPress gaining AI features, and more as WordPress becoming the kind of platform that AI tools can actually work with. The immediate payoff for editors and site owners is modest. What changes is what becomes possible in the months and releases that follow.
What’s actually included:
The AI story in 7.0 is not one single feature but a set of infrastructure pieces WordPress has been assembling across recent releases, now complete enough to work together in a meaningful way.
The AI layer
The AI Client. New in 7.0 core: a shared connection layer that lets any plugin send a prompt to an AI model and get a response back, regardless of whether it comes from OpenAI, Anthropic, Google, or anyone else. This ends the era of every AI plugin building its own bespoke connection to its own preferred provider.
Connectors. Also new in 7.0: a centralized settings screen where site administrators manage all AI provider credentials in one place, rather than configuring each AI plugin separately. The two work together: Connectors handles the keys, the AI Client handles the calls.
The Abilities API. Introduced in WordPress 6.9 and significantly expanded in 7.0, this gives a WordPress site a standardized way to describe its own capabilities to outside systems. Think of it as a machine-readable menu: every registered ability has a name, defined inputs and outputs, a permission level, and an action. An AI agent or automation platform can read what your site can do without anyone hand-writing a custom integration.
The editing experience
Improved editor accuracy. The editor now shows content as it will actually appear to visitors on the live site, reducing the back-and-forth between editing and previewing.
Block visibility by device. You can now hide or show individual blocks depending on whether someone is on mobile, tablet, or desktop, without any custom code.
Custom block styling. Individual content blocks can have their own styles applied directly in the editor, without a developer needing to edit theme files.
Visual revisions. Content history now shows a visual preview of exactly what changed between versions, color-coded by addition, deletion, and modification.
New blocks and design
Admin refresh. The dashboard has been visually modernized, and navigating between screens is now smooth and animated rather than a hard page reload.
New blocks. Three new blocks ship with 7.0: Breadcrumbs (automatic navigation hierarchy), Icon (native SVG icon library), and Navigation Overlay Close (for fully customizable mobile menus). The Cover block also gains support for YouTube and Vimeo video backgrounds without requiring a file upload.
Also in 7.0
Server requirements. WordPress 7.0 drops support for PHP 7.2 and 7.3, with a new minimum of 7.4 (8.3 recommended). This affects roughly 4% of sites — almost certainly not yours if you are on managed WordPress hosting.The one notable absence: real-time collaborative editing. This was a headline feature WordPress 7.0 was built around, but it was pulled after stability concerns around data conflicts and server load. It will now arrive in a future core release after further development.
Also worth knowing: launching around 7.0, but not in core
A few things are arriving in the same moment as 7.0 without being part of the core release — part of the same direction, but at different levels of readiness.
The MCP Adapter is a standalone library that bridges WordPress and external AI assistants. MCP (Model Context Protocol) is an open standard that lets AI tools like Claude and ChatGPT connect to external systems and actually act on them, not just discuss them. Install the adapter and an AI assistant can discover what your site can do and invoke those actions directly.
Content Guidelines is an experimental Gutenberg feature, not in core and not enabled by default. When switched on, it gives site owners a structured place to define editorial voice, tone, and content rules that AI tools can read and apply. Currently aimed at developers and early adopters.
Telex is a separate experiment from Automattic, demoed by Matt Mullenweg at WordCamp US last year. Describe a content block in plain language and Telex generates the code — no developer required. Early testing has found the output uneven and it is not production-ready, but the direction it points toward is significant.
The honest summary
WordPress 7.0 is a release where the marketing will be about AI and the substance is about infrastructure. Nothing is going to feel dramatically different in the editor on day one. But the rails are now in place for a category of work that was difficult, custom, and expensive to do this time last year, and that is going to be routine by this time next year.
The direction this release commits to is the same argument we have been making with clients for two years: AI does not work without a solid foundation underneath it. The organizations that benefit fastest from 7.0 are the ones that already have structured content, clean analytics, and operational discipline at the platform level. The ones that do not are about to find out that AI readiness starts further back than they expected.
Dreamers of Day is a data and product agency. We build, operate, and evolve digital platforms, and the data infrastructure behind them, for organizations where the platform matters too much to leave unattended. If you want a read on what WordPress 7.0 changes for your specific platform, we should talk.
