Illustration of a browser window with three stacked page cards and a curved arrow jumping to one of them

WordPress 7.2 Adds /random/: What to Check on Your Site

Admin

WordPress 7.2, with its final release scheduled for December 8, 2026, adds a new address: yoursite.com/random/ sends visitors to a randomly chosen published post. It is on by default and, according to Search Engine Journal, cannot be turned off from the dashboard. It affects every WordPress site that updates, especially sites that use custom post types.

What we know

  • The announcement: Aaron Jorbin published the developer note on Make WordPress Core on November 5, 2026. It says a visit to /random/ leads to a random published post and that the feature is on by default.
  • The variants: per the note, /random/category/…, /random/tag/…, /random/author/… and /random/ followed by a post type slug also work. The "random" base is translated with the site language and can be changed under Settings > Permalinks.
  • What content is included: the note adds a randomable option to post types. Regular posts are in; pages and attachments are out. Custom post types (testimonials, portfolio items, projects…) are in by default if they are publicly queryable and have an archive.
  • How to turn it off: the Make WordPress Core note gives the wp_enable_random_content_redirect filter. The November roundup on the WordPress Developer Blog (Justin Tadlock, November 13) spells a different name, wp_enable_random_content_direct. According to Search Engine Journal, only the first exists in the code.
  • What it returns: according to Search Engine Journal (November 19), the redirect is temporary (302) and the response carries a noindex, follow header plus no-cache headers. The same outlet says the destination post does not get that noindex and that selection does not skip posts an SEO plugin marked noindex. The official note does not cover these points.
  • The schedule: the RC1 post on WordPress News (November 17) mentions improvements to this redirect and keeps the final release on December 8. According to Search Engine Journal, RC2 is due on November 24 and the roadmap still shows December 10.

What changes and what doesn't

What changes: without anyone enabling it, your site gets an address that spreads visits across your posts and, unless you stop it, across custom post types with archives. Content that today is only seen by people who know its link can now come up from /random/.

What doesn't: what Google indexes on its own. According to Search Engine Journal, the redirect itself carries noindex, so /random/ should not show up in results. Nothing changes until the site is on 7.2. And, per the note, pages and attachments are left out.

How to tell if it affects you

  1. Test on a copy. On your host's staging environment, install the 7.2 RC and load yoursite.com/random/ several times. Note which posts come up and whether any should not be in view (old test posts, content for finished campaigns).
  2. Go through your post types. For each custom post type with an archive, try /random/ followed by its slug (for example, /random/testimonials/). If something you had set to noindex shows up, decide whether you want it there.
  3. If you don't want it, ask whoever maintains your site to either exclude that type with 'randomable' => false or switch the whole feature off with add_filter( 'wp_enable_random_content_redirect', '__return_false' );. Since two official pages give different names, check afterwards that /random/ no longer redirects.
  4. Do you have a page called "random"? According to Search Engine Journal, a page or post with that slug takes precedence. Check on the copy that it still loads as before.
  5. Check your cache and CDN. If your caching plugin or CDN stores the /random/ response, every visitor lands on the same post. Make sure that address is excluded from caching. According to Search Engine Journal, /random/ can also return a 404 right after updating until the cache is cleared.
  6. Watch Search Console after December 8. If /random/ shows up in the pages report or crawl stats, inspect the response headers with your browser's developer tools.
  7. On shared hosting, ask whether your site will auto-update to 7.2 and whether you can pick the date.

Related: WordPress 7.2 RC1: What to Test Before December 8

Sources

Updates: if RC2 or the final release changes how /random/ works or the filter name, it will be added here with its link.

Worried about how this affects your website?
We will go over what to change with you. It is a free 30-minute call.