WordPress 7.0 drops April 9, 2026, making history as the first major CMS with native AI integration. Release Candidate 1 ships March 19, giving developers two weeks to test the php-ai-client SDK that brings OpenAI, Anthropic Claude, and Google Gemini directly into WordPress core—no third-party plugins required. For a platform powering 43% of the web, this architectural shift eliminates credential fragmentation and establishes AI as platform-level infrastructure, not an afterthought.
Solving the Plugin Fragmentation Nightmare
Before WordPress 7.0, site owners juggled the same API keys across three or four different plugins, each managing credentials in its own silo. The security implications were grim: 11,334 new WordPress vulnerabilities surfaced in 2025 alone, a 42% jump from 2024. Average exploit time dropped from 72 hours to under 6 hours. The plugin ecosystem’s fragmentation wasn’t just inconvenient—it was actively dangerous.
WordPress 7.0 fixes this with the php-ai-client SDK, a shared PHP library that standardizes AI communication across the platform. Developers write features once against this unified interface, then switch between OpenAI, Claude, and Gemini via configuration changes—no code rewrites. Credentials live in WordPress Core’s new Connectors screen, eliminating duplicate key management and reducing the attack surface. It’s standardization as security strategy.
How the php-ai-client SDK Works
The architecture is deliberately simple. Three official provider plugins—AI Provider for OpenAI, AI Provider for Anthropic, and AI Provider for Google—sit in the WordPress Plugin Directory. Install one, add your API key through the centralized Connectors interface, and you’re live. The php-ai-client SDK handles the rest through a fluent interface:
AiClient::prompt('Summarize this post')->generateText();Behind that clean API: PSR-14 event dispatching for lifecycle monitoring, PSR-compatible HTTP clients backed by wp_remote_request(), and dynamic model discovery from provider APIs. Switch from GPT to Claude by changing a config value. No vendor lock-in, no architectural debt.
The SDK ships in WordPress 7.0 by default, requiring only PHP 7.4 or higher. Developers praised the approach: “The progression from MCP access to OAuth 2.1 to an official connector in just a few months is impressive. The read-only approach is smart for a first release—it builds trust before opening write access.”
What Developers Can Build
The practical applications hit immediately. Inline text generation in Gutenberg lets users highlight content and adjust tone or length without leaving the editor—Kadence Blocks already demonstrates this with context-aware AI suggestions. The Nexter Blocks plugin showcases AI repeater auto-fill: one prompt populates a six-card testimonial grid or full FAQ accordion. AI Editor takes natural language commands like “add a three-column features section about our product benefits” and generates layouts with placeholder content ready to refine.
Beyond content generation, the SDK enables smart content moderation, AI-powered post summaries, automatic SEO optimization, and chatbots built against WordPress APIs. Because the interface is provider-agnostic, developers focus on features instead of wrestling with OpenAI versus Anthropic API differences. Write once, deploy across providers based on cost, performance, or user preference.
The WordPress AI Experiments plugin (version 0.5.0 launched March 12) shows core team priorities: excerpt generation, integrated testing for the Connectors interface, and upcoming Ollama support for local models. The vision extends beyond hosted APIs to on-premise AI, privacy-first deployments, and developer choice.
Why This Matters for 43% of the Web
WordPress’s decision to bake AI into core—not as a feature, but as infrastructure—carries weight because of its market share. When 43% of the web gains standardized AI capabilities, the ecosystem shifts. Existing AI plugins will migrate to php-ai-client or face obsolescence. New plugins will launch with multi-provider support from day one. Enterprise adoption, long hesitant due to fragmentation and security concerns, now has a trusted foundation.
The open source advantage is stark. Proprietary CMS platforms can add AI features, but WordPress just standardized AI infrastructure for the entire ecosystem. That’s not incremental improvement—it’s architectural leverage. Plugin developers get cross-compatibility without negotiation. Site owners get provider choice without technical complexity. The 43% of the web running WordPress doesn’t just get AI features; it gets AI optionality.
Getting Started
Beta 3 is live now for early testing. Release Candidate 1 drops March 19, with the final WordPress 7.0 release on April 9. Developers can install provider plugins from WordPress.org, add API keys via the Connectors screen, and start building against the php-ai-client interface today. The GitHub repositories for php-ai-client and wp-ai-client include documentation, code examples, and integration guides.
WordPress just solved a problem it helped create. The plugin fragmentation that made WordPress extensible also made it vulnerable. Now, native AI integration offers a path forward: standardization without stagnation, flexibility without chaos. For developers tired of managing duplicate credentials and incompatible implementations, April 9 is worth watching.
