WordPress 7.2's planned random-post redirects will use existing archive filters to shape which published content visitors encounter. The feature is enabled by default, WordPress contributor Aaron Jorbin explained in a November 5 Core developer note, and runs through WordPress's main query.

TutKit reported November 5 that archive customizations can affect selection. WordPress released Beta 4 on November 3 and remains in beta, with the final release scheduled for December 8, according to the Beta 4 announcement. WordPress designates the beta for testing and development in local or test environments.

The beta is available for browser-based testing through WordPress Playground.

Which Content Enters the Random Pool

The `/random/` endpoint redirects a visitor to a randomly selected published post. Built-in posts qualify; pages and media attachments do not. Older published posts can include outdated advice and expired offers, WP Within reported November 5.

Custom post types gain a registration argument named `randomable`. Its default is `true` when the type is publicly queryable and has an archive. Developers can explicitly set it to `false` to exclude a type, Jorbin wrote.

Selection can also be narrowed by category, publicly queryable taxonomy, author or eligible custom post type. The route `/random/{post-type-slug}/` targets a particular type. Those scoped routes give the site's category and tag architecture another role in discovery: organizing the pool from which a visitor receives a selection.

How WordPress Random Redirects Use Archive Filters

Under the hood, `WP::handle_random()` temporarily adds three callbacks that restrict eligibility, apply `RAND()` ordering and limit selection to one database row. Existing callbacks on `pre_get_posts`, an archive-query hook, also affect that archive's random redirect, according to Jorbin's note.

Developers also gain `wp_is_random_content_query()`, which identifies a random-content request. That allows exclusions specifically for random selection. The distinction gives maintainers two places to express content rules: existing archive customization and logic aimed directly at random requests.

Search Requests and Database Sorting

October beta behavior included random selection from search results through `/?s={keyword}&random`, according to the official testing guide. The expected October beta behavior was a temporary HTTP 302 redirect with `noindex` headers, or a 404 response when nothing matched.

October beta testers were asked to make repeated requests to `/random/` and verify category and author restrictions. Testers were also asked to rename the random base, save the setting and verify the new route. Those tests addressed three distinct behaviors: destination selection, archive boundaries and URL configuration. That distinction matters for customized sites: a working redirect alone does not establish that the selected content fits the intended archive.

Only published content without a password qualifies, Dr. Web reported November 5, citing the source code. Database random sorting is also a performance consideration, Dr. Web reported. That makes query behavior relevant to both content eligibility and the database work involved in choosing a destination.

A Default With an Explicit Off Switch

Returning `false` through `wp_enable_random_content_redirect` disables the random rewrite rules, hides the random-base field in permalink settings and causes WordPress to ignore the random query variable. When enabled, the base is translatable and customizable on the Permalink Settings screen.

Alongside the WordPress 7.2 SVG icon compatibility changes, random redirects introduce another beta-testing concern, focused on content selection and archive behavior.

The central upgrade question is how existing publishing choices translate into the eligible pool. Expired offers and outdated advice illustrate the editorial stakes: published status and suitability for renewed discovery can be different judgments.

Image: AI-generated image.