WordPress 7.0 Update: Complete Preparation Guide for Site Owners

WordPress 7.0 drops on April 9, 2026, and it is the most significant release since the block editor arrived in WordPress 5.0. Real-time collaboration, a rebuilt admin interface, native AI infrastructure, responsive block visibility, and a new font library are all landing at once. That is a lot of moving parts, and any one of them could disrupt a plugin, a theme, or a workflow you rely on every day.

This guide gives you a step-by-step preparation plan so you can update with confidence instead of crossing your fingers. Every action here can be completed before launch day, and most take less than ten minutes.

What Is Actually Changing in WordPress 7.0

Before you prepare, you need to know what you are preparing for. WordPress 7.0 introduces five major changes that affect how sites look, behave, and integrate with external services.

Real-Time Collaboration (Phase 3 Gutenberg)

Multiple users can now edit the same post or page simultaneously. You will see live cursors, presence avatars, and instant content updates — similar to what Google Docs offers. WordPress core ships with an HTTP polling sync provider by default, while hosts and plugins can add WebSocket support for faster performance. The Classic block (core/freeform) is currently incompatible with real-time collaboration, so sites that still use it should plan for the transition.

DataViews Admin Overhaul

The Posts, Pages, and Media list screens are being rebuilt with DataViews — a modern, app-style interface that replaces the legacy WP List Table. You gain inline filtering, grid and table layout options, density controls, and persistent view preferences. The trade-off is that any plugin hooking into the old list table DOM structure may display incorrectly or lose functionality entirely.

WP AI Client and Abilities API

WordPress 7.0 includes a provider-agnostic AI client that gives plugins a unified API for text generation, image generation, and structured output. The Abilities API (introduced in 6.9 and expanded in 7.0) lets external AI tools discover and execute WordPress capabilities through a standardized interface. An MCP Adapter translates these abilities for tools like Claude, ChatGPT, and other AI assistants.

Responsive Editing Mode

You can now hide or show individual blocks based on device type — desktop, tablet, or mobile — directly in the block editor. No plugin required. Breakpoints are customizable, and you can preview and edit at each viewport size within the editor itself.

Font Library for Classic Themes

Classic theme users can upload and manage custom fonts through Appearance, then Fonts. Supported formats include TTF, OTF, WOFF, and WOFF2. This eliminates the need for font management plugins on many sites.

Step 1: Check Your PHP Version

WordPress 7.0 drops support for PHP 7.2 and 7.3. The minimum requirement is PHP 7.4, but PHP 8.2 or 8.3 is strongly recommended for performance and security.

To check your version, go to Tools > Site Health in your WordPress dashboard and look under the Server section. If you are running anything below PHP 7.4, you will be blocked from updating. Contact your host to upgrade before April 9.

If your host still offers PHP 7.2 or 7.3 as the default, that is a red flag. Modern managed WordPress hosts like Cloudways, Kinsta, and SiteGround all support PHP 8.2+ and make version switching straightforward.

Step 2: Create a Full Backup

Before testing anything, take a complete backup of your files and database. This is your safety net if something breaks during the update.

Use your existing backup solution — whether that is UpdraftPlus, BlogVault, your host’s built-in backup tool, or a manual approach through phpMyAdmin and SFTP. The critical requirement is that you verify the backup actually works by confirming the backup file exists and contains recent data. A backup you have never tested is not a backup. If you need help selecting a backup solution, our disaster recovery testing guide compares the leading options in detail.

Store at least one copy off-site (cloud storage, local download, or a separate server). Hosting-only backups disappear if your hosting account has an issue.

Step 3: Set Up a Staging Environment

Never test a major WordPress update on your live site. A staging environment gives you a clone where you can break things without consequences.

Most managed WordPress hosts offer one-click staging. If yours does not, tools like WP Staging, InstaWP, or the WordPress Playground project can create a test copy. Clone your production site, then update WordPress to the latest beta or release candidate on staging first. Our staging plugins guide walks through setting up a staging environment from scratch.

Enable WP_DEBUG in your staging site’s wp-config.php file to surface hidden errors:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

This logs PHP warnings and deprecated function notices to wp-content/debug.log without showing them to visitors. Check this file after updating to catch compatibility issues early.

Step 4: Audit Your Plugins for Compatibility

This is the most important step in the entire process. Plugins that modify admin list views, inject custom admin CSS, or hook into the Classic editor block carry the highest risk of breaking in WordPress 7.0.

High-Risk Plugin Categories

• Admin interface modifiers: Plugins that customize the Posts, Pages, or Media screens are most likely to conflict with the DataViews overhaul. If you use custom admin columns, bulk action extensions, or admin theme plugins, test them on staging immediately.
• Page builders with admin hooks: Elementor, Divi, Beaver Builder, and Bricks should release 7.0-compatible updates before launch. Check their changelogs and announcement pages. Our page builder comparison covers how each handles major WordPress updates.
• Classic Editor users: The Classic block is incompatible with real-time collaboration. If your workflow depends on the Classic Editor plugin, collaboration features will not apply to those editing sessions.
• Custom post type plugins: Plugins that register custom list table columns or filters will need DataViews-compatible updates.

How to Check Compatibility

1. Update all plugins to their latest versions on staging.
2. Update WordPress to 7.0 beta or RC on staging.
3. Visit every admin screen you use regularly. Look for broken layouts, missing elements, or PHP errors.
4. Test key workflows: publish a post, upload media, manage users, process a form submission, complete a WooCommerce order.
5. Check Tools > Site Health for new warnings.
6. Review wp-content/debug.log for deprecation notices or errors.

If a plugin breaks, check the plugin’s support forum or website for a 7.0-compatible release. For premium plugins like Gravity Forms, WooCommerce, Yoast SEO, and WPML, vendors typically release compatibility updates within the first week of a major WordPress release — and many have beta-compatible versions available before launch.

Step 5: Test Your Theme

Themes are generally less affected than plugins by WordPress 7.0, but two areas need attention.

First, if you use a classic theme, visit Appearance > Fonts on your staging site to confirm the new font library works correctly with your theme’s typography settings. This feature is new for classic themes and could interact with existing font plugins or custom CSS font declarations.

Second, test the Responsive Editing Mode by creating a test post, adding a few blocks, and toggling visibility for different device types. Verify that hidden blocks actually disappear on the frontend at the correct breakpoints. If your theme uses custom breakpoints that differ from WordPress defaults, you may need to align them.

Step 6: Evaluate Your Hosting for Collaboration Features

Real-time collaboration works out of the box using HTTP polling, but the experience improves significantly with WebSocket support. Not all hosting environments support persistent WebSocket connections, particularly shared hosting plans.

If your team edits content collaboratively and you want the best experience, check with your host about WebSocket support. Managed WordPress hosts like WordPress VIP, Pressable, and Convesio already support it. If you are on basic shared hosting, the HTTP polling fallback works fine — it is just slightly less instantaneous.

For single-author sites or sites where editors rarely work on the same content simultaneously, this is a non-issue. The collaboration features exist but do not interfere with solo editing workflows.

Step 7: Review Custom Code and Integrations

If your site uses custom code — whether in a child theme’s functions.php, a custom plugin, or code snippets — review it for compatibility with these WordPress 7.0 changes:

• WP List Table hooks: Any code that hooks into manage_posts_columns, manage_pages_columns, or similar filters may need updating for DataViews compatibility.
• Admin CSS overrides: Custom admin stylesheets may conflict with the refreshed design tokens and unified styling in 7.0.
• REST API integrations: The Abilities API adds new REST endpoints. Existing REST API integrations should continue working, but verify that custom endpoints do not conflict with the new /wp-json/wp/v1/abilities route. Our REST API authentication guide covers the security model that still applies in 7.0.
• PHP 7.4+ syntax: If your custom code was written for PHP 7.2 or 7.3, ensure it runs cleanly on PHP 8.2+.

Step 8: Plan Your Update Timeline

Just because WordPress 7.0 launches on April 9 does not mean you need to update on April 9. Here is a practical timeline:

When	Action	Risk Level
Now through March 19	Complete Steps 1-7 above using Beta 2	No risk (staging only)
March 19 – April 8	Re-test with Release Candidate 1	No risk (staging only)
April 9 (launch day)	Wait. Monitor plugin vendor announcements.	Low risk (no action)
April 10-16 (week 1)	Update staging to final 7.0. Test all plugins again.	No risk (staging only)
April 17+ (week 2+)	Update production once staging passes all checks.	Minimal (tested and verified)

The safest approach is waiting one to two weeks after release. By then, major plugin vendors have released compatibility patches, early adopters have surfaced edge-case bugs, and WordPress 7.0.1 (a bug-fix release) may already be available.

What You Can Skip Worrying About

Not everything in WordPress 7.0 requires preparation. Here is what you can safely ignore during your update planning:

• The AI Client: It is infrastructure only — no AI features activate automatically. You need to install a provider plugin and configure API keys before anything AI-related happens.
• Collaboration on single-author sites: Real-time editing features are designed for teams. Solo site owners will not notice any difference in their editing experience.
• New block types: WordPress 7.0 adds blocks like Accordion, Term Query, and Icons. These do not affect existing content — they are simply new options available when editing.
• Design token changes: Unless you have written custom admin CSS, the refreshed admin styling will look better without requiring any action from you.

Your Pre-Update Checklist

Print this or save it as a reference for update day:

• PHP version is 7.4 or higher (8.2+ preferred)
• Full backup created and verified
• Off-site backup copy stored
• Staging environment created
• WordPress 7.0 installed on staging
• All plugins updated to latest versions on staging
• Admin screens tested (Posts, Pages, Media)
• Key workflows tested (publishing, forms, orders)
• Theme tested with Font Library and Responsive Mode
• debug.log reviewed for errors
• Site Health checked for warnings
• Plugin vendor compatibility statements reviewed
• Custom code audited for deprecated hooks
• Production update scheduled for 1-2 weeks post-launch

Conclusion

WordPress 7.0 is a genuinely exciting release. Real-time collaboration changes how teams work together, the admin overhaul modernizes an interface that has looked roughly the same for over a decade, and the AI infrastructure opens entirely new categories of plugin functionality. But excitement should not override caution.

The sites that transition smoothly will be the ones that tested on staging, verified plugin compatibility, and waited for the dust to settle before updating production. Follow the eight steps in this guide, use the checklist, and you will be ready to take advantage of everything WordPress 7.0 offers without the downtime or broken layouts that catch unprepared site owners off guard.

Start with Step 1 today — checking your PHP version takes less than a minute, and it is the single most common blocker for WordPress 7.0 adoption.