WordPress 7.0: What Agencies Need to Know Before Upgrading
WordPress 7.0 is the biggest core release since Full Site Editing landed. For agencies managing dozens of client sites, a rushed upgrade could mean broken layouts, design regressions, and panicked client emails. Here is what actually changes and how to prepare.
The Headline Changes
WordPress 7.0 Beta 1 landed on February 19, 2026. The release includes foundational changes to the editor, new block capabilities, and deprecations that affect both themes and plugins. Here are the critical ones for agency workflows.
Always-Iframed Post Editor
The post editor is now always rendered inside an iframe, regardless of block API version. This is good for style isolation but may break custom blocks that rely on the global document object. Every custom block needs testing.
Viewport-Based Block Visibility
You can now hide blocks per viewport (mobile, tablet, desktop) directly from the editor. This replaces hacky CSS display-none patterns and gives clients safe, built-in responsive control.
Per-Block Custom CSS
Individual block instances can now have custom CSS attached. Great for one-off design adjustments, but a potential maintenance headache if clients overuse it. Consider restricting this via user roles.
Tabs & Breadcrumbs Blocks
Two long-awaited blocks are production-ready. The Tabs block now has a clean nested structure (Menu > Items, Panels > Tab) and the Breadcrumbs block has proper filter hooks for customization.
What Could Break
Not everything is plug-and-play. Here are the areas I am actively auditing on client sites before upgrading:
Custom Blocks Using Block API v2
If your blocks reference
window.documentor inject styles into the parent frame, they will break in the always-iframed editor. Follow the official migration guide to useuseBlockPropsand scoped styles.PHP 7.2 and 7.3 Dropped
WordPress 7.0 requires PHP 7.4 minimum. If your client's hosting still runs 7.2 or 7.3 (surprisingly common on budget shared hosts), the upgrade will fail. Check hosting environments first.
Navigation Block Overlay Changes
New Navigation blocks default to "always show overlays." Existing menus might render differently. If you have custom mobile navigation styling, verify it against the new overlay patterns.
Paragraph Block Gets a New Class
The Paragraph block now has a
.wp-block-paragraphclass on the front end. If your CSS targetspelements inside content areas with very specific selectors, check for conflicts.
My Recommended Upgrade Process
For every agency client site I manage, here is the systematic approach I follow:
- Stage first, always. Never update production directly. Clone the site to a staging environment and run the update there.
- Check PHP version. Confirm the hosting is running PHP 7.4 or higher. Upgrade the runtime before upgrading WordPress.
- Audit custom blocks. Test every custom block in the new iframed editor. Check for JS errors in the console and visual regressions.
- Run visual regression tests. Use a tool like BackstopJS or Percy to screenshot key pages before and after the update.
- Test plugin compatibility. Deactivate plugins one by one on staging and check which ones throw errors. Pay special attention to page builders, ACF, and WooCommerce.
- Verify mobile navigation. The overlay changes will affect responsive menus. Test thoroughly across breakpoints.
- Update, deploy, monitor. Once staging passes, push to production during low-traffic hours and monitor error logs for 48 hours.
The Wins Worth Celebrating
Viewport visibility finally removes the need for custom "hide on mobile" CSS patterns. Less custom code, fewer maintenance issues.
Native Tabs and Breadcrumbs mean two fewer third-party plugins on every site. Less bloat, fewer update conflicts.
View Transitions in the admin make the entire dashboard feel more polished. Client perception of "modern" improves without any extra work.
No extra wrapper divs in the editor means WYSIWYG is truly what you get. Less discrepancy between editor and front end.
Need Help with the WordPress 7.0 Upgrade?
I help agencies audit, stage, and safely upgrade client sites to major WordPress releases. Custom block migration, visual regression testing, and post-upgrade monitoring included.