All terms

CRO Glossary

Redirect Test

A test that sends visitors to entirely separate URLs per variant, rather than modifying a single page in place.

A redirect test (sometimes called a split URL test) routes traffic to different live pages hosted at distinct URLs, as opposed to A/B tests that swap content on a single page via JavaScript. This approach is typically used when the variant is a fundamentally different page design, layout, or template — a full redesign rather than an incremental change — since building that as a client-side DOM change would be impractical or introduce flicker.

The tradeoff is that redirect tests usually rely on a redirect at the server or edge layer, which adds a small amount of latency and can create discrepancies in analytics if the redirect isn't handled cleanly. They also require care with URL parameters, canonicalization, and SEO, since search engines may index the wrong variant or split link equity across pages if the test isn't set up with proper no-index or canonical tags on the non-primary variant.

A typical example: an e-commerce team wants to test a completely rebuilt product page template against the current one. Rather than trying to inject the new layout via JavaScript, they host the new template at a separate URL and use a redirect rule so that a defined percentage of visitors to the original URL are sent to the new one, with analytics tagging the variant based on which URL the user landed on.

Related terms

See this in the wild

ABWatcher watches how top teams apply redirect test.

Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.