WordPress 7.0 launched today, 20 May 2026. Before diving into what shipped, it is worth being direct about one thing: real-time collaboration, the headline feature announced at WordCamp Asia, was pulled from the final release. The core team discovered that the implementation was inadvertently disabling WordPress query caches sitewide whenever the block editor was open. The fix required a new database table, which was too significant a change to make safely in a late release candidate. It will ship in 7.1.
We mention this not to diminish the release, which is genuinely substantial, but because several summaries published today still describe real-time collaboration as a shipped feature. It is not. For the purposes of this article, we are going to focus on what actually landed, particularly the AI infrastructure, because that is where the commercial implications are most significant for UK businesses.
Before you update: Do not update production sites on day one of a major WordPress release. Test on staging first, verify plugin compatibility, and create a full backup. PHP 7.4 is the new minimum requirement. PHP 8.2 or later is recommended. Check your hosting environment before updating.
What Actually Shipped in WordPress 7.0
Setting aside what did not make it, the WordPress 7.0 release is still significant. Here are the four changes that matter most for business owners and the agencies that work with them.
01 – Native AI Infrastructure. The WP AI Client, Abilities API, and MCP Adapter are built into the core. The most commercially significant change in the release and the one most other summaries will underexplain. Covered in detail below.
02 – Settings and Connectors Screen. A new admin page at Settings, then Connectors, showing available AI providers. OpenAI, Google Gemini, and Anthropic Claude appear by default. Community-built connectors for OpenRouter, Ollama, and Mistral are already available. Connection requires API keys through respective connector plugins.
03 – Admin Redesign and DataViews. The WordPress dashboard receives its first significant visual refresh in over a decade. Updated styling, smoother transitions, and DataViews are replacing traditional list tables with a more modern interface. Noticeably better day-to-day, but not a workflow transformation on its own.
04 – Developer APIs and Block Improvements. PHP-only block registration without a JavaScript build step, client-side Abilities API, new Breadcrumbs and Icons blocks, responsive block visibility controls, and several performance improvements. Significant for developers and less immediately visible for site owners.
The AI Infrastructure: What It Is and Why It Matters
The WP AI Client is a new core PHP library that provides a standardised interface for communicating with AI services. Before WordPress 7.0, every plugin that wanted to use AI handled its own integration independently. Each plugin called different AI services, stored its own credentials, and managed its own configuration. The result was a fragmented experience where AI features across different plugins had no awareness of each other and site owners had to configure multiple separate API connections.
The WP AI Client replaces that fragmented approach with a single abstraction layer. Any plugin can now communicate with AI services through one standardised interface. Switching AI provider becomes a configuration change rather than requiring code changes across multiple plugins. The Connectors screen centrally manages provider credentials.
This is genuinely useful infrastructure, even if its immediate impact on day-to-day site management is limited. The value compounds as more plugins adopt the standard over the coming months.
The Abilities API
The Abilities API, first introduced on the PHP side in WordPress 6.9, now has its JavaScript counterpart in 7.0. It provides a standardised way for plugins to declare what they can do. Rather than AI tools having to infer what a plugin can do from page content or documentation, the plugin registers its capabilities as named, structured abilities.
A WooCommerce store can register abilities for retrieving order data, checking stock levels, and returning product attributes. A membership plugin can register abilities for managing subscriber records. A booking plugin can register appointment availability queries. These abilities are discoverable by AI tools that know how to ask for them.
The practical benefit is accuracy. When an AI tool understands what a WordPress site can do based on declared capabilities rather than scraped content, the information it returns is structured and verified rather than approximated. For WooCommerce stores in particular, this matters for AI shopping recommendations, where accuracy directly affects conversion rates from AI-referred traffic.
The MCP Adapter
The Model Context Protocol Adapter converts the abilities registered through the Abilities API into the MCP format that external AI agents, including Claude Desktop, Cursor, and VS Code with MCP extensions, can discover and invoke. It turns your WordPress site into an MCP server.
What this enables in practical terms: an AI assistant with the correct permissions can query your site, understand what it offers, retrieve structured data, and perform defined actions via a controlled interface, rather than relying on fragile HTML scraping or custom API integrations. Its actions are limited to the registered abilities and the permissions you have granted.
Before WordPress 7.0: AI tools tried to read your site as a human would, interpreting HTML and guessing at its structure and capabilities.
After WordPress 7.0 with MCP: Your site can declare exactly what it does in a format AI tools read natively. The conversation between your site and AI tools becomes structured and reliable rather than approximate and inconsistent.
What This Means for LLM Optimisation
LLM optimisation is the practice of structuring your website so that large language models cite your brand accurately in AI-generated responses. It is the emerging parallel to traditional search engine optimisation, focused on answer engines rather than ranked results pages.
WordPress 7.0’s AI infrastructure connects directly to LLM optimisation in three specific ways.
Declared capabilities improve citation accuracy. AI tools that can query your site through the Abilities API and MCP Adapter have access to structured, verified information about what you offer. This reduces the likelihood of your brand being misrepresented in AI responses, which happens frequently when AI tools are forced to infer capabilities from page content alone.
The combination of schema markup and Abilities API is more powerful than either alone. Schema markup tells AI systems about your entity data: who you are, what services you offer, and where you are based. The Abilities API tells AI agents what your site can do: what data it can return, what actions it supports. Together, they provide a complete picture. A WordPress site with Organisation and Service schema, plus properly configured Abilities API, gives AI tools everything they need to represent your brand accurately across both static knowledge and dynamic queries.
WooCommerce stores have a specific advantage. WooCommerce has published MCP integration documentation that exposes store operations as abilities via the Abilities API. AI shopping assistants that can query live product data through MCP will generate more accurate recommendations than those limited to scraped page content. Accurate recommendations convert at higher rates than approximate ones.
A complete LLM optimisation foundation for WordPress 7.0 comprises four layers that work together. Organisation, Service, and FAQ schema markup tells AI tools who you are and what you offer. Structured, entity-optimised content gives AI tools information they can extract and cite. The WordPress 7.0 Abilities API and MCP Adapter let AI agents interact directly with your site’s declared capabilities. Brand authority built through mentions on credible external sources reinforces all three. Sites with all four layers in place will be consistently more visible in AI-generated responses than competitors with none.
What You Can Actually Do With This Today
The honest answer is that the AI infrastructure in WordPress 7.0 is well-built foundational plumbing whose full utility will emerge over the next six to twelve months as plugins adopt the Abilities API standard and AI tools build native WordPress MCP support into their clients.
What is genuinely usable today:
-
Connecting an AI provider through Settings and then Connectors to enable AI features across compatible plugins from a single credential configuration
-
Using Claude Desktop or Cursor with the WordPress MCP Adapter to query your site, audit content, and generate reports through natural language for sites running on supported infrastructure
-
WooCommerce stores can begin exploring the MCP integration documentation to understand what product and order data can be exposed as abilities
-
Developers building custom plugins can register abilities now, positioning their integrations ahead of the broader ecosystem adoption
What requires patience:
-
The plugin ecosystem adopting the Abilities API at scale will take the better part of 2026
-
AI shopping assistants with native WordPress MCP support are not yet widespread
-
Real-time collaboration, which will bring the most visible day-to-day change for editorial teams, ships in WordPress 7.1
How to Upgrade Safely
-
Test on staging first. This applies to every major WordPress release, especially those touching the admin interface, editor, and block system. A staging environment is not optional for sites with multiple plugins or custom development.
-
Check your PHP version. PHP 7.4 is the new minimum. PHP 8.2 or later is recommended for best performance and compatibility. If your hosting is on PHP 7.2 or 7.3, you need to upgrade before applying the WordPress 7.0 update.
-
Test plugin compatibility. Page builders, SEO plugins, WooCommerce extensions, and any plugin that customises the admin or editor are the ones to check carefully. Most major plugins have published 7.0 compatibility notes.
-
Create a full backup before updating. Even stable major releases can surface plugin conflicts. A verified backup means any issue is recoverable.
-
Do not configure AI providers immediately. The AI infrastructure is optional and entirely separate from the core WordPress update. Update first, verify stability, and then explore the Connectors screen at your own pace.
One Action Worth Taking This Week
If your WordPress site does not have Organisation, Service, and FAQ schema markup properly implemented, that is a more impactful action than anything the WordPress 7.0 AI infrastructure can provide right now. Schema markup is the foundation that AI tools use to understand and cite your brand. The Abilities API builds on that foundation. Configuring the Abilities API on a site with no schema is like adding a second floor to a house with no ground floor.
Rank Math handles Organisation, Website, WebPage, Breadcrumb, and Article schema. Schema Pro handles Service, FAQ, and Person schema. Keeping these responsibilities cleanly separated between plugins avoids conflicts and produces cleaner, structured data across every commercial page. If your schema implementation is incomplete or using a single plugin for everything, that is worth addressing before focusing on WordPress 7.0 AI integration.
If you want a clear picture of where your site stands in both traditional SEO and AI search visibility, our LLM optimisation audit covers schema implementation, content structure, entity optimisation, and MCP readiness in a single assessment.
Frequently Asked Questions
Did real-time collaboration ship in WordPress 7.0?
No. Real-time collaboration was removed from the WordPress 7.0 final release after the core team discovered that the implementation was disabling WordPress query caches sitewide when the block editor was open. The fix required a new database table, which was too significant an architectural change to make safely in a late release candidate. It is expected to ship in WordPress 7.1, planned for August 2026.
Is it safe to update to WordPress 7.0 on day one?
For most sites, waiting a few days to a week is sensible. Day one of a major WordPress release typically surfaces plugin compatibility issues that are patched quickly in 7.0.1 and 7.0.2. If your site has complex plugin dependencies or custom development, using a staging environment is essential before updating the live site. If you are on managed WordPress hosting with automatic updates and rollback capabilities, the risk is lower.
Do I need to configure AI providers to benefit from WordPress 7.0?
No. WordPress 7.0 works exactly as before without any AI provider configuration. The AI Client, Abilities API, and MCP Adapter are all optional infrastructure. Configure AI providers only if you have a specific use case in mind and have verified that your hosting environment supports the requirements.
What is the WordPress Abilities API?
The Abilities API is a standardised framework built into WordPress core that allows plugins to register their capabilities as named, structured units of work. Rather than having AI tools guess what a plugin can do, the plugin explicitly declares it through the API. A WooCommerce store can register the ability to return product data. A booking plugin can register appointment availability queries. These registered abilities are then accessible to the AI Client and, through the MCP Adapter, to external AI agents.
What should I prioritise before exploring WordPress 7.0 AI features?
Schema markup first. If your site does not have Organisation, Service, and FAQ schema correctly implemented and validated, that is a higher-impact action than any AI configuration. Schema is the foundation that AI tools use to understand your brand. The WordPress 7.0 AI infrastructure builds on that foundation. Once your schema is solid and your site is confirmed stable on 7.0, then exploring the Connectors screen and Abilities API integration makes sense.
WordPress Website AI Capabilities: What UK Businesses Need to Know
The WordPress 7.0 release is part of a broader shift in how artificial intelligence is being integrated into professional website management. Understanding where WordPress MCP fits alongside existing AI plugins and AI WordPress plugins helps clarify what is genuinely new and what has been available for some time.
The WordPress plugin ecosystem already includes a wide range of AI capabilities across different categories. SEO tools with AI features help identify content gaps, suggest improvements to search engine rankings, and generate meta descriptions. Page builder plugins, including Elementor AI, allow teams to generate copy, create layouts, and produce design variations through natural language prompts directly within the editor. These tools have steadily improved and offer a practical entry point for teams exploring AI on a WordPress website without committing to a full MCP implementation.
The distinction between these existing AI plugins and the WordPress 7.0 AI infrastructure lies in scope and architecture rather than capability. An individual AI plugin operates within its own context. The WP AI Client and Abilities API operate at the platform level, making AI capabilities available across every compatible plugin through a single, standardised configuration. A professional WordPress website built on the 7.0 infrastructure is not just a site with AI plugins added. It is a site where AI integration is a first-class citizen of the platform rather than a collection of independent add-ons.
AI Power and the Professional Website: Practical Considerations
The practical AI power now available through a properly configured WordPress 7.0 site goes beyond what individual AI plugins could previously achieve. AI models connected through the WP AI Client can draw on declared site capabilities across multiple plugins simultaneously. A query about product availability can leverage WooCommerce’s capabilities. A content audit can draw on post data, SEO metadata, and schema implementation status across the entire site at once. This cross-plugin awareness is genuinely new and represents the most significant upgrade that the 7.0 AI infrastructure delivers over the previous plugin-by-plugin approach.
For teams managing a professional website with significant content volumes or a WooCommerce catalogue, the AI power unlocked by this cross-plugin awareness has real commercial value. Reporting tasks that previously required manual review or separate analytics tools can be handled conversationally. Content workflows can be accelerated without sacrificing editorial oversight. The key is treating these AI models as capable assistants with defined boundaries rather than autonomous systems operating without human review.
An AI website builder approach, where artificial intelligence generates a site from scratch based on prompts, is an entirely separate category from what WordPress 7.0 provides. Tools in the AI website builder space target users who want to create a basic web presence quickly without agency involvement. WordPress 7.0’s AI infrastructure targets businesses that already have a professional WordPress website and want to make it more capable, more visible in AI search tools, and more efficient to manage over time. These are fundamentally different audiences with fundamentally different needs.
Content Creation, SEO Tools, and AI WordPress Plugins Working Together
Content creation is where most UK businesses will first encounter the practical benefits of WordPress AI integration. AI models connected through the WP AI Client can assist with drafting posts, generating summaries, suggesting internal links, and producing schema-ready FAQ content. The difference from standalone AI writing tools is that the AI has context about the specific WordPress website it is working with, including existing content, categories, and site structure, rather than operating in isolation.
SEO tools remain essential alongside AI capabilities. Rank Math and similar plugins handle the structured data and search engine rankings signals that AI systems use to understand and cite your brand. The relationship between SEO tools and AI integration is complementary rather than competitive. SEO tools build the schema foundation. AI capabilities are built on top of it. A professional website that has invested properly in both is significantly better positioned for AI search visibility than one that has focused on either alone.
Elementor AI and similar page-builder AI features continue to serve their specific purposes within the editing workflow. WordPress 7.0 does not replace these tools. For teams that rely on Elementor AI for layout generation and copy drafting within the editor, those workflows continue unchanged. What changes is the availability of a broader AI power layer at the platform level that these tools can gradually integrate with as the ecosystem matures through 2026 and into 2027.
For UK businesses evaluating their WordPress website’s readiness for AI search visibility, the starting point remains the same, regardless of WordPress 7.0: get schema markup in place, ensure content is clearly structured, and build brand authority through credible external mentions. The artificial intelligence infrastructure that WordPress 7.0 provides is the next layer once that foundation is solid. If you would like an honest assessment of where your site stands, our LLM optimisation service covers all of these areas in a single audit.
