WordPress 7.0 is the biggest release in years. The core team has been shipping announcements almost daily through March 2026, the Connectors API, Pattern Overrides, MCP server support, AI agent integration, and a delayed Release Candidate that is giving the community more time to prepare than usual. If you have been watching the make.wordpress.org posts pile up and wondering what actually matters, this guide covers every significant feature in plain language, from what it is to what it means for your site.
The RC delay is actually good news for site owners. It means the release is being held to the right standard, and it means there is time to understand what is coming before it lands on your site. Use that time now.
What Is WordPress 7.0?
WordPress 7.0 is a major release, the kind that bumps the first version number, not just the second. These happen roughly every several years and carry significantly more architectural change than standard point releases. WordPress 6.x was defined by the block editor maturing: Full Site Editing, synced patterns, theme.json, block bindings. WordPress 7.0 is defined by WordPress connecting to the outside world, AI systems, external services, developer tooling, and the broader ecosystem of software that surrounds modern websites.
The headline new features are: the Connectors API, Pattern Overrides stabilization, native MCP server support, and AI agent integration. Behind those headlines are dozens of smaller improvements to performance, the block editor, developer APIs, and site management. This guide covers all of it, starting with the biggest additions.
The Connectors API: WordPress Talks to Everything
The Connectors API is the feature with the broadest long-term impact of anything in WordPress 7.0. It provides a standardized framework for connecting WordPress to external services, CRMs, payment processors, email platforms, analytics tools, inventory systems, in a way that is built into WordPress core rather than bolted on by each plugin individually.
The Problem It Solves
Right now, every plugin that connects WordPress to an external service has to build its own connection management. OAuth flows, API key storage, credential validation, webhook handling, error recovery, each plugin reinvents this from scratch. That is why your WordPress admin has five different “Connect to [Service]” sections with five different UIs, five different credential storage approaches, and five different ways of handling authentication failures.
The Connectors API standardizes the entire layer. One connection management UI in the WordPress admin, one credential storage model, one authentication flow pattern. Plugins register as connectors and consume the framework instead of building their own. For site owners, this means fewer broken integrations, clearer connection status across all services, and a single place to audit what external services your site is talking to.
What It Means for Plugin Developers
For developers, the Connectors API provides a set of registration functions and hooks that handle the authentication layer while the plugin focuses on what to do with the connection. The WordPress REST API remains the transport layer for data moving between WordPress and external services, the Connectors API handles the authorization and credential management that sits in front of those requests.
Third-party services can also register as connectors, making their APIs first-class citizens in the WordPress connection ecosystem. Expect the major SaaS platforms, HubSpot, Mailchimp, Stripe, Salesforce, to ship official WordPress 7.0 connector plugins shortly after release, replacing their current custom integration UIs with the standardized connector model.
What Site Owners Should Do Now
If your site has multiple service integrations, a CRM, an email platform, a payment processor, an analytics tool, audit your current integrations before updating to 7.0. Some plugin authors will migrate to the Connectors API immediately; others will take time. You may have a period where some integrations use the new system and some use their existing custom connection management. The transition should be seamless for end users, but it is worth knowing what integrations your site depends on before a major update.
Pattern Overrides: Synced Patterns That Actually Work for Clients
Pattern Overrides were introduced in WordPress 6.6 and reach their stable, production-ready form in 7.0. The short version: synced patterns (reusable design components) can now have some parts that are customizable per-instance while the rest of the layout stays globally consistent.
Before this, synced patterns had an all-or-nothing problem. Either every instance of a team member card, testimonial, or pricing tier was identical (not useful for content), or you broke sync entirely and each instance became fully independent (not useful for design consistency). Pattern Overrides eliminate the trade-off. The card layout is locked and synced everywhere; the photo, name, title, and bio are overrideable per-instance.
In WordPress 7.0 specifically, Pattern Overrides add support for more block types (Image gains additional attribute overrides, Button gains more CTA-level customization), the Block Bindings APIs that power overrides are fully stabilized out of experimental status, and the Site Editor now marks pattern instances that have active overrides so you can audit customizations at a glance.
For block theme developers and agencies delivering client sites, this is the feature that makes the Site Editor practical for content-heavy designs. Build your components as synced patterns with the right override bindings, update the design once, content stays in place everywhere.
MCP Server Support: AI Tools Can Now Talk to WordPress
MCP (Model Context Protocol) is an open standard originally developed by Anthropic that allows AI coding agents and AI assistants to connect to external tools and data sources in a standardized way. In plain language: it is a protocol that lets an AI assistant reach out to your WordPress site, read data, and take actions, without requiring custom integration code for every AI tool.
What WordPress Core Is Shipping
WordPress 7.0 ships with two significant MCP implementations. First, the WordPress Playground MCP Server: WordPress Playground (the browser-based WordPress sandbox that runs entirely in WebAssembly) now exposes an MCP server that AI coding agents can connect to. This means tools like Claude Code or Cursor can spin up a WordPress instance, install plugins, run tests, and verify changes, all inside the isolated Playground environment without touching a real server.
Second, the Plugin Directory MCP Server: the WordPress.org plugin repository now exposes an MCP server. AI agents can query plugin data, active installs, version history, changelog, compatibility information, open support threads, directly. A developer asking an AI agent to audit their plugin’s dependencies or check compatibility with a specific WordPress version can now get answers from the actual Plugin Directory data rather than from whatever the AI was trained on.
What This Means for WordPress Developers
For developers using AI-powered development tools, the MCP integrations mean WordPress becomes a first-class citizen in AI-assisted workflows. Instead of pasting code into chat windows and hoping the AI’s training data included the right WordPress version, agents can query live WordPress data, test against real WordPress behavior in Playground, and pull accurate plugin information from the directory.
The practical impact starts immediately for plugin developers and grows as AI tooling matures. Teams that already use AI coding agents in their WordPress development workflow will feel the difference first. Site owners who do not write code will benefit indirectly as the tools their developers use get smarter about WordPress-specific context.
Self-Hosted vs WordPress.com
The WordPress.org MCP implementations (Playground and Plugin Directory) are developer infrastructure, they do not expose your site’s content or data to AI tools by default. They are services that AI agents can query to understand WordPress as a platform, not hooks into your specific site. Connecting an AI agent to a specific self-hosted WordPress site would require a separate site-level MCP implementation, which third-party plugin developers are beginning to ship.
AI Agents in WordPress: What Is Actually Shipping
TechCrunch covered WordPress.com’s announcement on March 20 that the hosted platform now lets AI agents write and publish posts. This generated significant discussion in the WordPress community about what it means for self-hosted WordPress, content quality, and the future of the CMS. Here is a clear-eyed breakdown of what is actually shipping and what it means.
WordPress.com AI Agents
WordPress.com (the hosted platform run by Automattic, not the open-source software at WordPress.org) has integrated AI agents that can draft posts, generate images, optimize for SEO, and publish, operating with varying levels of human review depending on how you configure them. This is a feature of the WordPress.com subscription service, not of WordPress core itself. If you run a self-hosted WordPress site on your own hosting, this is not something that is automatically added to your site.
What WordPress Core (WordPress.org) Is Adding
WordPress 7.0 core adds the infrastructure that makes AI agent integration possible, the Connectors API for service authentication, the MCP server support for AI tool connectivity, and REST API improvements that make programmatic WordPress interaction more reliable. The core does not ship a specific AI content agent. Third-party plugins build on the core infrastructure to deliver AI features.
If you want AI content capabilities on a self-hosted WordPress 7.0 site, you install a plugin that uses the Connectors API to authenticate with an AI service (OpenAI, Anthropic, Google Gemini) and the Block Bindings API to integrate AI-generated content with Gutenberg. Several plugins in this space are already in active development timed to the 7.0 release.
The Human Review Question
The most important decision for any site using AI content agents is where human review sits in the workflow. WordPress 7.0 makes agent-to-WordPress publishing more capable, it does not make it more advisable to publish without review. AI-generated content that bypasses editorial judgment carries reputational and SEO risk that no amount of technical sophistication eliminates. The infrastructure is neutral; the workflow decisions are yours.
Block Editor and Full Site Editing Improvements
WordPress 7.0 ships a significant round of Block Editor improvements that have been accumulating since 6.7. The most impactful for everyday site management:
Improved Template Part Management
The Site Editor’s template part management, headers, footers, sidebars, and other reusable template sections, gets a revised UI that makes it easier to see which template parts are used on which templates, preview changes before applying them globally, and revert template parts to their theme defaults. For block theme users who have been frustrated by the difficulty of tracking what changed where, this is a meaningful quality-of-life improvement.
Style Variations at the Block Level
Theme authors can now register style variations at the block level via theme.json, not just at the global level. This means a theme can offer multiple visual treatments for a specific block, different card layouts, different button styles, different heading treatments, and users can switch between them from the block inspector without affecting other blocks of the same type. Previously this required either multiple registered block styles or manual CSS customization.
Zoom Out Mode Enhancements
Zoom Out mode, which lets you view and rearrange full-page sections at a reduced scale, gets significant improvements in WordPress 7.0. Pattern insertion and section rearrangement in Zoom Out mode is now more reliable, the mode correctly handles nested template parts, and the transition between Zoom Out and normal editing is smoother. This makes Zoom Out genuinely useful for page-level layout work rather than primarily a visual curiosity.
Font Library Improvements
The Font Library (introduced in WordPress 6.5) gets a round of improvements in 7.0: better Google Fonts browsing, reliable local font upload with proper format validation, and font previews that reflect your theme’s current color settings rather than generic defaults. Variable font support is also expanded for themes that use variable fonts in their design system.
Performance Improvements
WordPress 7.0 continues the performance trajectory that the core team has been building since 6.3. The improvements in this release focus on three areas:
Autoloaded Options Cleanup
One of the most common performance problems on WordPress sites is an oversized wp_options table with too many autoloaded options, data that WordPress loads on every page request regardless of whether it is needed. WordPress 7.0 includes a tool in the admin (under Tools → Site Health) that identifies autoloaded options exceeding recommended thresholds and suggests remediation steps. It also changes the default autoload behavior for new plugin options, making autoload: no the safe default unless explicitly set to yes.
Block Rendering Performance
The block rendering pipeline gets a significant optimization in WordPress 7.0, particularly for pages with many block types or deeply nested block structures. The PHP-side block parser has been optimized to reduce memory allocation per block, and blocks that share attributes (common in template parts reused across many pages) benefit from improved caching of parsed attribute data.
Improved Object Cache Integration
WordPress 7.0 expands the data that the core object cache covers, reducing database queries for common operations. User capability checks, term relationship lookups, and post meta retrievals all benefit from improved cache coverage. Sites running a persistent object cache (Redis, Memcached) will see the largest gains; sites running the default in-memory cache get smaller improvements from reduced redundant computation within a single request.
Developer API Changes
Block Bindings API, Stable
The Block Bindings API, which allows block attributes to pull values from registered data sources, moves out of experimental status in WordPress 7.0. The API for registering custom binding sources (register_block_bindings_source()) is now stable and part of the public API surface. Plugins and themes that built on the experimental version need to check the 7.0 migration guide for any naming changes, but the core functionality is stable and safe to build on for production use.
Interactivity API Enhancements
The Interactivity API, WordPress’s framework for adding client-side interactivity to blocks without loading a full JavaScript framework, gets expanded directive support and improved server-side rendering integration in WordPress 7.0. The additions make it practical to build more complex interactive experiences (multi-step forms, dynamic filtering, real-time data display) without dropping back to custom JavaScript outside the Interactivity API framework.
PHP 8.2 and 8.3 Optimization
WordPress 7.0 raises the recommended PHP version to 8.2 and is tested against 8.3. The codebase has been updated to take advantage of PHP 8.x improvements, readonly properties, intersection types, fibers for async-style programming in applicable areas, and removes legacy code paths that were maintained for PHP 7.x compatibility. If your site is still running PHP 7.4, 7.0 is a strong signal to plan that upgrade.
Deprecated Functions, What to Check
WordPress 7.0 deprecates a set of functions that have had documented alternatives for several major versions. The most impactful for plugin developers: several functions related to the old widgets system, a handful of media upload functions that predate the Media Library, and some query functions with cleaner WP_Query equivalents. Run your plugin code through a static analysis tool against the WordPress 7.0 stubs before the release to catch deprecation warnings before they become notices in production.
How to Prepare Your Site for WordPress 7.0
A major version update warrants more careful preparation than a standard security release. The steps below apply to any site, regardless of size or complexity.
1. Verify Your PHP Version
Check your hosting control panel or ask your host what PHP version your site is running. WordPress 7.0 requires PHP 7.4 minimum but strongly recommends 8.2. If you are on 7.4 or 8.0, plan a PHP upgrade alongside or before the WordPress update. Most managed WordPress hosts handle PHP updates on request or automatically; self-managed VPS users need to schedule this explicitly.
2. Update Plugins and Themes First
Before updating WordPress core to 7.0, update all your plugins and themes to their latest versions. Plugin authors have been releasing 7.0 compatibility updates as the beta cycle progressed. Running outdated plugins against a new major WordPress release is the most common cause of post-update problems.
3. Test on Staging
Test the full update on a staging copy of your site before updating production. For WooCommerce stores, membership sites, or any site where downtime has revenue impact, staging testing is not optional. Most managed hosting providers offer one-click staging environments. Test your checkout flow, forms, login, and any JavaScript-dependent features after the update. The update process itself is safe, but plugin compatibility issues can only be caught by testing your specific combination of plugins and theme.
4. Back Up Before You Update
A complete backup, files and database, immediately before updating gives you a clean rollback point if anything goes wrong. Even if your host provides automatic backups, take a manual snapshot immediately before the update so you have a clean restore point at the exact moment before the upgrade. The update itself takes under a minute; having a backup takes two minutes and eliminates the downside risk entirely.
5. Check Your Site Health After Updating
After updating to 7.0, go to Tools → Site Health in your WordPress admin. WordPress 7.0’s expanded health checks include the new autoloaded options analysis and PHP version recommendations. Review any warnings the health check surfaces and address them in priority order. A clean Site Health report is a good signal that your site is running well on the new version.
When Is WordPress 7.0 Being Released?
As of this writing (March 22, 2026), WordPress 7.0 is in the RC (Release Candidate) phase with a delayed timeline. The RC delay was announced on make.wordpress.org and attributed to quality threshold requirements, the core team is holding the release until the testing bar is met rather than shipping on a fixed calendar date. This is the right call and consistent with how previous major WordPress releases have been handled.
Based on the current Beta 6 status and typical RC-to-release timelines for major WordPress versions, a late March or early April 2026 release is the most likely window. Once the RC is declared stable, the release typically follows within one to two weeks. Watch the make.wordpress.org/core blog for the official release announcement. Subscribe to the WordPress news RSS feed or follow the official WordPress Twitter/X account for immediate notification.
For site owners on managed WordPress hosting, automatic updates may apply the 7.0 update as soon as it is released, depending on your host’s update policy. Check your hosting dashboard’s update settings before the release and configure the level of automatic updates you are comfortable with, core security updates only, or all major releases. For high-traffic or business-critical sites, manual update control is the safer default for major version updates.
Summary: What Matters Most in WordPress 7.0
Across everything in WordPress 7.0, the theme is connectivity. The platform is opening up, to external services through the Connectors API, to AI developer tooling through MCP server support, to AI content systems through improved programmatic access, and to the broader ecosystem of software that modern websites depend on. The block editor improvements and performance gains are meaningful but evolutionary; the connectivity features are genuinely new territory for WordPress.
For site owners, the immediate priorities are straightforward: verify your PHP version, update your plugins, test on staging, and update when the release lands. The new features do not require any immediate action, they become available when plugins start using the new APIs, which happens over the months following the core release.
For developers, the Connectors API and the stabilized Block Bindings and Interactivity APIs open up integration patterns that were significantly harder to build before. If you have been waiting for the APIs to stabilize before building on them, 7.0 is the release where that patience pays off.
The RC delay means you have a few more weeks before 7.0 lands on production sites. Use them to test, prepare, and understand what is coming. The release itself will be worth the wait.
ai block builder wordpress Block Editor WordPress 7.0
Last modified: March 22, 2026
