WordPress 7.0: What actually changes for agencies

WordPress 7.0 was supposed to ship on April 9, 2026, during WordCamp Asia in Mumbai. The core team delayed the release at the last minute to resolve stability issues in the real-time collaboration feature. As of now, the new release date has not been confirmed, but the WordPress project has indicated an announcement will come soon. Most estimates put the final release somewhere in May 2026.

WordPress 7.0 marks the official launch of Phase 3 of the Gutenberg project, the collaboration phase, and it brings the most significant editorial and technical changes in years. So this won’t be a routine point release. We decided to ask Natalia, our Head of Production at WLA, to walk us through what actually changed and what it means in practice for agencies building on WordPress.

Multiple users can now edit the same page at once

Source: WordPress.com

Until now, if two people tried to work on the same WordPress page simultaneously, one of them would get locked out. WordPress 7.0 changes that. Multiple editors can now work on the same post or page at the same time, with live cursors showing who is where and changes syncing in real time. It’s like Google Docs, but inside your WordPress editor. 

It’s worth noting that real-time collaboration depends on the underlying infrastructure and may rely on technologies like WebSockets or similar connections. Not all hosting environments fully support these, which can affect how smoothly real-time syncing works. It’s a good idea to verify compatibility with your hosting provider before relying heavily on this feature.

Blocks can now be hidden on specific screen sizes

Responsive design has always required some level of custom work to control what appears on mobile versus desktop. WordPress 7.0 builds that control directly into the editor. You can now show or hide specific blocks depending on the device: desktop, tablet, or mobile, without any plugin or custom code.

“This simplifies setups that previously depended on third-party tools or bespoke CSS workarounds. Fewer plugins means fewer things to maintain, and fewer points of failure when WordPress updates in the future,” Natalia notes. 

New blocks: breadcrumbs, icons, and tabs

Several new blocks have been added to the Gutenberg editor in 7.0, including a Breadcrumbs block, an Icons block, and a tabs-style block. These cover common design patterns that agencies were previously handling with custom solutions or third-party plugins. 

“Breadcrumbs come up constantly on agency projects,” Natalia said. “Having it as a native block means less custom code to maintain.” 

Additional design settings have also landed for existing blocks, including more granular image size controls. For teams building with block themes, these additions reduce the amount of custom block development needed on routine projects.

The WordPress admin has been redesigned

The Posts, Pages, and Media screens inside the WordPress admin have been fully rebuilt. The new interface supports inline filtering, sorting, grouping, and multiple view modes, including table, grid, and list, all without page reloads. It feels noticeably more like a modern dashboard than the old list tables did. 

“The colors are a bit different, and everything feels slightly slower at first because you’re not used to it,” Natalia explains. “But the filtering and the multiple views are genuinely useful once you’re in there.” 

The initial load is marginally slower in some environments during this testing phase, which is expected to improve as the release stabilizes.

WordPress can now be edited through AI

Source: WordPress.com

WordPress 7.0 introduces what the core team calls an internal MCP server, a technical foundation that allows AI tools to connect to and interact with a WordPress site in a structured, permissioned way. In plain terms, this means AI assistants can now understand what your WordPress site can do and make edits through a native connection, rather than through workarounds.

 “This makes the site editable through AI,” Natalia told us. “That is significant for how WordPress will develop over the next few years.” This is not a feature most agencies will use directly in 7.0. Its importance is in what it opens up: a formal bridge between WordPress and the AI tooling that is already becoming standard in development workflows.

Custom block development is now simpler

Developers who build custom blocks for client sites will find the process more straightforward in 7.0. You can now register a block using PHP alone, without needing a JavaScript build step or a Node.js setup. For developers who work primarily in PHP, this removes a significant barrier that previously made even simple custom blocks more complicated than they needed to be. 

The editor itself has also moved into an iframed environment, which improves style isolation but may affect how some existing custom block styles render. Any agency with custom blocks will want to test on a staging site before upgrading.

CTA: https://thewhitelabelagency.com/hire-wordpress-developer/

The minimum PHP version has moved to 7.4

WordPress 7.0 drops support for PHP 7.2 and 7.3, setting 7.4 as the new minimum required version. For most agencies, this will not be an issue. The majority of well-maintained hosting environments are already running PHP 8.x. 

“On our server, we have PHP 8.5, so we do not need to worry,” Natalia confirmed. That said, agencies managing older client infrastructure should check PHP versions before upgrading. Running WordPress 7.0 on an unsupported PHP version will create compatibility problems. The recommended version is PHP 8.2 or higher.

Where conflicts and compatibility issues may appear

Not every change in 7.0 will land smoothly across every site. Based on what we know from testing and from Natalia’s review of the release, there are several areas where problems are most likely to surface.

• Admin customization plugins are the highest-risk category. Any plugin that modifies the Posts, Pages, or Media list screens is touching code that has been substantially rewritten in 7.0. Plugins in this category, including some dashboard enhancement tools and admin UI libraries, may behave incorrectly or break entirely until updated.
• Custom block styles may render differently inside the new iframed editor. If a theme or custom block relied on inheriting CSS from the admin environment, that styling inheritance no longer applies in the same way. So a visual review on a staging site is important.
• Real-time collaboration and hosting compatibility is a potential issue for sites on hosting that do not support WebSockets, as we pointed out above. The feature will not work, and depending on how the plugin or host handles the failed connection, it may produce errors rather than simply disabling gracefully.
• Plugin compatibility in general is still settling. While major tools like Yoast, ACF, WooCommerce, and WPML are expected to ship compatibility updates around the final release, smaller or unmaintained plugins are unpredictable. Any plugin that has not been updated in the past 12-18 months is worth checking before upgrading.

WordPress update checklist: how agencies should prepare

The delay gives agencies more time to prepare, and it is worth using that time well. We asked Natalia for her practical advice.

Her recommendation was consistent with how we approach major updates at WLA: test first, upgrade deliberately, and do not rush on production sites.

Here is a practical checklist and a recap of how to avoid the compatibility issues easily: 

1. Check PHP versions on client sites. PHP 7.4 is the minimum requirement. PHP 8.2 or higher is recommended.
2. Audit plugins for compatibility. Prioritize anything that touches admin list views, the block editor environment, or custom post type management.
3. Set up a staging environment for each site before upgrading. Install the 7.0 release there first and review the admin, the editor, and any custom blocks.
4. Test iframed editor rendering. Check that custom block styles look correct inside the new editor environment.
5. Verify hosting WebSocket support if you plan to use real-time collaboration with clients.
6. Create full backups before any production upgrade. Files and database.
7. Do not rush production upgrades. Wait for the first week of real-world feedback after the release lands before upgrading sites where stability is critical.

On the question of whether agencies should upgrade immediately: the short answer is no, not on production sites. The delay itself is a signal that this release is complex. Waiting a week or two after the final release, running a full staging test, and confirming plugin compatibility is a sensible approach for any client site with real traffic or business-critical functionality.

Our take

WordPress 7.0 is a significant release. The collaboration features change how editorial teams can work inside WordPress, the admin redesign brings the interface closer to what users expect from modern tools, and the Abilities API lays the groundwork that will matter more and more as AI tooling becomes standard in development workflows.

At WLA, we’ve worked with 600+ agencies building on WordPress for the past decade. What we hear most often is that the platform needs to be more team-friendly and that client review processes are harder than they should be. The 7.0 collaboration tools address both of those directly.

The delay was the right call. A broken real-time collaboration feature at launch would have done more damage than a few extra weeks of testing. When the release does arrive, it will be worth the time you put into preparing for it.

If you want experienced WordPress developers handling the upgrade and compatibility testing for your clients, we can help.