The Position 5–20 Method: Finding Your Highest-ROI AI-Citation Opportunities in Search Console

Somewhere in your Search Console data right now sit a handful of keywords with an unusual property: they're one content rewrite away from being cited by AI answer engines. Not one link campaign, not six months of authority building — one structural rewrite. They're sitting at positions 5–20, and almost nobody works them systematically.

This is the complete method. It has five phases: extraction, prioritization scoring, the rewrite, publishing, and delta measurement. Done manually it's a day of focused work; it's also the default pipeline in the Scrabio GEO platform, which runs it end-to-end in one analysis.

Why positions 5–20 are the GEO sweet spot

The band isn't arbitrary. Three conditions intersect there:

1. Retrieval eligibility. Answer engines draw candidates from search indexes. Position 5–20 means the page is reliably retrieved for the query — the first precondition of citation. A page at position 60 is invisible to the pipeline no matter how well it's written.
2. Authority validation. Google's ranking system has already judged the page topically strong. You don't need to earn trust — you need to repackage for a different consumer (the passage selector, not the human scroller).
3. The gap is structural. Pages in this band usually rank on authority while failing the extraction test — answer buried mid-paragraph, heading that doesn't mirror the question, register mismatch. Structural gaps are the cheapest gaps to close.

Compare the alternatives: position 21+ needs authority investment before GEO pays; position 1–4 already wins the click — the only question there is defending the AI answer too. The 5–20 band is where effort converts fastest. It's also, conveniently, a band your client or boss can understand: "these pages are trusted, they're just not built for the new consumer."

Phase 1 — Extraction (10 minutes)

Search Console → Performance → Search results → Queries tab →

• Filter: Position greater than 5, less than 20 (or export all and filter in a sheet — cleaner for the next steps)
• Sort: Impressions, descending
• Window: last 28 days

Group the export by the page each query triggers (the query→page mapping is in the export). Then aggregate: you're looking for the handful of pages that carry most of the 5–20 demand. In most properties, 5–8 pages carry 80% of it.

Also pull: for each priority page, its top 5 queries verbatim — including the embarrassing ones. Typos, dialect, fragments. This is the language your rewrite must mirror, and why it matters.

Phase 2 — Prioritization scoring (15 minutes)

Not all 5–20 keywords deserve the same urgency. Score each page-cluster on four factors, 0–3 each:

The last factor needs the citation test — ask the question, see who's quoted. "Competitor cited" scores highest because the answer is being built on live sources and you're just losing the quote.

Priority = the sum. Anything ≥ 9 is this week's work. Anything ≤ 4 waits for the next cycle. This scoring keeps the rewrite list honest — most properties generate far more 5–20 keywords than any team can rewrite, and prioritization is the discipline that makes the method compound.

Phase 3 — The rewrite (the actual GEO)

For each priority cluster, produce dual-format content per topic — this is the core of the method, and the part where most attempts fail by writing only one format:

1. The target prompt — the question exactly as the cluster's queries phrase it (cleaned grammar, preserved phrasing and language)
2. Heading version — H2/H3 built around the prompt, answered in the first sentence, paragraph passes the self-containedness test
3. FAQ version — the question as a literal Q&A pair, answer tight and quotable
4. The score — evaluate both on the five citable-passage properties and publish the winner per topic

The format decision, the language register, and the scoring are exactly what the decision framework covers — and what the platform automates. What you must not do is bury the answer three sentences deep: the passage selector reads first sentences.

One more rewrite rule: place the new sections where they belong topically on the page — usually directly under the existing H1 or beside the section currently answering the topic badly. Don't append a FAQ graveyard at the bottom; passage selection doesn't care about page position, but internal linking and crawl freshness benefit from prominence.

Phase 4 — Ship and trigger the re-crawl

Publish. Then request indexing in Search Console (URL inspection → Request indexing) for each touched page. Re-crawl latency is the silent killer of GEO momentum — a page rewritten Monday and crawled three weeks later is three weeks of lost citation experiments.

Phase 5 — Measure the delta (the part that makes the method stick)

Wait 7–14 days, then measure three things per target keyword:

1. Citation test: ask the target prompt in each engine. Cited? Which position in the sources?
2. Position drift: did the rewrite also move classic rankings? (It usually does — answer-first structure helps CTR.)
3. Impression → click conversion: did CTR recover on the query?

The delta — before vs after — is the report that keeps GEO funded. "We rewrote 6 sections; citations went from 0 to 4 of 6; CTR on the targets rose 38%." No projection required; it's all measured.

Running it at scale

Manual, the full method is roughly a day per cycle for a 20-page scope — fine for a first pass, unsustainable as a rhythm. Two automations cover it:

• The GEO platform runs phases 1–4 automatically: top pages, real queries, dual-format content per cluster, citation scores, prioritized list. One run per cycle; you review and publish.
• The free GSC MCP server puts Search Console inside Claude or ChatGPT, so phase 1 becomes a prompt ("queries ranking 5–20, sorted by impressions, grouped by page") and phase 5 becomes a follow-up ("compare those queries' clicks vs 28 days ago").

The method's power isn't the filter — anyone can filter 5–20. It's the discipline of scoring priorities, writing both formats, and measuring the delta every cycle. Start with this month's export; by next month you'll have the baseline that makes the month after arguable.