WordPress 7.2 will open a new address on your site: what to check before December 8

What happened
On November 5, 2026, the WordPress team published a technical note about something new in version 7.2: a new address, /random/. Anyone who visits yoursite.com/random/ lands on a published post picked at random. It's on by default, and the final release is scheduled for December 8.
A second note that day covers the icons in the admin dashboard, which are changing too. We explain who that affects further down.
WordPress 7.2 is still in testing, so some details could change before release.
What it means
Picture a bookshop with a "surprise me" button: you walk in and someone hands you whatever book comes off the shelf. /random/ does the same thing with your posts.
It also works by section. /random/category/news/ sends people to a random post in that category, and tags and authors work the same way. Pages like "Contact" or "About us" are left out. Other content types, such as a custom-built catalog, can be included if they meet certain technical conditions. Your team can exclude them.
How it affects you
The good. If you run a blog with a lot of posts, readers get another way to find older pieces that still hold up, and you don't have to install anything. Aaron Jorbin, who wrote the note, thinks most people will find it useful because most people want their content discovered.
The bad. Any published post can come up, including the ones you forgot about: an expired promotion, or a piece that no longer reflects your business. They were already public, but now they're easier to stumble on.
Not everyone is sold on having it on by default. In the comments on the note, Joost de Valk and other developers asked for it to start switched off. Ryan McCue also warned that the method for picking a random post can be slow on large sites, especially if a lot of bots hit it. Another comment says that query has already been tested and improved, and McCue asked whether that fixes the problem on sites with many posts. As of November 6, the note didn't reflect any change.
Our take: on a small site, this is no cause for alarm. If your site has thousands of posts or a lot of bot traffic, it's worth measuring before you upgrade.
The dashboard icons. This one stays behind the scenes: your visitors won't see any change on your site because of it. The note says most plugins and themes need no changes. Dashboards with custom colors or icons are where things can go wrong, and they may not look the way they used to.
What you can do
If your site runs on WordPress, ask whoever maintains it to do the following:
- Test WordPress 7.2 on a copy of the site, never the live one. WordPress asks people not to install test versions on production sites.
- Visit
/random/on that copy. Check what comes up, especially if you already have a page at that address: the note doesn't explain what happens in that case. - Clean up old posts. Move anything you no longer want to show back to draft.
- Decide whether to keep it on. To turn it off, your team can add this line to a small plugin that WordPress always loads (a "mu-plugin"):
add_filter( 'wp_enable_random_content_redirect', '__return_false' ); - Open the admin dashboard and check that colors, menus and icons look right.
If you do nothing, your site won't break: once you upgrade, /random/ will simply be there.
Source
This article is based on official WordPress posts: Your Content Is Going To Get More Random! and SVG icons in the admin bar and menu in WordPress 7.2, both on Make WordPress Core, dated November 5, 2026, and WordPress 7.2 Beta 4, on WordPress News, dated November 3, 2026.
Frequently Asked Questions
Can /random/ show my drafts?
The note only talks about published posts, so a draft shouldn't come up. Test it on the copy if you handle sensitive content.
Do I have to turn it off?
No, that's your call. If your site is small and your posts are up to date, you can leave it on.
Can my contact or services pages come up?
No. The note says pages and attachments are left out.
When should I upgrade?
The final release is scheduled for December 8. The sensible move is to test it on a copy first and upgrade the live site once that test goes well.