
WordPress 7.2, scheduled for December 8, 2026, adds a web address, yoursite.com/random/, that sends a visitor to a randomly chosen published post. The feature is on by default, so a site that updates gets it unless someone switches it off. If you run a business site, this WordPress 7.2 random redirect is worth a quick question to your webmaster before the update.
The worry that reaches owners first is Google. Google has not said the feature affects rankings. In the test versions, the redirect came back marked noindex, a note that tells search engines not to list an address in their results. The final release may behave differently from the test versions, so the check that counts happens after you update.
That leaves three jobs: send your webmaster one short message, decide whether your site wants the feature, and open /random/ yourself once the update is live.
Key Takeaways
WordPress 7.2 is scheduled for December 8, 2026. The /random/ address is on by default and sends a visitor to a randomly chosen published post.
A 302 is a temporary redirect, a noindex rule has to stay crawlable to be seen, and robots.txt controls crawling, not guaranteed removal from results.
Ask your webmaster what /random/ returns on a staging copy, which post types it can pick, and whether caching and rewrite rules were refreshed.
The filter `wp_enable_random_content_redirect` switches the feature off, and the No Random Posts plugin is optional.
WordPress 7.2 adds a /random/ address that sends visitors to a random post
The address works like this. Someone types yoursite.com/random/ into a browser, and WordPress sends them to a randomly selected published post on your site. The November 5, 2026 dev note from WordPress core says the feature is on by default. A dev note is the short write-up WordPress contributors publish to explain a change to developers.
The send-off is a redirect, which means the address forwards the visitor to a different address. It is a temporary one, called a 302, the number web servers use for "found somewhere else for now." Each visit can land on a different post.
The same idea covers narrower paths. There are random addresses for a category, a tag and an author, so a path starting with /random/category/ followed by a category name picks a random post from that category. Custom post types, the special kinds of content some sites add for things like portfolios, events or listings, get one too.
Regular posts can be picked. Custom post types may be picked as well when they have public archive pages, unless the developer opted them out. A site with only regular posts has the simplest case, and a site with several custom post types has more to review.

A temporary redirect is something Google already knows how to read
Google's own pages describe the pieces involved. On redirects, Google says a 302 is temporary, that Googlebot (Google's crawler, the program that visits pages) follows it, and that it is not used as a signal for choosing which address is the main one. So, a /random/ visit forwards to a post, and the post keeps its own address.
The test versions added a second layer. In the WordPress Hosting team's November 12, 2026 testing notice, /random/ and ?random answered with a 302 and an X-Robots-Tag header of "noindex, follow." A header is a note a server sends along with a page, and this one tells search engines not to list the address while still following its links.

Google's page on blocking indexing says a page with a valid noindex rule is dropped from results, and that the rule has to stay crawlable so Googlebot can see it. Google's robots.txt introduction adds that robots.txt controls crawling, not guaranteed removal from results, and that a blocked address can still appear if other pages link to it.
| Piece | What Google's page says | What it means for /random/ |
|---|---|---|
| 302 redirect | Temporary; Googlebot follows it; not a signal for the main address | Visitors are forwarded to a post each time |
| noindex rule | A valid rule drops the address from results; it must stay crawlable | The test versions sent it; confirm it after you update |
| robots.txt | Controls crawling, not guaranteed removal from results | A robots.txt line is not a reliable way to keep /random/ out of results |
A plugin author and some commentators have argued that /random/ could cause trouble for search. Treat that as one view to weigh against the checks below, since those checks show what your own site actually does.
One short message to your webmaster covers the whole update
Your webmaster is whoever looks after your site: a freelancer, an agency or your host's support team. Send this message before your update window opens. It asks for the test on a staging copy, which is a private duplicate of the site where an update can be tried safely.
> Hi, WordPress 7.2 is scheduled for December 8, 2026 and adds a /random/ address that is on by default. Before we update, can you try it on a staging copy and tell me: > > 1. What does /random/ return, and where does it send you? > 2. Which post types can it pick, including any custom post types with public archives? > 3. Do the response headers still show a 302 and a noindex note? > 4. Were caching and rewrite rules refreshed after the update? > 5. Should we keep the feature, or turn it off with the wp_enable_random_content_redirect filter? > > Please check /random/ again on the live site once we update.
Two of those terms are worth knowing. Rewrite rules are the list WordPress keeps of which web addresses go where, and saving the Permalinks screen refreshes it. A cache is a saved copy of your pages that speeds the site up, and it can hold on to an old answer for an address like /random/.
Question 2 deserves a slow answer if your site has custom post types. A portfolio or event listing is meant to be seen. A set of client documents is not, and a public archive page is what makes a post type eligible, so your webmaster should say which of your types qualify.
If your site is still on an older 7.1 version, the security update comes first. Our post on the WordPress 7.1.4 security release, updated for 7.1.5, shows how to check your version in a couple of minutes.

Turning /random/ off takes one line, and the plugin is optional
The dev note's way to switch the feature off is a single line of code: `add_filter( 'wp_enable_random_content_redirect', '__return_false' );`
A filter is a hook that lets code change how WordPress behaves. The dev note places this one in a small must-use plugin, a file WordPress loads automatically on every page. With it in place, WordPress stops generating the random addresses, hides the Random base field on the Permalinks screen, and ignores the ?random version of the address.
Use the name exactly as the dev note gives it. Earlier development material used a slightly different name, and a hook with the wrong name has no effect on the feature.
Whether to switch it off is your decision. A site that gets nothing from random-post discovery, or one whose custom post types hold material meant to stay out of casual browsing, has a reason to. A site that likes the idea can leave it on.
A free plugin called No Random Posts also turns the feature off. It is optional, because the filter does the same job. Its page lists fewer than 10 active installs and a test up to WordPress 7.1.4, so your webmaster should confirm it with 7.2 before relying on it.
After December 8, open /random/ and check Search Console a few weeks later
Once the update is live, open yoursite.com/random/ in a browser three or four times. Note where each visit lands. Ordinary public posts mean it is working as described. A 404 or an unexpected destination goes to your webmaster, who can look at caching, rewrite rules, and whether a page or post already uses the /random/ path.
A few weeks later, open Search Console's Page indexing report, which lists which of your addresses Google indexed and why it left others out. Our guide to pages that are not indexed in Search Console explains each reason. If /random/ shows up as a redirect or as excluded by noindex, that would fit how the test versions behaved.
If anything appears as a soft 404, an address that looks like an error page to Google even though the server calls it fine, our post on the soft 404 in Search Console covers what to do.
Run these checks on the live site rather than assuming. The final release may handle /random/ combined with a search query differently from the test versions, and a browser test is the quickest way to see what your own site does.

The 7.2 dates run from the November 5 dev note to the December 8 release
The dev note appeared on November 5, 2026. WordPress published release candidate 1 on November 17 and said it includes improvements to the random-content redirect feature. A release candidate is a near-final version released for last testing. The 7.2 schedule lists release candidate 2 for November 18 and the final release for December 8.
WordPress 7.2 dates
- 1
November 5, 2026
WordPress core publishes the dev note describing /random/.
- 2
November 17, 2026
Release candidate 1 arrives, with improvements to the random-content redirect.
- 3
November 18, 2026
Release candidate 2, per the 7.2 schedule.
- 4
December 8, 2026
Scheduled final release of WordPress 7.2.
Do you know what /random/ does?
Pick an answer to begin.
1. What does yoursite.com/random/ do once WordPress 7.2 is installed?
2. What does Google say robots.txt does?
3. How does the dev note say to turn the feature off?
Frequently Asked Questions About WordPress 7.2 Random Redirect
What does the WordPress 7.2 random redirect do?
It sends a visitor who opens yoursite.com/random/ to a randomly selected published post through a temporary redirect. The feature is on by default, according to the November 5, 2026 dev note.
Is the /random/ redirect a 301 or a 302?
In the test versions it answered with a 302, the temporary kind. A 301 is the permanent kind, used when an address has moved for good. Check the live response after you update.
When is the WordPress 7.2 release date?
WordPress has scheduled the final release for December 8, 2026. Release candidate 1 came out on November 17 and release candidate 2 is listed for November 18.
How do I turn off the random post redirect in WordPress?
Ask your webmaster to add the filter from the dev note, `wp_enable_random_content_redirect`, set to return false. After that, WordPress stops creating the random addresses.
Which posts can /random/ pick?
Regular posts can be picked. Custom post types with public archives may be picked too, unless the developer opted them out, so your webmaster should review any custom types your site has.
Should I block /random/ in robots.txt?
A robots.txt line controls crawling, not guaranteed removal from results, and Google says a noindex rule has to stay crawlable to be seen. Ask your webmaster to check the response headers first, and to use the filter if you want the feature gone.
Final Thoughts
WordPress 7.2 adds a /random/ address on December 8, 2026. It sends visitors to a randomly chosen published post by temporary redirect and is on by default. Google's pages explain how it treats redirects, noindex and robots.txt, and the test versions marked the redirect noindex. Your part is one message to your webmaster, a decision about keeping the feature, and a look at /random/ after the update.
Those small steps keep the update an ordinary maintenance job. You will know what the address does on your site, which of your post types can appear, and how to switch it off if you would rather not have it.
If you would like a second pair of eyes, Web Leveling can run these checks with you, from the /random/ response to your Search Console reports. Our search engine optimization work is a good starting point, and our web design and website maintenance work cover the site itself and its updates. We make no promises about rankings; we show you what the site does and what to change. We work with small and medium businesses across the country and overseas. Ask us to look at your site before the update, and we will reply with what we find.
Terms
Words used in this post
Tap a term to see what it means.
Redirect. A rule that sends a visitor from one web address to another.
302. The status number a server uses for a temporary redirect.
noindex. A note telling search engines not to list an address in their results.
robots.txt. A file that tells crawlers which parts of a site they may visit.
Custom post type. A special kind of content a site adds beyond regular posts, such as events or listings.
Rewrite rules. The list WordPress keeps of which web addresses go where.
Staging copy. A private duplicate of a site where an update can be tested safely.




