WordPress 7.2, the last major WordPress release of 2026, ships on December 8, and its most interesting feature for SEOs is a small one: a new /random/ link that sends visitors to a random post. WPBeginner tested it and found the implementation is search-friendly by design, using temporary 302 redirects and a noindex header, which means the random URLs should not create indexation problems or dilute ranking signals.
The release schedule is set. Beta 1 arrived on October 20, Beta 2 on October 27, and Beta 4 on November 3, with the first release candidate due November 17 and the final release on December 8, 2026. The feature list was locked at Beta 1, so what is in the betas now is, barring a late cut, what will ship. Matt Mullenweg is the release lead, and the WordPress team warns, as it does for every beta, that the test builds are for testing and development only and should not run on production or mission-critical sites.
The headline features are about editing and design rather than search. Notes move into the margin of the editor, with emoji reactions and a toolbar button. Ipsum, a minimal blog theme with 8 color styles, becomes the new default theme and ends the Twenty- naming tradition that has run since Twenty Ten. Responsive styling reaches more blocks, including per-device column counts for the Gallery block, and images can now be resized and compressed in the browser before they upload, from the Media Library as well as the editor. The admin area should load faster, and a new Secrets API and a larger Abilities API arrive for developers.
The /random/ feature is simple. A link to /random/ sends the visitor to a random post on the site, and category and author versions pick a random post from that archive. A category that does not exist returns a 404. WPBeginner checked the response headers in its testing and found the random links use temporary 302 redirects and a noindex header, which is exactly what an SEO would want: the redirect passes no permanent signal, and the noindex header tells search engines not to index the random URL itself.
There are sensible guardrails. If a site already has a page at /random/, that page wins over the random redirect. The random base can be renamed with a new Random base field on the Settings, Permalinks page, and developers can turn the feature off entirely. WordPress turns it on by default for all public post types that have an archive. For larger sites, the advice is still to check crawl reports after the update, because any new URL pattern deserves a look at what crawlers actually do with it, but the design gives crawlers nothing to index and nothing permanent to follow.
Nothing in WordPress 7.2 changes how WordPress outputs titles, meta tags or sitemaps, so no direct ranking impact is expected. The indirect effects are positive: faster image handling, better responsive galleries, and a faster admin. The risks are the usual ones for a major update, and they sit with plugins and themes rather than core: a conflict that breaks schema can hurt revenue quickly, which is why testing on staging matters.
The practical checklist is short. Test 7.2 on a staging copy before December 8, confirm the theme, page builder and ad plugins are compatible, and after updating, view the page source and confirm the title, meta description, canonical tag and schema from the SEO plugin are unchanged. Re-check Core Web Vitals and run a crawl of key pages to catch any layout shifts introduced by theme or plugin changes. And check the /random/ behaviour on the live site, confirming that a visit to /random/ redirects and that the noindex header is present.
For technical SEOs, the /random/ detail is a small case study in how to ship a feature that could have been an SEO problem and was not. A random post link that used 301 redirects and no noindex header would have created a crawl trap and a set of junk URLs competing for attention. WordPress chose the safe implementation, and the lesson for anyone building features is to make that choice the default rather than leaving it to site owners to fix later.
For link builders and content teams, the release is mostly good news with a footnote. The faster admin, the browser-side image processing, and the Notes improvements all make it easier to publish and review content, which is the raw material link building depends on. The footnote is the December 8 date: a major platform update landing three weeks before Christmas, in the middle of the holiday season, is a bad week to discover a plugin conflict. Test early, update on staging first, and do not let a routine update become a December traffic problem.
Watch for the first release candidate on November 17 and the Field Guide that comes with it, which lists every change in detail for developers. After December 8, watch crawl reports and Search Console for any new URL patterns or errors tied to /random/, and watch the WordPress support forums for plugin conflicts in the first week. If the rollout is clean, 7.2 will be remembered as a quiet, practical release, and the /random/ link will be a small discovery feature that never caused a single SEO ticket.
Sources: WPBeginner, November 9, 2026.
Related reading on this site: November Core Update Collides With Black Friday, and a Clean Read Will Not Come Until December, Core Update Volatility Started Days Before Google Announced It, November Search Console Click Spikes May Be Bots, SEJ Reports, SEJ Pulse: Core Update, ChatGPT Business Hub and AI Mode's New Model, AI Overview Citations: What 15 Studies Agree On, and Don't, and Black Friday SEO Starts Eight Weeks Out, and November Is Already Late.
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