TEARDOWN 115 · REVIEWED 2026-08-21
SEOTesting
SEOTesting connects to a website's Google Search Console and Google Analytics accounts to run before-and-after tests on SEO and content changes, flag content decay and keyword cannibalization, and turn the results into client-ready reports — including a newer feature that infers which AI-chatbot prompts are sending a page traffic.
Pulling a website's own Google Search Console and Analytics data is free and exactly what Google's own reporting APIs are built for — request the before and after date ranges for a page or query, diff the clicks and impressions, and you have the same before-and-after comparison the tests are built on.
What you lose building it yourself
- ✕A tested statistical method for isolating a change's real impact from seasonality or algorithm noise
- ✕Built-in content-decay and keyword-cannibalization detection across a whole site
- ✕A feature inferring which AI-chatbot prompts are likely driving a page's clicks
- ✕Polished, white-label client reports with annotations and a changelog, ready to send
Why people still pay
A DIY script can diff two date ranges of Search Console data in an afternoon; what SEOTesting actually sells is a tested method for telling a real change from normal noise, automatic decay/cannibalization detection across a whole site, and reporting polished enough to send a client without extra work — building and maintaining all of that yourself is the harder, ongoing part.
A BASIC DIY SEARCH CONSOLE BEFORE/AFTER TESTER
Connect the Google Search Console API and Google Analytics (GA4) API for a site you own, pull clicks, impressions, and click-through rate for a page or query across a before and after date range, and chart the difference. An AI coding tool can build this comparison script in an afternoon, but SEOTesting's real value is its tested statistical methodology for isolating a real change from normal seasonality or algorithm noise, automatic cannibalization/decay detection across a whole site, and polished client-ready reporting — that takes real, ongoing product work to match.
StackThe Google Search Console API (OAuth or a service account) · the Google Analytics Data API (GA4) · a small script or notebook to diff two date ranges · a spreadsheet or simple chart for the before/after comparison.
Build a Python script using the Google Search Console API and the Google Analytics Data API (GA4) for one verified site. Given a page URL or query, a change date, and an equal-length before/after window (e.g. 28 days each), pull clicks, impressions, click-through rate, and average position for both windows, then print the percentage change for each metric. Also pull GA4 sessions and conversions for the same page and windows. Cap the script to one site and one comparison per run, and handle the case where Search Console returns no data for a window by printing a clear warning instead of crashing.
Similar tools
Free alternative: advertools — a free Python library that covers bulk Google Search Console data pulling and analysis, but you'd have to build the before/after statistical comparison, cannibalization detection, and client reporting yourself
QUESTIONS
Does SEOTesting replace Google Search Console, or sit on top of it?
It sits on top — SEOTesting has no ranking or traffic data of its own; every number it reports comes from a site's own connected Search Console and Analytics accounts.
What is a 'split test' in SEOTesting, as opposed to a time-based test?
A time-based test compares a page's performance before and after a single change; a split test rolls a change out to only some pages in a group and compares them against the untouched pages over the same period, which better isolates the change from outside noise like seasonality.
How does it measure AI-chatbot traffic if Search Console doesn't track that directly?
It infers likely prompts from referral and query patterns already present in Search Console and Analytics data, rather than pulling anything directly from ChatGPT, Gemini, or other platforms — a proxy signal, not a direct citation feed.