GSC Query-Gap Prompt Expansion

If a query already sends you organic traffic, you have a reason to know whether AI assistants answer it the same way search does — but you can’t know that if Scrunch isn’t tracking it. This workflow finds that blind spot and closes it, expanding prompt coverage based on queries you’ve already proven matter.

Tools used in this workflow

Tool	Required?	Used for
Scrunch MCP	Required	Checking existing prompt coverage and creating new prompts
Google Search Console MCP	Required	Sourcing real search queries you already rank for

Looking for content gaps instead of monitoring gaps? Use Where Search Rankings and AI Presence Diverge — that workflow finds pages that need new or improved content. This one just makes sure you’re watching the right queries in the first place.

For [brand name] / [domain], find search queries we rank for that aren't tracked as Scrunch prompts yet, and create prompts for the highest-value gaps.

Step 1 — Pull our real search queries:
From Google Search Console, get the top [50] queries by impressions for [domain] over the last 90 days, where we rank in the top 10. Include impressions, clicks, and average position for each.

Step 2 — Check existing coverage:
List all prompt variants currently tracked for [brand name] in Scrunch. Compare against the Step 1 query list — which of our top-ranking search queries have no closely-matching Scrunch prompt at all?

Step 3 — Prioritize the gaps:
Of the uncovered queries, rank by impressions — these are the ones worth monitoring first since they represent proven search demand.

Step 4 — Create prompts for the top gaps:
For the top [10] uncovered queries, create a Scrunch prompt for each, phrased as a natural question rather than the raw keyword string. Tag each one "gsc-expansion" so we can track this batch separately, and assign the appropriate funnel stage based on query intent (informational = awareness, comparison/branded = consideration or decision).

Step 5 — Confirm:
List everything created, with the original search query, impressions, and the prompt text Claude generated for it.

What you get: A batch of new Scrunch prompts sourced directly from queries you already know drive real search traffic — so your AI monitoring coverage starts where your proven search demand already is, instead of guessing.

Tips

Rewriting keywords as natural questions

Search queries are often keyword fragments (“best crm small business”), but AI assistants get asked full questions (“what’s the best CRM for a small business”). Step 4 asks Claude to rephrase — check a few of the generated prompts to make sure the intent held up in translation.

Re-running this quarterly

Search rankings and query volume shift over time — re-run this every quarter to catch new queries you’ve started ranking for since the last pass, rather than treating prompt coverage as a one-time setup task.

Filtering by page or section first

If [domain] is large, scope Step 1 to a specific subdirectory or page group (e.g. “queries where the ranking page is under /pricing/”) to keep this workflow focused on one part of the business at a time.

What to do once these prompts have data

Give new prompts 30 days to accumulate observations, then run the Rankings & Priority Lists prompts from the Prompt Library — the “gsc-expansion” tag makes it easy to filter to just this batch and see how AI presence compares to the search rank you started from.

Where Search Rankings and AI Presence Diverge

For finding content fixes rather than monitoring gaps.

Build Your Prompt Library from SEO Keywords

A broader keyword-list version of this same idea, sourced from Semrush/Ahrefs instead of GSC.

⌘I

​Tips

Where Search Rankings and AI Presence Diverge

Build Your Prompt Library from SEO Keywords

Tips