Split URL Testing

Split URL testing is an A/B testing approach where each variant is hosted on a separate URL, with traffic divided between the original page and one or more alternative pages — also called a redirect test.

Split URL testing (also called a redirect test) is a form of A/B testing where each variant lives on a completely separate URL. Instead of injecting changes into a page via JavaScript, visitors are silently redirected — server-side — to a different URL based on which variant they've been assigned.

The original page might be /landing, and the test variant might be /landing-v2. A visitor assigned to the variant is redirected to /landing-v2 before the page renders, with no visible change to the browser address bar.

How It Differs from Standard A/B Testing

Standard A/B testing modifies the existing page via a JavaScript snippet after it loads. The visitor lands on the same URL; the testing platform adjusts the DOM before it's visible. This works well for smaller changes — headlines, button colors, copy tweaks — but struggles with large structural differences.

Split URL testing is better when:

  • The variant requires a fundamentally different layout or template — full redesigns, new page frameworks, or entirely different content structures
  • You want to eliminate the flicker effect — since no client-side DOM manipulation occurs, there's no flash of the original content before the variant appears
  • Your team has built fully separate pages — comparing /v1 vs. /v2 is operationally easier than managing heavy JavaScript-based modifications

Common Use Cases

  • Full page redesigns — Testing a completely new page template against the existing one
  • Different URL structures — Comparing /pricing-detailed against /pricing-simple
  • Platform migrations — Testing a new CMS-built or framework-built page before committing to a full migration
  • Dedicated landing pages per ad group — Running separate pages per campaign and comparing performance in aggregate

SEO Considerations

Split URL tests require care around indexability. If a variant page gets crawled and indexed, it creates duplicate content issues and can dilute ranking signals. Standard precautions:

  1. Add a canonical tag on variant pages pointing back to the original URL
  2. Set noindex on variants for the duration of the test
  3. Redirect the loser to the winner URL after the test concludes, then remove the losing page

Split URL vs. Server-Side Testing

Server-side testing also avoids flicker — but it delivers variant content from the same URL by branching logic before the response is sent. Split URL testing is a specific implementation where traffic physically navigates to a separate location. Server-side is cleaner from an SEO standpoint; split URL is easier to implement without server-level code changes.