Updated: March 31, 2026 By: Marios
WordPress 7.0 lands on April 9, 2026 — and it quietly changes everything about how AI works inside the world’s most popular CMS.
This isn’t another release with incremental block editor tweaks. WordPress 7.0 embeds a full AI infrastructure layer directly into core. That means any plugin can now connect to Claude, ChatGPT, Gemini, or any other AI model through a single, standardized system — without every plugin reinventing the wheel.
I’ve been building WordPress sites since 2010 and testing AI plugins for the past three years. After spending weeks with the WordPress 7.0 beta, here’s my complete walkthrough of what’s actually shipping, what it means for your site, and exactly how to prepare before update day.
What’s actually new in WordPress 7.0 for AI
Let’s cut through the noise. WordPress 7.0 introduces three interconnected AI features that work together as a system. Understanding how they fit together matters more than understanding each one individually.
The AI Client SDK (now in core)
Until now, every AI-powered WordPress plugin had to build its own connection to OpenAI, Anthropic, or Google. That meant each plugin stored its own API keys, handled its own authentication, managed its own error handling, and created its own settings page. If you ran three AI plugins, you had three separate API key fields scattered across your dashboard.
WordPress 7.0 changes this fundamentally. The WP AI Client SDK is now part of WordPress core itself. It provides a single, standardized way for any plugin to make AI requests. The plugin developer doesn’t need to worry about API key management, provider authentication, or rate limiting — WordPress handles all of that centrally.
For site owners, this means one settings page for all your AI connections instead of a dozen scattered ones. For developers, it means writing significantly less code to add AI features to a plugin.
The SDK was first released as a standalone plugin in late 2025 (wordpress/wp-ai-client version 0.1.0). Starting with WordPress 7.0, it ships with every WordPress installation by default — the same way the REST API or the block editor is just there when you install WordPress.
The Connectors UI (Settings → Connectors)
This is the practical, visible part of the AI system. Navigate to WP-Admin → Settings → Connectors and you’ll find a new dashboard page where you manage all your external AI connections in one place.
From this screen, you can add your API keys for different AI providers, see which providers are active, manage and update connections, and test that your connections are working.
The Connectors UI was introduced in Beta 2 and refined through the beta cycle. It’s powered by an extensible architecture — meaning plugin developers can hook into this page and add their own connection types. So if a new AI provider launches next year, a plugin can add support without WordPress core needing an update.
The three default providers at launch are OpenAI (GPT-4o, GPT-4 Turbo, etc.), Anthropic (Claude), and Google (Gemini). Additional providers can be registered through the WP AI Client registry, and Beta 3 expanded this to dynamically register providers beyond the three defaults.
The Abilities API
This is the most forward-thinking piece, and it’s the one most people will overlook initially.
The Abilities API lets plugins register what they can do in a machine-readable format. Think of it as a menu that AI assistants can read. Instead of an AI agent needing to know the specific code to resize an image in WordPress, your image optimization plugin can register an “ability” called “resize_image” with parameters like width, height, and quality. Any AI system that connects to your WordPress site can discover and use that ability.
Why does this matter? Because it means WordPress is positioning itself not just as a platform you use AI with, but as a platform AI can use. An AI agent could theoretically discover that your WordPress site can resize images, generate thumbnails, publish posts, and manage WooCommerce inventory — all through standardized ability declarations.
This connects directly to the Model Context Protocol (MCP), which WordPress now supports through an adapter. MCP is the emerging standard for how AI systems interact with external tools. WordPress is one of the first major platforms to adopt it at the core level.
The Connectors screen: a hands-on walkthrough
Here’s exactly what to expect when you first open the Connectors page after updating to WordPress 7.0.
Step 1: Navigate to the Connectors page
After updating, go to WP-Admin → Settings → Connectors. You’ll see a clean interface listing available AI providers with their connection status.
Step 2: Add your first AI provider
Click “Add Connection” and select your provider. For this walkthrough, let’s start with Anthropic (Claude).
You’ll need your API key from the provider. For Anthropic, you get this from console.anthropic.com under API Keys. Paste the key into the field, give the connection a name (like “Claude Production”), and click Save.
WordPress will test the connection and show a green checkmark if it’s working.
Step 3: Add additional providers
Repeat for OpenAI (api key from platform.openai.com) and Google Gemini (api key from aistudio.google.com) if you want multiple providers available.
The point of having multiple providers isn’t redundancy — it’s flexibility. Some plugins may work better with specific models. Rank Math’s Content AI might use OpenAI for SEO analysis while your chatbot plugin uses Claude for customer conversations. With the centralized Connectors system, both plugins pull from the same API keys without you configuring anything twice.
Step 4: Verify plugin compatibility
After setting up your connections, check which of your existing AI plugins are already compatible with the new system. Plugins that have been updated for WordPress 7.0 will automatically detect your configured providers and stop asking for separate API keys.
As of launch, early adopters include AI Engine (which already supported multiple providers), Rank Math, and Jetpack AI. More will follow quickly after launch.
What this means for different types of WordPress users
If you run a blog or content site
The immediate benefit is simplified API key management. But the bigger benefit comes over the next 6-12 months as plugins start building on the Abilities API. Imagine your SEO plugin automatically discovering that you have an image generation connection and offering to create featured images during content creation — without any configuration on your part.
The practical step right now: set up at least one AI provider connection after updating. Even if you don’t use any AI plugins today, having the infrastructure ready means you’re prepared when you install one later.
If you run a WooCommerce store
AI chatbots that understand your product catalog, automated product descriptions, and intelligent search are all getting easier to build. The Abilities API means a chatbot plugin can discover your WooCommerce products, categories, and inventory without the chatbot developer needing to write WooCommerce-specific code.
The practical step: if you’re running an AI chatbot like Tidio, MxChat, or AI Engine’s chatbot feature, watch for updates that leverage the new Connectors system. This should reduce API costs (centralized rate limiting) and improve response quality (plugins can share context more efficiently).
If you’re a developer or agency
This is where WordPress 7.0 gets genuinely exciting. The Abilities API opens a new category of plugin development. Instead of building AI features from scratch, you can register abilities and let any AI client use them. A plugin that generates social media posts from WordPress content, for example, only needs to register a “generate_social_post” ability — it doesn’t need to build its own ChatGPT integration.
The practical step: start reading the WordPress 7.0 Developer Notes. The AI Client SDK documentation is on GitHub (WordPress/php-ai-client). If you’re building plugins today, require the SDK via Composer as a package dependency so you can ship AI features immediately and transition cleanly when WordPress 7.0 becomes your minimum supported version.
If you manage client sites
The centralized Connectors system is a big quality-of-life improvement for agencies managing many sites. Instead of tracking which API keys are configured in which plugins across dozens of client sites, you’ll have one standard location. This also makes it easier to audit AI usage and costs across your portfolio.
The practical step: standardize on one or two AI providers across your client sites. Set up a process for configuring the Connectors page as part of your WordPress 7.0 migration checklist.
What you need to do before April 9
Check your PHP version (this is critical)
WordPress 7.0 drops support for PHP 7.2 and 7.3. The new minimum is PHP 7.4, and the core team recommends PHP 8.3 or higher for best performance and security.
For the AI features specifically, PHP 8.2 or higher is recommended. Some AI Client SDK features may not work optimally on older PHP versions.
How to check: go to WP-Admin → Tools → Site Health → Info → Server. Your PHP version is listed there. If you’re on 7.2 or 7.3, contact your hosting provider about upgrading — or better yet, set up a staging environment and test PHP 8.3 before touching production.
Most modern managed hosts (like Raidboxes, Cloudways, Kinsta, WP Engine) already default to PHP 8.1 or higher. If your host doesn’t offer PHP 8.2+, it might be time to switch.
Test on a staging site first
This is a major release. The block editor now runs in an iframe by default (improving style isolation but potentially breaking plugins that inject CSS into the editor). React has been upgraded to version 19. The admin UI has been partially redesigned with DataViews replacing traditional list tables.
Any of these changes could affect your plugins or custom theme code. Set up a staging environment, update to WordPress 7.0, and test every critical workflow before updating your live site.
Audit your current AI plugins
Make a list of every AI plugin you’re currently running. Check each one for WordPress 7.0 compatibility. Some plugins may need updates to work with the iframed editor or React 19 changes. Plugins that already use the WP AI Client SDK (either the standalone plugin or the Composer package) should transition smoothly.
Get your API keys ready
If you don’t already have API accounts with the AI providers you want to use, set them up now. You’ll want at least one of the following ready to go on update day: an OpenAI API key (platform.openai.com), an Anthropic API key (console.anthropic.com), or a Google AI API key (aistudio.google.com).
Each provider has different pricing models. OpenAI charges per token with different rates per model. Anthropic charges per token with input and output priced separately. Google offers a generous free tier for Gemini. Compare pricing based on your expected usage before committing.
The bigger picture: why this matters beyond WordPress 7.0
WordPress 7.0 isn’t just adding AI features. It’s building infrastructure.
The distinction matters. Adding AI features means shipping a built-in writing assistant or image generator that works for a while and then gets outdated. Building AI infrastructure means creating the plumbing that lets anyone build AI features that evolve with the technology.
The Abilities API and MCP adapter mean that as AI models improve — as Claude gets smarter, as GPT models get faster, as new providers emerge — WordPress sites automatically benefit. The infrastructure is model-agnostic and provider-agnostic by design.
WordPress 7.1 (tentatively scheduled for August 2026) and 7.2 (December 2026) will likely expand on this foundation. Expect deeper Gutenberg integration, more first-party abilities, and potentially AI-assisted collaboration features built on top of the Phase 3 real-time editing system.
For anyone who has been waiting to see how AI fits into WordPress, the answer is now clear: it fits into the core, as infrastructure, available to every plugin and theme. And it starts on April 9.
Frequently asked questions
Does WordPress 7.0 include a built-in AI writing assistant? No. WordPress 7.0 provides the infrastructure (AI Client SDK, Connectors UI, Abilities API) that lets plugins build AI features. It doesn’t ship with its own writing assistant, image generator, or chatbot. You’ll still need plugins like Jetpack AI, AI Engine, or Rank Math Content AI for specific AI features — but those plugins will now work through a unified system.
Will my existing AI plugins break after updating? Most won’t break, but some may need updates. The biggest compatibility concerns are the React 19 upgrade and the iframed editor, not the AI features specifically. Check with each plugin developer for WordPress 7.0 compatibility before updating.
Do I need to pay for AI API access? Yes. WordPress 7.0 provides the connection infrastructure, but the AI processing happens on the provider’s servers. You’ll need API accounts with OpenAI, Anthropic, Google, or whichever providers your plugins use. Costs depend on usage volume and which models you use.
Can I use locally hosted AI models? The AI Client SDK is designed to be provider-agnostic. While the three default providers are cloud-based (OpenAI, Anthropic, Google), the extensible registry system means plugins can register local AI providers as well. AI Engine already supports this for users with the technical setup.
What if I don’t want to use any AI features? You don’t have to. The AI infrastructure is part of core but doesn’t do anything until you configure a provider connection and install a plugin that uses it. If you never visit the Connectors page, your WordPress site works exactly as before — just with the real-time collaboration features, admin redesign, and other non-AI improvements that WordPress 7.0 brings.
