WordPress 7.0 was supposed to ship this week. It didn't. The release has been pushed back three to four weeks while the WordPress core team stabilizes a feature that isn't ready — and the AI features that everyone's been talking about aren't the problem.
Here's what happened, what it means for you, and what you should be doing with the extra time.
What Caused the Delay
On March 31, the WordPress core team published "Extending the 7.0 Cycle." The decision came after conversations between Matias Ventura and project leadership about the stability of one specific feature: Real-Time Collaboration.
Real-Time Collaboration introduces a new database table and fundamentally changes how WordPress handles editing sessions. When multiple users edit the same post simultaneously, the system needs to synchronize changes without corrupting data or tanking performance. Testing revealed that active collaboration sessions disable persistent post caches — a performance issue the team wasn't willing to ship.
Matt Mullenweg called for "extreme stability." So the release was extended.
No new date has been set. Based on the three-to-four week estimate and the scope of the remaining work, late April to early May is the realistic window.
What Did NOT Cause the Delay
This is the part that gets lost in the headlines.
WordPress 7.0's AI features — the ones that generated the most anticipation — are not cited as reasons for the delay. The AI Client, Abilities API, MCP Adapter, and Connectors Screen all made it through the beta and release candidate phases without the stability concerns that plagued Real-Time Collaboration.
That's notable. The AI infrastructure passed the same quality bar that the collaboration features couldn't clear. If you've been wondering whether WordPress's first native AI features are ready for production, the answer from the WordPress core team's own release process is: yes. The question was never the AI. It was everything else.
We published a deep technical analysis of the AI architecture if you want to understand what's actually shipping — and we'll be going even deeper on the AI Client, Abilities API, and MCP Adapter in an upcoming piece:
What WordPress Chose (And What It Says About Them)
WordPress chose stability over shipping. That's worth acknowledging.
In the same week, Anthropic accidentally leaked 512,000 lines of Claude Code source code — the second leak in two months — because their release cycle moved faster than their security processes could keep up. The contrast is stark: one organization said "this isn't ready, we're waiting" and the other shipped fast enough to publish their internal codebase to npm.
Neither approach is wrong in the abstract. But if you're running production WordPress sites — especially for clients — the "extreme stability" approach is what you want from your CMS core.
What Agencies Should Do Right Now
The delay gives you a window that most agencies will waste. Don't be most agencies.
Brief your clients before they Google it. Your clients will hear about the delay. The agencies that look competent are the ones who told their clients first, with a plan. Two paragraphs explaining the delay and your approach sends a trust signal worth more than any technical deliverable.
Audit your plugin stack. The most common WordPress update disaster isn't a core bug — it's a plugin that isn't compatible. Use the delay to check compatibility, maintenance status, and known conflicts across your entire client portfolio. Document it now. When 7.0 ships, you update the ones that are ready and hold the ones that aren't.
Set up staging environments. If you don't have staging for every client site, the delay is your window to fix that. Every major host offers one-click staging. There's no excuse for testing a major version update on production.
We're publishing a full agency preparation playbook next — five specific things you should be doing with this window, including how to evaluate the AI features and what to do about the one thing WordPress 7.0 doesn't fix.
Full disclosure: we build wpRag, an AI search plugin for WordPress, so we've been living inside WordPress 7.0's AI architecture for months. The engineering assessment in Article 1? That's us going deep because it's literally our domain. Here's the thing we keep coming back to: WordPress 7.0 gives your site an AI brain. It doesn't give it AI search. More on that in the agency playbook.
What Marketers Should Do
Plan for a bigger traffic spike. When WordPress 7.0 eventually ships, the pent-up demand from the delay will amplify the launch coverage. If you're planning content around WordPress 7.0, keep producing — but don't publish your "Release Day Guide" until you have an actual release day. Publish your analysis, your preparation guides, your "what it means for X" pieces now. Save the definitive guide for launch.
Revisit your content freshness. Here's a data point that should change your planning: 50% of content cited by AI search engines is less than 13 weeks old. AI systems are biased toward recently-updated content — they even auto-append "2026" to 28% of queries that don't include a year. If your WordPress 7.0 content goes stale during the delay, it may not get cited when the release actually happens. Keep it updated.
Test AI features on staging. WordPress 7.0 RC2 is available. You can install it on a staging site today and test the AI features. When the release ships, you'll have hands-on experience instead of theoretical knowledge.
What Site Owners Should Do
Don't panic. The delay doesn't affect your current site. WordPress 6.x continues to work exactly as it does today.
Do update PHP. WordPress 7.0 requires PHP 8.1 or higher. If your host is still running PHP 7.4 or 8.0, the delay gives you time to migrate. Check with your hosting provider — most offer one-click PHP version changes.
Do review your hosting. If you've been on shared hosting and your site has grown, the 7.0 update is a natural moment to evaluate whether your hosting matches your needs. The new Real-Time Collaboration features (when they ship) will perform better on hosts with modern infrastructure.
The Opportunity
The delay is uncomfortable for the WordPress community but strategically favorable for anyone willing to prepare. When WordPress 7.0 ships — and it will ship — the organizations that used this window to audit, stage, learn, and prepare will deploy confidently on day one. Everyone else will be reading "How to safely update to WordPress 7.0" guides on day three.
You have three to four weeks. Use them.
This is Article 2 in our WordPress 7.0 series. Read Article 1: Engineering Assessment for the full technical analysis of what's shipping.
Next: The agency preparation playbook — 5 things every agency should do before WordPress 7.0 ships.