Skip to content
Join the waitlist

Measurement

Minimum Detectable Effect

The minimum detectable effect is the smallest true effect a test can expect to find statistically significant with a chosen probability, its power, at a chosen significance level. It is set before a test from the sample size and the noise of the metric: the fewer the pages or visits, the larger the effect must be to show.

  • Industry term

By QueryRev ResearchPublished Updated7 min read

Why it matters.

Every test can see some effects and not others. J-PAL, the Abdul Latif Jameel Poverty Action Lab, defines the minimum detectable effect as the smallest effect that, if true, has a chosen chance of producing an estimate that is statistically significant at the chosen level. Below it, the lab says, we may not be able to distinguish an effect from zero even if it is real[1]. A test that cannot see the lift you hope for is a test whose miss means little.

Several things set it. J-PAL describes the usual settings as a significance level of 0.05 and a power of 0.8, and lists the other inputs: the sample size, the variance of the outcome and the share of the sample given the change. A bigger sample, a smaller variance and an even split between the groups all lower the minimum detectable effect. Observations that are correlated within a cluster raise it, which in general increases the required sample size[1].

There is no number without assumptions. NIST says the question of how many measurements to include has no correct answer without additional information or assumptions, and that the answer is influenced by the risk of rejecting a true hypothesis, the risk of accepting a false one and the standard deviation. For a two-sided test at 0.05 with a 0.10 risk of missing the shift, its table gives 43 measurements to detect a shift of half a standard deviation and 11 to detect a shift of one[2].

The relation is a square. Kohavi and colleagues give the sample size as (4rσ/Δ)², for 95% confidence and 90% power, where r is the number of variants, σ the standard deviation and Δ the smallest difference to be found[3]. They note that asking to detect a 20% change in conversion instead of a 5% change, a factor of 4, cuts the users needed by a factor of 16[3]. Halve the lift you want to see and you need about four times the pages.

The same arithmetic applies to the groups inside a survey. QueryRev’s study reads 6,294 sites, and 1,339 of them, 21.3%, name at least one AI crawler in robots.txt[4]. A share worked out within those 1,339 rests on about a fifth of the sites read, so it needs a larger difference to stand out than a share across all 6,294.

How it is measured.

Work forwards from what you have. Take the weekly clicks per page, their spread from past weeks, the number of pages in each group and the weeks you can run. With a significance level of 0.05 and a power of 0.8, J-PAL’s formula gives the smallest effect the test could find[1]. It shrinks as the sample grows and as the variance falls.

Or work backwards from the lift that matters. If the business needs a lift of 10% to make a change worth the cost, the formula gives the number of pages, or weeks, needed to find a lift of that size[1]. Remember the square: halving the target about quadruples the pages[3].

Check the assumptions and write the answer as a range. The figure rests on the spread of past data, on the groups being independent and on the metric behaving as it did before. Pages of one site share a domain, links and releases, so they are not fully independent. Treat the result as approximate.

Measured by

  • Pages or visits in the test
  • Noise of the metric
  • Smallest lift it can show

A worked example.

Illustrative: an invented site, to show the method.

A coffee-equipment shop can change titles on 40 kettle pages, on 200 grinder pages or on all 1,100 product pages. Using eight weeks of past clicks for each set, it works out the smallest lift each could show at a significance level of 0.05 and a power of 0.8. The answers are approximate, so it writes them as ranges: a lift of about 22% to 32% for the kettle pages, 10% to 14% for the grinder pages and 4% to 6% for all product pages.

The business needs a lift of 10% to make the work worth doing. Forty pages cannot show that: a test on them would miss a 10% lift most of the time, and a miss would say nothing about the change. The grinder pages are borderline. The full catalogue could show it with room to spare, but a test needs untouched pages to compare with, and the shop will not change everything at once. It plans the grinder test for 12 weeks instead of eight, which should pull the range down, and it will report a miss as “too small to see”.

The smallest lift each set can show

What to do, step by step.

  1. Choose the metric and the length of the test, such as clicks per page per week for eight weeks.

  2. Take the spread of that metric from past weeks of the same kind of page.

  3. Set the significance level and the power before you start. J-PAL describes 0.05 and 0.8 as the usual settings[1].

  4. Work out the smallest lift each set of pages you could use would show, and write it as a range.

  5. Compare it with the lift that would matter to the business. If the smallest detectable lift is larger, use more pages, run more weeks, or choose a metric with less noise.

  6. Write the figure beside the result when you report it, so that a miss reads as “too small to see” and not as “nothing there”.

Mistakes to avoid.

  • Running a test that cannot see the effect. If the smallest lift a test can show is larger than the lift you can hope for, the test is likely to miss it. Work the figure out before you spend the weeks.

  • Borrowing the wrong noise. The spread of another page type, or of a different season, gives a wrong minimum detectable effect. Use past weeks of the pages you will test.

  • Forgetting the square. The sample size grows with the square of the noise divided by the difference to be found[3]. Halving the lift to be found about quadruples the pages needed.

  • Counting pages as if they were independent. J-PAL notes that observations within a cluster are more alike than observations across clusters, and that this in general raises the sample needed[1]. Pages of one site share links, templates and releases, so each counts for less than one.

  • Reading a miss as no effect. A result below the minimum detectable effect cannot be told from zero, even if the effect is real[1]. Report that the test was too small to see it.

How QueryRev treats it.

QueryRev verifies a change against a modeled baseline, and its verification page puts the arithmetic in plain words: the window is set for each change, and a quiet page needs a longer one. A result that cannot be told apart from the baseline is reported as no effect, not as a small win, and the lift is shown as a range. The smaller the page, the longer the last step of the loop takes: the revenue a page earns, the decision to change it, and an outcome that counts once it is verified. See SEO split testing, pre-post analysis, conversion rate and the guide to SEO forecasting.

Questions people ask.

What is a good minimum detectable effect?

One smaller than the lift that would matter to the business. There is no universal number: it depends on the noise of the metric and on how many pages or visits you can test. If the smallest lift you can show is larger than the lift you expect, change the design.

How do I make a test able to see a smaller effect?

Use more pages or visits, run it for more weeks, pick a metric with less noise, split the sample evenly between the groups, and match the groups so that less of the noise comes from differences between them. Each of these lowers the smallest effect the test can show.

Is the minimum detectable effect the effect I expect?

No. It is a property of the test design: the smallest effect the test is able to find. The expected effect is what you hope the change will do. If the expected effect is smaller than the minimum detectable effect, the test is likely to miss it.

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. Power calculationsJ-PAL (Abdul Latif Jameel Poverty Action Lab) ·

  2. Sample sizes required (e-Handbook of Statistical Methods, 7.2.2.2)NIST ·

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

  4. 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. “Minimum Detectable Effect.” QueryRev AI glossary, 25 October 2026. https://queryrev.com/glossary/minimum-detectable-effect#definition

Related terms