Full Site Tests: Test Your Whole Site Against a Variation Site on Another Domain (Beta)

Test your whole website against a different version of it, the variation site, on another domain or subdomain. Visitors are split between the two, land on the same page they asked for, and stay on the site they were given.

Beta. Full Site tests are new in AB Split Test 3.0.1 and are switched off by default. If you find a problem, let us know.


When to use it

A Full Page test compares one page with another. A Full Site test compares everything.

  • A redesign that lives on a subdomain, such as 2.example.com
  • A rebuild on a new platform, before you move your domain to it
  • A new theme or checkout that changes every page at once

If you only want to test one or two pages on another domain, use External URL Testing instead.

How it works

  • Every visitor to your site joins the test, whichever page they arrive on.
  • Half stay on the original site. Half are sent to the variation site, on the same address. A visitor who opens example.com/pricing/?utm_source=ad and is given the variation site goes to 2.example.com/pricing/?utm_source=ad.
  • They stay where they were put. A visitor given the variation site who comes back to the original later is sent to the variation site again, on whatever page they asked for.
  • Results are in your normal test screen, with one row for the original site and one for each variation site.

Before you start

  • A paid plan.
  • The variation site serves the same addresses as the original. If /pricing/ exists on the original it should exist on the variation site. A page that only exists on the original shows the variation site’s “not found” page to visitors given the variation site.
  • You can add a script to the variation site’s <head>. The variation site does not need to run WordPress.
  • If the variation site is a copy of your WordPress site, deactivate AB Split Test on the variation site and use the embed script there instead. Two copies of the plugin running the same tests will interfere with each other.

Step 1: Turn on Full Site tests

  1. Go to AB Split Test > Settings > Testing
  2. Find Full Site Tests and switch on Enable full site tests
  3. Save

Note: Turning this off again stops every running Full Site test straight away. Visitors stay on the original.

Step 2: Add the variation site as a tracked domain

  1. Go to AB Split Test > Settings > Tracking & Privacy
  2. Add the variation site’s domain, for example 2.example.com
  3. Copy the embed script that is generated for it
  4. Paste the script into the <head> of every page of the variation site

This is the same script used for External URL Testing. It is what records goals and conversions on the variation site.

Step 3: Create the test

  1. Go to AB Split Test > New Test
  2. Under Test Type, choose Full Site
  3. Under Variation sites, enter the variation site’s domain. Just the domain is enough, for example 2.example.com. You do not need to type https://. Your tracked domains are listed under the box, click one to add it.

Note: Only tracked domains are saved. If the box is empty after you save, the domain has not been added in Step 2.

You can add more than one variation site, one per line. Traffic is split evenly between the original and every variation site.

Step 4: Choose a goal both sites can count

The variation site records goals through the embed script, not through WordPress. Choose a goal that works on both sites, or the comparison will not be fair.

Work on both sites

  • URL visit. The best choice for most tests. For a store, *order-received* counts completed orders when the variation site is a store too.
  • Page or post visit. Counted on the variation site by the page’s address, so it works when the page has the same address on both sites.
  • Element click, link click, text on page, scroll depth, time active, JavaScript.
  • HubSpot form. Works when the same form is on the variation site. Enter * as the form ID to count any HubSpot form.

Only count on the original

  • WooCommerce and other store goals
  • WordPress form plugin goals (Fluent Forms, WPForms, Elementor forms and so on)
  • Conversion blocks and modules, the conversion pixel, and Advanced Mode

The editor warns you if you choose one of these. If your site’s default sub goal is a page visit, a new Full Site test starts with it as a URL visit on the same address.

Step 5: Check it in a private window

Launch the test, then open your site in a private (incognito) window while logged out of WordPress.

  • About half the time you will stay on the original. The other half you will land on the variation site, on the same address.
  • Close the window and open a new one to be assigned again.
  • Complete your goal on each site, then check both rows of the results show a visit and a conversion.

Keep pages out of the test

Use URL filtering in the test’s targeting to leave pages on the original. One rule per line, for example:

NOT *checkout*

A visitor who first arrives on a filtered page is not added to the test on that page. They can still join it on the next page they open, and visitors already given the variation site are still sent to it.

Good to know

  • Carts and logins are not shared between domains. A visitor with items in their cart on the original has an empty cart on the variation site.
  • Submitted forms are never redirected. A visitor who posts a form on the original stays on the original for that request.
  • Your other tests keep running, on less traffic. Visitors sent to the variation site are not counted in other tests on the original, so those tests take longer to reach a result.
  • Search engines. Ask search engines not to index the variation site, or point its canonical links at the original, so the two do not compete.
  • The redirect happens in the browser. Full Site tests do not use Cloudflare edge testing or server side redirects.
  • Before downgrading the plugin to a version older than 3.0.1, pause your Full Site tests.
  • Full Site tests are created in the test editor. They cannot be created through the REST API, WP-CLI or MCP yet.

Common questions

Does the variation site need to run WordPress?
No. Any platform works, as long as you can add the embed script to the head of every page and it serves the same addresses.

What happens to a page that does not exist on the variation site?
Visitors given the variation site see the variation site’s “not found” page. Add the page to the variation site, or keep it out of the test with URL filtering.

What if someone opens the variation site directly?
They see the variation site, and are not counted. Only visitors who start on the original and are assigned by the test are counted.

How do I end the test?
Mark it complete. To send everyone to the variation site from then on, tick “Forward all traffic to one variation” and choose the variation site.

Leave a Comment

You must be logged in to post a comment.