CMS

WordPress 7.2 Hits Release Candidate 1, Locking In Features for December 8

WordPress published the first release candidate for version 7.2 on November 17, 2026, the last stop before the final release scheduled for December 8. A release candidate means the feature list is frozen: from here on, only bug fixes land. For the huge share of the web that runs on WordPress, RC1 is the moment to start testing in earnest, because what ships in December is now essentially decided.

What RC1 locks in

The release candidate carries forward everything opened since the first beta on October 22. The new default theme, Ipsum, is now frozen, along with expanded responsive design controls and Gallery settings, improved Global Styles and typography tools, enhanced Canvas Notes and collaboration, and a new DataForm block settings inspector. The admin gets a modernised look with SVG icons, faster navigation and asset loading, and faster media uploads and image processing. There is also a new On This Day widget and random post discovery, improved translation update management, and accessibility, security and PHP 8.6 compatibility improvements.

One late change is worth noting. The new Secrets API, which would have added encrypted storage for credentials such as API tokens, was reverted from WordPress 7.2 before RC1, according to the Make WordPress Hosting team. It was disabled by default on sites without a key, and the decision to pull it means the feature will not ship in this release. That is the kind of cut a release candidate is designed to make: better to drop a half-ready feature than to freeze it into millions of sites.

What changed since Beta 5

RC1 is not just a label change. Since Beta 5 on November 10, the WordPress team closed more core tickets and landed further Gutenberg commits, bringing additional bug fixes, accessibility improvements and compatibility updates. Recent refinements include fixes to client-side media uploads, improvements to the new random-content redirect feature, and better keyboard navigation through a skip link in the admin bar. Plugin dependency messaging, script module translations, and the reliability of the HTML and Interactivity APIs were also improved, along with continued refinements to the Abilities API and updates to bundled libraries including PHPMailer, Requests, getID3 and sodium_compat.

The block editor got its own round of fixes. RC1 addresses duplicated block content, keyboard interactions on iOS, and revision previews, and it stops outdated navigation responses from replacing newer content through the Interactivity API. Plugin installation workflows, featured image compatibility and link suggestions were improved too, and the transition to modern SVG icons continues throughout the admin. None of these is a headline feature on its own, but together they are what makes a release candidate feel finished rather than experimental.

Why it matters for SEOs and link builders

A WordPress release candidate matters to SEOs for a practical reason: it is the last safe window to find problems before the update reaches client sites. WordPress asks theme and plugin authors to finish testing against RC1 and update the Tested up to version in their plugin readme files to 7.2. If a plugin your site depends on has not been tested, now is the time to find out, not the week after December 8. Hosts are testing too, since the release behaves differently on a hosting platform than on a single test site, particularly around upgrades and the new random-content route, which needs a rewrite flush after an upgrade.

The calendar matters as well. December 8 lands in the middle of the holiday shopping season, when many ecommerce sites are in a change freeze of their own. The sensible plan is to test RC1 on a staging copy now, check that key pages still render, that structured data and sitemaps are intact, and that speed has not changed, then pick a quiet moment to update. There is no ranking penalty for updating a few days late, and a careful update in January beats a careless one in December.

What to watch next

The next milestone is the final release on December 8, 2026, unless a serious bug forces a second release candidate first. Watch the Make WordPress Core blog for RC2 news and for the field guide of developer changes, and watch what site owners and hosts report in the first weeks after launch. Major releases sometimes surface issues that only appear at scale, in particular plugin combinations or hosting setups. If your sites run WordPress, put December 8 in the calendar, test RC1 on staging this week, and do not let the update collide with a holiday campaign.

Sources

Sources: WordPress.org News, November 17, 2026.

Related reading on this site: AI Overviews Showed Up in Only 20% of Local Searches, and Mostly Copied the Map Pack, Semrush Rebuilds Traffic and Market Data With a New Model, and Old Numbers Will Change, WordPress 7.2's New /random/ Links Use 302s and Noindex, So They Should Not Hurt SEO, 33 of 42 Top-Ranking Local Businesses Have Zero Local Links, 42-Site Test Finds, AI Traffic Now Reaches Nearly 80% of Websites, SE Ranking Finds, and November 2026 Core Update Still Rolling Out as Volatility Peaks on November 14.

More from Linkbaits

Turn this playbook into links

Linkbaits helps you create content that earns citations and backlinks. Start with the toolkit and build your first linkable asset this week.

Start free trial