The way teams build websites is about to fundamentally change. WordPress 7.0, scheduled for release on April 9, 2026, introduces real-time multi-user editing to the platform that powers 43.5% of all websites, according to W3Techs. This isn’t an incremental update. It’s the beginning of Phase 3 in WordPress’s long-term development roadmap—a phase entirely focused on collaboration.
For years, WordPress has operated as what The Repository aptly calls “the solo editor model.” One person works on a page. Everyone else waits. That ends with 7.0.
What Phase 3 Actually Means for WordPress Development
Understanding where WordPress 7.0 fits requires looking at the journey that brought us here. WordPress 5.0 launched in December 2018 with Gutenberg, the block editor that replaced the classic TinyMCE editor. That was Phase 1—rebuilding how individual users create content.
Phase 2 arrived with WordPress 5.9 in January 2022, introducing Full Site Editing. Suddenly, the block editor wasn’t just for posts and pages—it could handle headers, footers, and entire site templates. Phase 2 wrapped up with WordPress 6.2 in March 2023.
Now Phase 3 takes everything built in those previous phases and makes it collaborative. According to Make WordPress, the core development blog, real-time multi-user editing will work similarly to Google Docs. Multiple team members can work on the same page simultaneously, seeing each other’s changes as they happen.
This matters more than you might think.
Real-Time Collaboration Changes Agency Workflows
“WordPress 7.0 is set to redefine how teams build websites together, moving away from the ‘solo editor’ model and toward a shared, real-time creative environment,” The Repository reported.
For agencies like ours, this addresses a genuine pain point. Currently, coordinating website updates across a team involves a lot of “I’ll ping you when I’m done” and hoping nobody overwrites somebody else’s work. It’s manageable. But it’s not efficient.
The new collaboration features should allow:
- Content writers and designers working on the same page simultaneously
- Real-time feedback without the “save draft, send link, wait for response” cycle
- Reduced handoff friction between team members
Whether this works as smoothly in practice as it does in theory remains to be seen. We’ve been burned by “revolutionary” WordPress features before that needed a few point releases to actually become usable.
Native AI Integration Through the WP AI Client
WordPress 7.0 also introduces the WP AI Client directly into core. This is interesting for a few reasons.
First, it’s provider-agnostic. WordPress isn’t tying itself to OpenAI or Anthropic or any single AI service. The WP AI Client is designed to work with whichever AI provider you choose—or whichever your hosting company has integrated.
Second, this is a strategic move. Right now, the AI plugin space in WordPress is fragmented. Dozens of plugins offer AI content generation, AI image creation, AI SEO suggestions. Most of them are, frankly, not great. Having a standardized AI client in core gives plugin developers a foundation to build on, which should eventually lead to more consistent experiences.
What it won’t do is write your content for you. At least, it shouldn’t. The AI integration is positioned as an assistant, not a replacement. We expect it’ll handle tasks like suggesting meta descriptions, generating alt text for images, and offering content recommendations.
The Admin Visual Refresh
Along with the major feature updates, WordPress 7.0 includes a visual refresh of the admin interface. The details are still emerging, but this appears to be the first significant admin redesign since WordPress 3.8 introduced the current dark sidebar in 2013.
Visual refreshes can be polarizing. Some users adapt quickly. Others spend weeks frustrated that their muscle memory no longer works. If your team relies heavily on the WordPress admin, plan some adjustment time after the update.
Breaking Change Alert PHP 7.4 Minimum Requirement
WordPress 7.0 raises the minimum PHP version to 7.4, officially dropping support for PHP 7.2 and 7.3.
This sounds technical, and it is. But it matters for site owners because PHP 7.2 reached end-of-life in November 2020, and PHP 7.3 followed in December 2021. If your site is still running on these versions, it’s already operating on unsupported software. Security patches stopped years ago.
According to Patchstack’s 2024 security report, 7,966 new vulnerabilities were discovered in the WordPress ecosystem last year—a 34% increase over 2023. And Wordfence reports blocking 55 billion password attacks against WordPress sites in 2024 alone.
Running outdated PHP isn’t just a compatibility issue. It’s a security risk.
The good news: most quality hosting providers have already migrated customers to PHP 8.0 or higher. But if you’re on a budget host or managing your own server, verify your PHP version before April 9.
Should You Update to WordPress 7.0 Immediately
It depends.
For small sites, personal blogs, and non-critical projects, updating within the first week is probably fine. WordPress major releases go through extensive beta and release candidate testing. They’re generally stable at launch.
For business-critical sites, e-commerce stores, or anything that generates revenue, we recommend a more cautious approach:
Wait 2-4 weeks after release for initial bug reports to surface. Major releases often have edge cases that only appear at scale.
Test on staging first. If you don’t have a staging environment, this is your sign to set one up. Never test major updates on production.
Check plugin compatibility. This is crucial. According to Patchstack, 89-92% of WordPress vulnerabilities come from plugins, not WordPress core. A core update can break plugin functionality, and broken plugins create security gaps.
Follow the update order: plugins first, then themes, then WordPress core. This gives you the cleanest path to identifying what broke if something goes wrong.
And after updating, monitor your site for at least 48 hours. Check forms, checkout processes, user registration—anything interactive. Problems don’t always show up immediately.
The Bigger Picture for WordPress Security
We’d be remiss not to mention the broader context here. WordPress powers nearly half the web. That makes it a massive target.
The 61% statistic gets thrown around a lot: according to industry research, 61% of infected WordPress sites are running outdated versions of WordPress, plugins, or themes. Keeping current isn’t just about new features. It’s about not becoming part of that statistic.
WordPress 7.0’s PHP requirement change is actually a security measure dressed as a technical requirement. Forcing sites to modernize their server environment closes vulnerabilities that have existed for years. For more on protecting your site, see our guide to WordPress security.
What We’re Doing to Prepare
For our maintenance clients, we’re already building WordPress 7.0 testing into our spring schedule. Every site on a care plan will get a staging test before their production update.
For sites running PHP 7.2 or 7.3, we’re initiating conversations now about server upgrades. April is two months away. That’s enough time to handle this without panic.
For new builds starting in February or March, we’re designing with real-time collaboration in mind. The interfaces and workflows we create should take advantage of what 7.0 enables.
The Bottom Line
WordPress 7.0 represents a meaningful evolution in how the platform handles team-based work. Real-time collaboration and standardized AI tooling address genuine needs. The PHP requirement increase pushes the ecosystem toward better security practices.
Is it worth the upgrade? Almost certainly. Is it worth rushing into on day one? For most business sites, no.
Take it seriously. Test it properly. And when you do update, you’ll be joining a platform that’s continuing to evolve in ways that actually matter.