Skip to content
Join the waitlist

Measurement

SEO Split Testing

SEO split testing measures the effect of a change on organic search by applying it to one group of similar pages and leaving a matched group unchanged, then comparing the groups over the same weeks. Because a search engine sees one version of each page, it splits pages rather than visitors, and it estimates an effect with its uncertainty.

  • Industry term

By QueryRev ResearchPublished Updated6 min read

Why it matters.

Search cannot be split by visitor. Google’s testing guide explains why a test that sends different visitors to different versions fits search badly: Googlebot generally does not support cookies, so it sees only the version that browsers without cookies are given. Showing Googlebot one set of URLs and people another is cloaking, which is against Google’s spam policies whether or not it is a test[1]. A test of search therefore has to vary pages, not visitors.

The design is that of a controlled experiment. Kohavi, Henne and Sommerfield describe users randomly assigned to a control, usually the existing version, or to a treatment. If the experiment is designed and run properly, they say, the only thing consistently different between the two is the change, so a difference in the measure follows from the assignment, and they stress that the assignment must be random[2]. In a split test the unit is the page. The paper assumes the units are independent, which pages of one site meet only in part, since they share a domain, links and updates. So the result is an estimate.

Where a clean experiment is out of reach, a model fills the gap. Brodersen and colleagues propose a state-space model that predicts the counterfactual response that would have occurred had no intervention taken place, and discuss the strengths and limits of such models where a randomised experiment is unavailable. The model can take account of seasonality and of covariates that move with the outcome[3]. A matched group of untouched pages plays the part of such a covariate.

Time is part of the design. Google says some changes take effect in a few days while others take several months, that in general it is worth waiting a few weeks before assessing the result, and that there is no guarantee changes will have a noticeable effect[4]. It also says that a site running an experiment for an unnecessarily long time may be read as trying to deceive search engines[1].

Assignment shows its worth in any data set. In QueryRev’s study, the top 1,000 sites of the panel block at least one AI crawler by name more often than the rest, 17.6% against 13.9%[5]. Those groups were not assigned at random and differ in many other ways, so the gap is not an effect of rank. A split test assigns pages on purpose to avoid that reading.

How it is measured.

Build the groups before the change. Choose pages of one kind and split them into two groups matched on traffic, past trend and type, by a rule written down in advance rather than by hand. Check the match: a no-change test, which Kohavi and colleagues call an A/A test, should show no difference, and at a 95% confidence level a null test should reject about 5% of the time[2].

Compare the groups over the same weeks. The measure is the difference between the changed group and the control after the date of the change, set against the difference before it. Report it as a range with the method named, because a single figure hides the uncertainty. A range that includes zero shows no effect; it does not show that there is none.

Check what else moved. Anything that reaches every page, such as an update or a season, reaches both groups, which is the reason for a control. Anything that reaches one group only, such as a new link block or a template change, breaks the comparison. Read both groups in Search Console for the whole period.

Measured by

  • Matched pages per group
  • Difference between groups
  • Range of the estimate

A worked example.

Illustrative: an invented site, to show the method.

A retailer has 200 category pages of one kind. It splits them into two groups of 100, matched on traffic and trend, and checks that the groups moved together for 12 weeks. It then rewrites the titles of one group and leaves the other as it was.

After eight weeks, clicks to the changed pages are 11% above their previous eight weeks, and clicks to the unchanged pages 2% above, the season and an update that touched both. A model that predicts the changed group from the control and from the history gives an effect of +6% to +14%, a range, labelled modeled. The retailer reports it for these pages in these weeks, and tests another page type before extending the change to it.

Changed against matched

What to do, step by step.

  1. State the change and the one measure, such as clicks to the pages, before you start.

  2. Choose pages of one kind, enough of them that no single page decides the result, and split them into matched groups by a rule written down in advance.

  3. Check the match in a period with no change: the groups should move together.

  4. Apply the change to one group only, on a date you record in your change log, and change nothing else on either group. Serve the same version to people and to crawlers[1].

  5. Fix the length in whole weeks in advance, long enough for search to respond and no longer than needed[1].

  6. Compare the groups over the same weeks, report the effect as a range with the method named, and say which pages and weeks it covers.

Mistakes to avoid.

  • Splitting visitors instead of pages. Googlebot sees one version of a page, and serving it something different from people is cloaking[1]. Vary pages, and serve each page the same to everyone.

  • Hand-picking the groups. The authors of a practical guide to online controlled experiments say the key is that assignment is random and that no factor may influence it[2]. Pick by a written rule, then check the match.

  • Reporting a single figure. A model-based estimate comes with an interval[3]. A lone number makes the test look more certain than it is.

  • Letting the test run on. Google asks that experiments run only as long as necessary and be removed promptly[1]. Set the end date at the start.

  • Generalising to other pages. A result holds for the pages tested, in the weeks tested. A different page type, market or season may respond differently, so test it before assuming the same.

How QueryRev treats it.

QueryRev does not treat a split test as the default method. Most SEO changes cannot be split between visitors, so a change is verified by comparing what happened with a modeled baseline, and the uncertainty is shown. Where the data and the sample size allow, stronger causal methods are used, and the method is named beside the result (the rules). A group of changed pages set against a matched group is one such method, and its result is a range, never a promise. See counterfactual baseline and the guide to SEO ROI.

Questions people ask.

Is SEO split testing the same as A/B testing?

No. An A/B test sends different visitors to different versions of a page. A search engine’s crawler sees only one version, and showing it something different from people is cloaking, so an SEO split test changes some pages and leaves a matched group of pages alone.

How long should an SEO split test run?

Long enough for search to respond, and no longer than needed. Google says some changes take effect in days and others take months, suggests waiting a few weeks before assessing, and asks that experiments run only as long as necessary. Decide the length in whole weeks before you start.

Can a split test show that a change works?

It gives an estimate, with its uncertainty, for the pages and weeks tested. Pages of one site are not fully independent, and a model has assumptions, so a result is evidence and not a guarantee. A range that includes zero shows no effect, which is different from showing that the change does nothing.

Sources and citation.

Primary sources only: the search engines, the AI vendors, standards bodies and QueryRev’s own research. Each is cited in the text by its number.

  1. Minimize A/B testing impact in Google SearchGoogle Search Central ·

  2. Practical Guide to Controlled Experiments on the Web (Kohavi, Henne and Sommerfield, KDD 2007)exp-platform.com ·

  3. Inferring causal impact using Bayesian structural time-series models (Brodersen et al., Annals of Applied Statistics, 2015)arXiv ·

  4. Debugging drops in Google Search trafficGoogle Search Central ·

  5. State of AI crawler access, October 2026QueryRev Research ·

Cite this definition

A suggested citation. Its link goes to the definition, whose anchor does not change.

QueryRev Research. “SEO Split Testing.” QueryRev AI glossary, 24 October 2026. https://queryrev.com/glossary/seo-split-testing#definition

Related terms