WordPress 7.0 will not ship on April 9, 2026. The release team announced a delay on March 31, pushing the most significant WordPress update since the block editor into an uncertain timeline. If your business runs on WordPress, this changes your planning. Here is what happened, why it matters, and what you should do right now.
WordCamp Asia 2026 opened today in Mumbai with over 3,000 attendees. The event was supposed to host the first live WordPress release at a WordCamp. Instead, organizers replaced the launch with a panel discussion and a community testing session. The release everyone waited for became a conversation about the release everyone is still waiting for.
Why WordPress 7.0 Was Delayed
The delay comes down to one feature: real-time collaboration. WordPress 7.0 introduces the ability for multiple users to edit the same post simultaneously, similar to Google Docs. The technical foundation for this feature relies on how WordPress stores editing data.
The original approach used post meta, a standard WordPress storage method. During testing, contributors discovered this caused cache invalidation problems at scale. The core team concluded that a new dedicated database table was needed instead.
Matias Ventura, WordPress 7.0 release lead, announced the decision on March 31. He described it as a delay of a few weeks, not months. A revised release schedule will be published by April 22, 2026.
No new features will be added during this extension. The delay is about getting the architecture right for a feature that will affect every WordPress site running collaborative workflows.
What WordPress 7.0 Actually Includes
This is not a routine update. WordPress 7.0 marks the start of Gutenberg Phase 3, the collaboration phase. It is the most architecturally significant release since the block editor arrived in WordPress 5.0 in 2018.
Three headline features define this release:
Real-time collaboration. Multiple users editing the same content simultaneously, with presence indicators and conflict resolution built into the editor. This removes the need to draft in Google Docs and paste into WordPress.
Native AI infrastructure. The Abilities API lets AI services understand what capabilities a WordPress site supports. The AI Client Connectors interface provides a centralized settings screen for connecting providers like OpenAI, Anthropic, and Google. Previously, every AI plugin managed its own configuration.
The MCP Adapter. Model Context Protocol support means AI agents can interact with WordPress directly. Not through hacks or workarounds, but through a standardized protocol that WordPress core supports natively.
On top of that, WordPress 7.0 drops support for PHP 7.2 and 7.3. The new minimum is PHP 7.4.
What Happened at WordCamp Asia Instead
WordCamp Asia 2026 runs April 9 to 11 at the Jio World Convention Centre in Mumbai. The three-day structure remained intact despite the release delay.
Contributor Day (April 9) replaced the live release celebration with a WordPress 7.0 panel discussion and Q&A session. Attendees can test the latest Release Candidate build and interact directly with members of the release squad.
The conference portion (April 10-11) features sessions across three tracks: Foundation, Growth, and Enterprise. James LePage, Automattic’s Head of AI, delivers the keynote on how AI is being integrated into WordPress core. Matt Mullenweg, WordPress co-founder, speaks on the final day.
AI is the dominant theme across the schedule. Sessions cover MCP integration, AI agents for WordPress, AI-powered testing pipelines, and the intersection of AI with content strategy. WordCamp Asia is signaling where WordPress is headed, even if the software itself is not ready yet.
Why This Delay Is Good News for Your Business
A delayed release with solid architecture beats an on-time release with technical debt. Here is why this matters for businesses specifically.
You get more preparation time. WordPress 7.0 introduces database migrations. That is different from a standard update. If you manage client sites or run an e-commerce store, you need staging environment testing before updating production. The delay gives you weeks to get that infrastructure ready.
The collaboration feature will actually work. Real-time editing is only useful if the data layer behind it is reliable. Shipping a collaboration feature on a storage system that breaks caching would have created more problems than it solved. The core team made the right call.
The AI infrastructure is still coming. The Abilities API and MCP Adapter are not affected by the delay. These features are ready. When WordPress 7.0 ships, your site will be able to connect to AI services through a standardized, core-supported interface for the first time.
The Cloudflare Factor You Should Know About
The same week WordPress announced its delay, Cloudflare launched EmDash. It is a TypeScript CMS built in two months using agentic AI, released under the MIT license. Cloudflare described it as a “spiritual successor” to WordPress.
Joost de Valk, former CEO of Yoast and one of WordPress’s most prominent critics in recent years, is among EmDash’s early supporters.
This is not a direct threat to WordPress today. EmDash is a brand new product with no ecosystem, no plugin library, and no decade of community development behind it. But it signals something important: competitors are watching WordPress’s AI gap and building alternatives that are AI-native from day one.
WordPress 7.0’s AI features, the Abilities API, the MCP Adapter, and the AI Client Connectors, are the answer to this competitive pressure. The delay to get collaboration right does not change the AI roadmap. If anything, it shows the WordPress core team is prioritizing quality over speed, which is exactly what enterprise users need to see.
What You Should Do Right Now
The delay creates a preparation window. Use it. Here is a practical checklist:
Check your PHP version. WordPress 7.0 requires PHP 7.4 minimum. Sites running PHP 7.2 or 7.3 will not receive the automatic update. They will stay on the 6.9 branch. Contact your hosting provider or check your dashboard under Tools > Site Health.
Set up a staging environment. If you do not have one, create it now. Most managed WordPress hosts offer one-click staging. You will need it to test the 7.0 update before pushing to production.
Audit your page builder dependency. WordPress 7.0 pushes further toward Gutenberg-native block editing. If your site relies on Elementor, Divi, or another JavaScript-heavy page builder, check compatibility with the 7.0 Release Candidate. Test on staging, not production.
Check your robots.txt for AI crawlers. This is independent of the 7.0 timeline, and you can do it today. Open your robots.txt file and look for GPTBot, ClaudeBot, and PerplexityBot. If they are not listed, AI systems cannot crawl your site. Semrush found that sites with AI crawler access see citations appear 3 to 4 weeks faster.
Review your structured data. WordPress 7.0’s AI features work best on sites that already have clean JSON-LD schema markup. Schema App reported a 19.72% increase in AI Overview visibility after implementing entity-linking. Start with Organization, Person, and Service schemas.
The Timeline Going Forward
Here is what we know as of April 9, 2026:
- WordPress 6.9.4 is the current stable release
- WordPress 7.0 RC2 is available for testing only (do not install on production)
- A revised release schedule will be announced by April 22, 2026
- The delay is described as “a few weeks,” suggesting a late April or May release
- WordCamp Asia sessions (April 10-11) will provide additional clarity on the release direction
We will update this article as new information becomes available. Follow the official release schedule at make.wordpress.org/core.
FAQ
When will WordPress 7.0 be released?
The original April 9, 2026 date has been postponed. The WordPress core team will publish a revised schedule by April 22, 2026. Based on the “few weeks” language used by release lead Matias Ventura, a late April or May 2026 release is the most likely outcome.
Why was WordPress 7.0 delayed?
The real-time collaboration feature required a change in database architecture. The original post meta approach caused cache invalidation issues at scale. A new dedicated database table is being implemented to support collaborative editing reliably.
Should I install WordPress 7.0 RC2 on my live site?
No. Release Candidate builds are for testing only. Install RC2 on a staging environment to check plugin compatibility and site behavior, but keep your production site on WordPress 6.9.4 until the final stable release ships.
Does the delay affect the AI features in WordPress 7.0?
No. The Abilities API, MCP Adapter, and AI Client Connectors are not related to the collaboration delay. These features remain part of the WordPress 7.0 release and are ready for deployment when the final version ships.
How do I prepare my WordPress site for the 7.0 update?
Start with three steps: verify your PHP version is 7.4 or higher, set up a staging environment for testing, and audit your site’s plugin compatibility with the RC2 build. Also check that your robots.txt allows AI crawlers (GPTBot, ClaudeBot, PerplexityBot) and review your structured data implementation.
Your WordPress Site Needs to Be Ready Before 7.0 Ships
WordPress 7.0 will bring native AI infrastructure to every WordPress site. The Abilities API, the MCP Adapter, and real-time collaboration are not optional upgrades. They represent a new foundation for how WordPress works.
If your site runs on a legacy theme, a JavaScript-heavy page builder, or an outdated PHP version, the 7.0 update will be disruptive instead of transformative. The delay gives you time to fix that.
We specialize in preparing WordPress sites for this transition. Our WordPress 7 Migration service covers PHP updates, Gutenberg-native rebuilds, structured data implementation, and AI crawler configuration. Every site we ship is server-side rendered, schema-rich, and visible to both search engines and AI systems.
Prefer to write? Send us a message and we will get back to you within 24 hours.
About the Author
Kevin Pantanella is the founder of Suzaku Productions, a Bangkok-based WordPress agency specializing in AI-native WordPress development. With over 12 years of WordPress experience, Kevin helps businesses across Thailand, Singapore, Hong Kong, and Europe build websites designed for both human visitors and AI systems.
Last Updated: April 10, 2026
