WordPress 7.0 RC2 Is Here: What It Means for Your Site and How to Prepare

The second Release Candidate for WordPress 7.0 dropped on March 26, 2026, and the countdown to one of the most significant WordPress releases in years is officially on. With the final release scheduled for April 9, 2026, now is the time to get your site, your themes, and your plugins ready.

At AI WP Coder, we help thousands of WordPress site owners build, extend, and maintain their sites with AI assisted code. A major core release is always a moment to pay attention, so here is our practical breakdown of what RC2 brings and what you should be doing about it this week.

What Is a Release Candidate?

A Release Candidate (or RC) is the stage of the WordPress release cycle where the software is considered ready to ship, but the community is given one last window to flush out bugs, compatibility issues, and edge cases before it reaches millions of live sites.

RC2 follows the first Release Candidate from earlier in March and, importantly, marks the hard string freeze. That means translators can now finalise localisation work without the text changing underneath them, and no further user facing strings will be added to 7.0.

In short: the feature set is locked. Anything you see in RC2 is what you will get on April 9.

What Is New in WordPress 7.0?

RC2 itself is a stabilisation release rather than a feature drop, but it carries forward everything introduced across the 7.0 beta cycle. The two headline initiatives worth flagging for site owners and developers:

1. Real Time Collaboration

WordPress 7.0 brings real time collaboration into the editor. Multiple users can now work on the same post or page together, with live presence indicators and simultaneous editing. For agencies, editorial teams, and anyone who has ever emailed a draft back and forth, this is a quality of life leap.

2. Pattern Editing and Content Only Interactivity

Pattern editing gets a meaningful upgrade in 7.0, along with improvements to content only interactivity. Designers and site builders can now create richer, more reusable patterns with clearer boundaries between structure and content, which should make template maintenance far less painful across large sites.

Beyond these headline features, 7.0 includes the usual mix of performance improvements, accessibility fixes, and developer API refinements. If you want the deep technical detail, the 7.0 Developer Notes on Make WordPress Core are the definitive source.

How to Test WordPress 7.0 RC2

You have four ways to try RC2 right now. A very important note first: do not install this on a production or mission critical site. Use a staging environment, a local install, or the browser based Playground.

  1. WordPress Beta Tester plugin. Install the official WordPress Beta Tester plugin, then set it to the "Bleeding edge" channel and the "Beta/RC Only" stream.
  2. Direct download. Grab the RC2 zip file and install it manually.
  3. WP-CLI. If you live on the command line, run: 
    wp core update --version=7.0-RC2
  4. WordPress Playground. Spin up a disposable browser based instance with zero setup via the Playground RC2 link.

If you find a bug, report it to the Alpha/Beta support forum or, if you are comfortable writing a reproducible bug report, file it directly on WordPress Trac.

What Site Owners Should Do Before April 9

If you run a WordPress site and you are not a developer, here is the short version of how to prepare:

  • Back up your site. Full database and files, stored somewhere off server. Do this before any major version upgrade, every time.
  • Spin up a staging copy. Most quality hosts offer one click staging. Use it.
  • Test RC2 on staging. Walk through the parts of your site that matter most: checkout, contact forms, membership logins, bespoke block patterns, page builder pages, and so on.
  • Check your plugin and theme update queues. Many developers ship 7.0 compatibility updates in the days leading up to release. Applying them now on staging is safer than applying them blind on launch day.
  • Wait a week after April 9 to update production. Unless you need a specific 7.0 feature on day one, letting the ecosystem catch up for a few days is almost always the right call.

What Plugin and Theme Authors Should Do

If you maintain plugins or themes on the WordPress.org directory:

  • Test against RC2 now. The API surface is frozen, so what you see is what you ship against.
  • Update the "Tested up to" header. Once your plugin or theme is confirmed working, set the version to 7.0 in your readme.txt so users see the compatibility badge.
  • Review the 7.0 Developer Notes. Even if you do not think the changes touch you, a quick skim can save you a support ticket storm later.
  • Report compatibility issues early. The Alpha/Beta forum is monitored and the core team is actively triaging reports.

How AI WP Coder Can Help

The jump from a beta cycle to a stable release is where AI WP Coder pays for itself. Whether you need to:

  • audit a custom plugin for 7.0 compatibility,
  • refactor a block pattern to use the new pattern editing improvements,
  • wire your editorial workflow to take advantage of real time collaboration, or
  • just deprecation check a pile of bespoke code you inherited,

our AI powered WordPress coding agent can work through it with you, generate the code, and test it against a sandboxed site before you ship.

If you are a UK based agency or freelancer juggling multiple client sites through the 7.0 transition, this is exactly the kind of work we were built for.

The Bottom Line

WordPress 7.0 RC2 is a signal. The release is locked, the strings are frozen, and April 9 is not far away. The sites that sail through the upgrade are the ones whose owners are testing this week, not the ones who find out something broke on release day.

Back up, stage, test, and update your "Tested up to" headers. And if you get stuck, AI WP Coder is here to help you move faster without breaking things.

Source: WordPress 7.0 Release Candidate 2 announcement by Mary Hubbard, published March 26, 2026 on wordpress.org.