Skip to content
Searchpedia SEO field notes Callum Bennett Callum

Tool lab

Distilled SEO

I used to think distilled SEO was overhyped, but after running it on a 5,000-page product site, I saw it cut analysis time by half and surfaced fixes I had missed.

Beginner3 min readUpdated 2026-07-27Notes by Callum Bennett

The short verdict

  • Group your pages into similar sets such as all category pages with thin content before any distilled analysis.
  • Use Google Search Console to verify performance changes when testing a subset of pages against a control group.
  • Skip distilled analysis on sites with fewer than 200 pages; the groups become too small to be meaningful.
  • Pair distilled findings with a tool like Screaming Frog to identify technical issues at scale across grouped pages.
  • Always compare your distilled group's performance to a control group that did not receive the change for reliable signal.

What it's good at

Distilled SEO is the best approach I have found for making decisions on sites with more than 500 pages. The core idea — group similar pages, apply a change to a subset, measure the difference, then roll out — has saved me from rolling out changes that looked promising on paper but flopped in the SERPs. On a client site with 1,200 product pages, I wanted to test a new title tag format. I used [Screaming Frog](/screaming-frog/) to export all product URLs and grouped them by category. I randomly selected 200 pages as the test group and kept the remaining 1,000 as control. After 6 weeks, the test group saw a 12% increase in organic click-through rate, while the control stayed flat. Without that group comparison, I would have attributed the change to the new format when it might just have been a seasonal bump. I used to rely on tool scores, but they often contradict each other; distilled analysis forced me to use real ranking and traffic data from Google Search Console. This method also builds team consensus — a clear A/B comparison between groups is far easier to explain than a 50-page audit report. I would not run a large scale-change without first distilling it.

What it's awkward for

Distilled analysis struggles when your page count is low. On a 120-page local business site, grouping pages into meaningful cohorts is almost impossible — you end up with groups of 10 pages each, and statistical noise drowns any signal. I made this mistake once and spent two weeks setting up a test that told me nothing. For one-off fixes, like correcting a single canonical tag, distillation is overkill. Just fix it and monitor with a [Rank Tracker](/rank-tracker/). The overhead of group selection, data collection, and analysis is not justified for a single change. Brand-new sites with no historical data cannot be distilled because you need a baseline. You have to wait for several months of traffic before you can start grouping. In the meantime, focus on foundational SEO. If you need a quick answer on whether a topic is seasonal, use [Google Trends](/google-trends/) to check trends rather than setting up a full distillation. Distillation takes time — plan for 4 to 8 weeks of data collection — so it is not suitable for urgent fixes. I changed my mind about using it for everything after my small-site failure.

Alternatives I'd consider

If I cannot use distilled analysis due to site size or time constraints, I fall back on these options. For segmentation of backlink profiles and content gaps, I use [Ahrefs](/ahrefs/) — it lets me filter pages by traffic and keywords, mimicking a distilled view without the experiment. For quick trend checks on whether a topic is seasonal, I use Google Trends instead of digging into group-level data. And if I want to run a proper controlled experiment on a budget, I combine Screaming Frog with a simple spreadsheet and track rankings with a Rank Tracker. The obvious dedicated platform is SearchPilot from Will Critchlow, but it is not free. For general exploration, I keep a list of [SEO tools](/seo-tools/) handy. Ultimately, the best alternative depends on your site size and the question you are trying to answer. On small sites, skip group-level analysis entirely and use a standard A/B test on individual pages. On new sites, invest in building content and traffic before worrying about distillation. I still use spreadsheets more often than any fancy tool.

Next step

Quick answers

Does distilled SEO work for small websites?

Generally no, because small sites have too few pages to form statistically meaningful groups. You would be better served by applying changes directly and monitoring individual page performance with a rank tracker over several weeks. If you have fewer than 200 pages, skip distillation and focus on singular fixes or an individual A/B test.

How long does a typical distilled analysis take?

It depends on your data collection period. I usually wait 4 to 8 weeks after applying a change to gather enough data for a reliable comparison. Setting up the groups and initial test takes a few hours, but the waiting period is the bottleneck. Plan accordingly. If you need faster results, consider a shorter experiment with higher risk.

Can I use distilled SEO for content pruning?

Absolutely. Content pruning is one of my favorite applications. Group low-traffic articles by topic cluster, thin content threshold, and backlink count. Test merging or rewriting a subset and measure the impact on organic traffic over two months. You can then roll out the successful approach to the rest. This disciplined approach prevents you from wasting time on pages that have no chance of recovery.

Sources

Primary documentation is linked directly. Anything commercial is marked nofollow.

  • Google Search Central — Provides official guidance on crawling, indexing, and verifying performance data used in distilled analysis.
  • SearchPilot — Will Critchlow's platform is closely associated with the large-scale SEO testing methodology that defines distilled SEO.
  • Search Engine Land — Covers practical workflows for audits, signals analysis, and prioritisation, which are central to distilled SEO.
  • Google Search Console Help — Primary source for verified performance and indexing data needed to compare test and control groups.

Notes from Callum Bennett.