Back to Cookbook

Search Console Impact Diff

Pinpoint where organic traffic changed and why

Create a tight "before vs after" diff for Google Search Console (queries, pages, CTR, position) to identify the specific segments driving traffic loss or gains. Produces a prioritized action list and hypotheses per segment.

House RecipeWork8 min setup

INGREDIENTS

🔎Web Search📄Google Docs

PROMPT

Build a Search Console before/after impact diff. Output: - Top 10 loss segments with hypotheses (why each dropped) - Top 10 win segments (what to replicate) - Action plan: quick wins (this week) + strategic fixes (this month) - SERP change notes (AI overviews, feature shifts, ad density) Inputs: - Baseline dates: - Affected dates: - Export snippets or summaries: - Primary conversions impacted: - Any known SERP feature changes:

How It Works

This recipe turns vague "SEO is down" into a segmented diagnosis you can act on.

Triggers

  • Post-update traffic drop
  • Clicks down while position is stable (CTR/SERP shift suspicion)

Inputs

  • Two date ranges (baseline vs affected)
  • Query/page exports (top 1k–10k rows)
  • Notes on SERP changes (AI answers, new features, ads density)

Outputs

  • Top loss/gain segments (query class, page type, device)
  • CTR vs position interpretation notes
  • Action plan per segment (content rewrite, snippet optimization, internal links, tech fixes)

Actions / Steps

  1. Rank losses by business impact (not just clicks).
  2. Separate ranking loss vs CTR loss vs indexing loss.
  3. Generate "quick wins" (titles/snippets, internal links) and "structural fixes" (templates, topical authority).

Parameters

  • Minimum impact threshold to include a segment
  • Segment taxonomy (intent, funnel stage, topic cluster)
Tags:#seo#search-console#analytics#content#diagnostics