Retrospective SEO Tests
Bailey Allen
Currently, the 'SEO test' feature requires setting a 'control' start date from
today
, waiting 1–2 weeks, implementing a change on a pre-set date, and then waiting another 1–2 weeks for results.Since these tests rely on Google Search Console data, it would be far more efficient to select a past change date and set a lookback / look-forward window (e.g. 14 days before vs 14 days after) to evaluate the impact.
If a test's finish date extends into the future, the system should assign an 'In Progress' status and offer an email notification upon completion.
Tests should support multiple granularities: single pages, page groups, single keywords, and keyword groups.
Pulling day-by-day performance data via the GSC API is likely the best implementation method. SEOTesting.com offers a good reference for this workflow.
Proving that specific actions drive measurable organic results is a major challenge in SEO, and this feature would make attribution far easier.
As a bonus, integrating GA4 metrics like engagement rate, average engagement time, conversions, and revenue alongside GSC data would provide full-funnel impact analysis.