From Analysis to Action: Turning AI Visibility Gaps Into a Content Roadmap

Tracking AI visibility answers one question well: did the brand show up? Across a set of topics, run through ChatGPT, Gemini, Claude, Perplexity, and Google AI Overviews, you get a clean presence/absence signal per prompt per provider. That's the analysis half.

The harder half (the one that actually changes a customer's roadmap) is what happens after the dashboard says "absent." Absent where? Instead of what? And most concretely: what does someone on the content team open a doc and write?

This post is about the pipeline we built to answer that, how measuring the gap by keyword cluster evolved into measuring it by citation once we ran it against real production data, and why that sharper unit holds up against what the wider GEO/AEO research community has been publishing this year.

1. What a gap actually is

Before building anything, we had to settle one definition, because everything downstream inherits it.

A gap = a topic × provider where the brand has zero share of voice (no mentions, no citations) across that topic's discovery prompts, for that provider.

This comes directly from our presence tracking: whether the brand was recorded as present or absent, for every prompt, entity, and provider, on every run. It's discovery-only by design: sentiment prompts measure how we're talked about, not whether we occupy the territory at all, and mixing the two lets a sentiment-only run zero out a real absence streak.

The important design decision is what everything else (citations, keywords, content) is allowed to be: evidence that explains a gap, not a gap of its own. We do not maintain a separate "citation gap count" and a separate "keyword gap count" that both need their own trend line. We validated this isn't just tidiness. On one project's run, of 140 discovery prompt×provider pairs, 135 were absent, 5 were mentioned-and-cited, and the part that mattered: zero were mentioned-but-not-cited. Citation absence was fully entailed by prompt absence. A separate citation-gap tier would have tracked the exact same curve under a different name.

That single run raises an obvious question: was the zero a fluke of one project's one run? To check, we repeated the same count across five independent random samples of five live projects each. Mentioned-but-not-cited pairs turned up in four of the five samples, at rates that varied a lot, from none in one sample to close to a third of that sample's "mentioned" pairs in another. Small samples are noisy by nature, that variance is expected, but the state itself is not a fluke: it's real, it recurs, and it's visible to the model but unsourced, which makes it the one gap state that deserves separate treatment rather than folding into the general absence count.

2. Finding the right unit to measure a gap by

The first version measured a gap at the keyword-cluster level: run the citations from a brand-absent prompt through Google Ads' site-seed keyword expansion, cluster the resulting keywords, and turn each cluster into a card: "you're missing these 40 keywords your competitors cover." It was a reasonable starting hypothesis and we built it end to end: a three-stage job pipeline, persistent storage for the resulting clusters, and a drill-down UI from cluster → citations → prompts.

Running it against real production data is what surfaced a sharper, more actionable unit hiding underneath the cluster:

What all four rows point to is the same underlying unit: the citation, not the cluster, is what's actionable. A cluster spans multiple pages with genuinely different actions attached to them. And a cluster's identity depends on LLM output, which drifts by construction, so it can't anchor a stable row in a register users check week over week.

3. The sharper version: citation-first, register-first

This version keeps the one gap definition from section 1, and restructures everything under it around the citation as the unit of evidence and action.

<g transform="translate(1240 73)"> <rect width="278" height="40" rx="20" fill="#0d2638" stroke="#28506a"/> <circle cx="22" cy="20" r="5" fill="#70dfec" filter="url(#softGlow)"/> <text x="39" y="25" class="micro cyan">DETERMINISTIC EVERY-RUN PATH</text> </g> <!-- Input --> <g transform="translate(80 276)" filter="url(#shadow)"> <rect width="232" height="210" rx="18" fill="#0d1c2d" stroke="#2c4864" stroke-width="1.5"/> <rect x="18" y="18" width="52" height="28" rx="8" fill="#152e46"/> <text x="33" y="37" class="micro cyan">INPUT</text> <g transform="translate(22 69)"> <circle cx="15" cy="15" r="13" fill="none" stroke="#68d3e2" stroke-width="2"/> <path d="M15 6V16L22 20" fill="none" stroke="#68d3e2" stroke-width="2" stroke-linecap="round"/> </g> <text x="22" y="126" class="nodeTitle white">Prompt visibility</text> <text x="22" y="153" class="nodeBody muted">topic × provider</text> <text x="22" y="179" class="nodeBody coral">is_present = 0</text> </g> <!-- Gap register --> <g transform="translate(372 276)" filter="url(#shadow)"> <rect width="254" height="210" rx="18" fill="#0e2033" stroke="#35617b" stroke-width="1.5"/> <rect x="18" y="18" width="82" height="28" rx="8" fill="#16334b"/> <text x="32" y="37" class="micro cyan">REGISTER</text> <g transform="translate(22 69)"> <rect width="30" height="30" rx="6" fill="none" stroke="#68d3e2" stroke-width="2"/> <path d="M8 9H22M8 15H22M8 21H17" stroke="#68d3e2" stroke-width="2" stroke-linecap="round"/> </g> <text x="22" y="126" class="nodeTitle white">One stable gap row</text> <text x="22" y="153" class="nodeBody muted">(project, topic, provider)</text> <g transform="translate(22 171)"> <rect width="55" height="23" rx="11.5" fill="#17394a"/> <text x="14" y="16" class="micro cyan">NEW</text> <rect x="65" width="94" height="23" rx="11.5" fill="#2e2a32"/> <text x="77" y="16" class="micro coral">RECURRING</text> </g> </g> <!-- Diagnosis group --> <g transform="translate(692 212)"> <rect width="456" height="528" rx="24" fill="#0a1727" stroke="#2d4e69" stroke-width="1.5" filter="url(#shadow)"/> <text x="26" y="40" class="eyebrow muted">CITATION-FIRST DIAGNOSIS</text> <g transform="translate(24 66)"> <rect width="408" height="88" rx="14" fill="#0f2134" stroke="#2d4963"/> <circle cx="34" cy="32" r="18" fill="#142f46"/> <text x="26" y="38" class="nodeBody cyan" font-weight="700">01</text> <text x="64" y="30" class="nodeTitle white">Prompts affected</text> <text x="64" y="56" class="nodeBody muted">The absent evidence chain</text> <path d="M335 44H378" stroke="#56738f" stroke-width="2" stroke-linecap="round"/> <circle cx="342" cy="44" r="4" fill="#6886a2"/> <circle cx="358" cy="44" r="4" fill="#6886a2"/> <circle cx="374" cy="44" r="4" fill="#6886a2"/> </g> <path d="M228 154V170" stroke="#65d5e8" stroke-width="2"/> <g transform="translate(24 170)" filter="url(#softGlow)"> <rect width="408" height="100" rx="14" fill="url(#citationGlow)" stroke="#68dbea" stroke-width="2"/> <circle cx="34" cy="36" r="18" fill="#15516a"/> <text x="26" y="42" class="nodeBody white" font-weight="700">02</text> <text x="64" y="33" class="nodeTitle white">Citation evidence</text> <text x="64" y="60" class="nodeBody cyan">Atomic unit of diagnosis and action</text> <g transform="translate(337 27)"> <path d="M15 10l6-6a9 9 0 0113 13l-8 8a9 9 0 01-13 0" fill="none" stroke="#8aebf5" stroke-width="3" stroke-linecap="round"/> <path d="M25 30l-6 6A9 9 0 016 23l8-8a9 9 0 0113 0" fill="none" stroke="#8aebf5" stroke-width="3" stroke-linecap="round"/> </g> <text x="64" y="82" class="micro muted">DOMAIN CLASS · PAGE TYPE · URL</text> </g> <path d="M228 270V286" stroke="#65d5e8" stroke-width="2"/> <g transform="translate(24 286)"> <rect width="408" height="88" rx="14" fill="#0f2134" stroke="#2d4963"/> <circle cx="34" cy="32" r="18" fill="#142f46"/> <text x="26" y="38" class="nodeBody cyan" font-weight="700">03</text> <text x="64" y="30" class="nodeTitle white">Recurring keyword pattern</text> <text x="64" y="56" class="nodeBody muted">Ranked by distinct-domain spread</text> <g transform="translate(331 23)"> <rect width="54" height="8" rx="4" fill="#294b65"/> <rect y="17" width="38" height="8" rx="4" fill="#3f7089"/> <rect y="34" width="47" height="8" rx="4" fill="#68dbea"/> </g> </g> <path d="M228 374V390" stroke="#65d5e8" stroke-width="2"/> <g transform="translate(24 390)"> <rect width="408" height="88" rx="14" fill="#111f31" stroke="#ff9a83" stroke-width="1.5"/> <circle cx="34" cy="32" r="18" fill="#47303a"/> <text x="26" y="38" class="nodeBody coral" font-weight="700">04</text> <text x="64" y="30" class="nodeTitle white">Deterministic rules engine</text> <text x="64" y="56" class="nodeBody muted">Evidence + own-page coverage → action</text> <g transform="translate(340 20)"> <path d="M22 0V12M22 34V46M0 23H12M34 23H46" stroke="#ffad99" stroke-width="3" stroke-linecap="round"/> <circle cx="23" cy="23" r="10" fill="none" stroke="#ffad99" stroke-width="3"/> </g> </g> </g> <!-- Connections --> <path d="M312 381H372" class="line"/> <path d="M626 381H662Q676 381 676 395V453Q676 468 692 468" class="line"/> <!-- Outputs --> <g transform="translate(1214 226)"> <text x="0" y="14" class="eyebrow muted">EXPLAINABLE ACTION</text> <g transform="translate(0 42)"> <rect width="306" height="82" rx="15" fill="#0f2235" stroke="#3f647e"/> <circle cx="32" cy="41" r="17" fill="#173b4e"/> <path d="M24 42l6 6 11-15" fill="none" stroke="#75e0ec" stroke-width="3" stroke-linecap="round" stroke-linejoin="round"/> <text x="61" y="37" class="nodeTitle white">Strengthen page</text> <text x="61" y="59" class="nodeBody muted">Named URL + keyword diff</text> </g> <g transform="translate(0 140)"> <rect width="306" height="82" rx="15" fill="#0f2235" stroke="#3f647e"/> <circle cx="32" cy="41" r="17" fill="#173b4e"/> <path d="M25 50V31h14v19M22 50h20M28 36h8M28 41h8" fill="none" stroke="#75e0ec" stroke-width="2.4" stroke-linecap="round"/> <text x="61" y="37" class="nodeTitle white">Create new blog</text> <text x="61" y="59" class="nodeBody muted">Prompt + target vocabulary</text> </g> <g transform="translate(0 238)"> <rect width="306" height="82" rx="15" fill="#0f2235" stroke="#3f647e"/> <circle cx="32" cy="41" r="17" fill="#173b4e"/> <path d="M23 43h18M27 35h10M27 51h10" fill="none" stroke="#75e0ec" stroke-width="2.5" stroke-linecap="round"/> <text x="61" y="37" class="nodeTitle white">Get listed</text> <text x="61" y="59" class="nodeBody muted">Directory · review · marketplace</text> </g> <g transform="translate(0 336)"> <rect width="306" height="94" rx="15" fill="#171f2d" stroke="#9c6f67"/> <circle cx="32" cy="47" r="17" fill="#3a2931"/> <path d="M24 47h16M32 39v16" stroke="#ff9a83" stroke-width="2.7" stroke-linecap="round"/> <text x="61" y="37" class="nodeTitle white">Not a content gap</text> <text x="61" y="60" class="nodeBody muted">Authority · retrieval · freshness</text> </g> </g> <path d="M1148 646H1178Q1192 646 1192 632V309Q1192 294 1214 294" class="line"/> <path d="M1192 392H1214" class="lineMuted"/> <path d="M1192 490H1214" class="lineMuted"/> <path d="M1192 594H1214" class="lineMuted"/> <!-- Data persistence --> <g transform="translate(80 790)"> <rect width="1068" height="54" rx="14" fill="#0a1725" stroke="#2a435c"/> <text x="22" y="23" class="micro muted">PERSISTED EVIDENCE</text> <text x="22" y="42" class="nodeBody white">prompt_visibility_metrics</text> <path d="M238 27H300" class="lineMuted dash"/> <text x="320" y="34" class="nodeBody white">gap register</text> <path d="M425 27H487" class="lineMuted dash"/> <text x="507" y="34" class="nodeBody white">citation classification</text> <path d="M680 27H742" class="lineMuted dash"/> <text x="762" y="34" class="nodeBody white">accumulating keyword evidence</text> </g> <!-- Agentic layer --> <g transform="translate(1214 790)"> <rect width="306" height="54" rx="14" fill="#111827" stroke="#52647a" stroke-dasharray="6 6"/> <text x="20" y="23" class="micro muted">ON-DEMAND · CREDIT-GATED</text> <text x="20" y="42" class="nodeBody white">Agentic deep-dive</text> </g>

The gap register is the main surface: one row per open topic × provider gap, with a sparkline of that gap's absent-rate across runs and a status badge: new (first seen this period) or recurring (seen across multiple runs). Because the identity contains no LLM output, rows are stable by construction; a gap doesn't silently reshuffle into a different row because a labeling pass ran differently this week.

Clicking a gap opens a diagnosis panel with four layers, in causal order, not presentation order: each layer's data justifies the next:

1. Prompts affected: the topic's absent prompts × providers, with the actual prompt text and topic name threaded through.
2. Who's cited instead: per cited URL: a competitor-by-domain flag (not "was a competitor mentioned on this page", see the table above), page type (product/service · blog · homepage · directory/third-party), and how many times it was cited.
3. What to target: the deduped keyword intersection across those citations (more on this below).
4. Recommended action: output of a deterministic engine, described in section 5.

The trend strip above the register is deliberately simple: total open gaps per week, computed raw from whatever was measured that week: no carry-forward, no debounce. A missed provider run reads as a close-then-reopen. That's an accepted trade, not an oversight, because runs are admin-scheduled and normally complete; the raw per-run data is retained, so a debounce layer can be added later without touching what's already stored. "Closed / new" chips are a set-diff of topic × provider pairs between the two most recent measurement periods, at topic grain rather than individual-prompt grain, because topics are user-curated and stable while the underlying prompts churn on regeneration; churn in the chips has to mean an AI-visibility change, not a topic-list edit.

4. From citations to keywords: finding the pattern that recurs

Once a gap's citations are typed and classified, the question becomes: what, specifically, does the content that's winning here talk about that ours doesn't?

The naive approach (union every keyword from every citation) reproduces the same undifferentiated-bag problem the cluster-first version had, just at a smaller scale: a big pile of terms with no signal about which ones actually matter. The fix is a recurrence signal, not a size signal:

A keyword's importance = the number of distinct cited domains it spans, not how many times it was sighted.

Raw sighting counts just restate that a citation recurred; distinct-domain spread tells you the keyword is load-bearing across multiple competitors' winning pages, not an artifact of one page using it five times. Before that computation runs, a variant-dedupe pass collapses close phrasings (the fix for the 39% volume inflation in section 2) using the same fuzzy-signature primitives as our keyword-pool pipeline.

The results accumulate rather than get replaced on every run: each keyword is tracked per project and region, with when it was first seen, when it was last seen, and how many times it's recurred. A keyword that shows up again in next month's run isn't a new entry; it's the same one aging, which is what makes "this gap keyword has persisted for three runs" a meaningful, queryable fact instead of something you'd have to reconstruct from job logs. Presentation-level grouping still runs Leiden community detection over the accumulated keyword set, and we've written before about why graph-based community detection beats threshold clustering here, but the label is explicitly presentation, never identity. Nothing downstream keys off a cluster label anymore.

There's one more state worth calling out separately: present-but-invisible. If a keyword already sits in our own site-seed pool but the topic it belongs to is still absent, that's not "we have no content"; it's "we have content the model isn't surfacing." Same gap register entry, different action class: this is an authority/retrievability problem (schema, cross-references, freshness), not a content-creation problem, and treating it as "go write a blog" would be actively wrong advice.

5. The recommendation engine: rules, not agents, for the every-run tier

The action attached to each gap comes from a deterministic classifier (an explicit table, not an LLM call) because the always-on tier needs to be stable across runs, explainable to a customer who asks "why did it say this," unit-testable, and free to run on every project every week.

Own-page matching runs superset → subset: shortlist our own pages by keyword overlap against title and description (a cheap DB query), gate by page type so a blog can't masquerade as a product page, then test whether the shortlisted page's own keyword footprint actually covers the gap keywords. Low confidence anywhere in that chain degrades to "create," never to naming a page we're not sure about; a wrong page reference is worse than a generic recommendation.

The agentic version (reading the competitor's actual page, working out why it specifically got cited, drafting the outreach) is a deliberately separate, later, credit-gated layer that runs on demand per gap rather than inside the analysis job. If the agents stack has a bad day, one request degrades, not the whole run. The bar for shipping this deterministic tier first: it has to be genuinely useful on its own, or the credit gate for the deep-dive reads as a paywall on basic functionality.

6. What the prompt gives you that the keyword can't

It's worth being explicit about the division of labor between layers 1 and 3 of the diagnosis panel, because it maps directly onto how a content brief actually gets written.

The keyword layer tells you what terms need to appear: the vocabulary a page has to use to be a plausible retrieval candidate. The prompt layer tells you what question the content has to actually answer, in the customer's own phrasing, because that's literally the text that was sent to the model and came back without the brand in it. A content brief built from keywords alone reads like a term list. A content brief built from the absent prompt reads like a question the piece is obligated to resolve, closer to how a person actually asked.

7. Checking this against what the rest of the field is finding

We built this from our own telemetry, but a design like this earns more confidence when independent research lands on adjacent conclusions for different reasons. A few 2026 findings line up closely enough with our design decisions that they're worth citing directly.

None of this tells us our specific numbers are right; that still comes from our own project data. What it tells us is that the shape of the problem (provider fragmentation, run-over-run volatility, earned-media dominance, citation sources diverging from organic rank, evidence-density mattering more than keyword density) is not something we're seeing because our sample is small. It's the ambient behavior of the ecosystem, and a gap-analysis system that ignores any one of those five facts will eventually produce a recommendation that doesn't survive contact with a real project.

8. Build order

Each phase ships independently useful, in this order:

1. Register + trend: definite data only, no LLM anywhere: register rows and sparklines straight from the presence data we already collect, the trend line with closed/new chips, and moving the section to the top level out from under Citations.
2. Diagnosis layers: competitor-by-domain classification, per-URL page typing, the accumulating keyword table with the recurrence signal, and inverting the drill order to citation-first.
3. Recommendation engine: the deterministic action matrix from section 5, own-page superset→subset matching, and the present-but-invisible card.
4. Agentic deep-dive: credit-gated, off the analysis run path, for the depth a rules engine structurally can't reach.

Phase 1 alone answers "are we improving?" with zero new tables. Phase 4 is the only phase that touches an LLM in the run-critical path at all; everything a customer sees by default is a deterministic function of measured data.

Closing

"Analysis to action" is not a bigger dashboard; it's a shorter, more literal path between "you're invisible here" and "here is the exact page to strengthen, the exact keywords it's missing, and the exact question it has to answer." The first version of that pipeline got the destination right from day one: turn absence into a recommendation. What running it against real data sharpened was the unit of work itself: a keyword cluster spans citations that want different, sometimes contradictory, actions, so the unit moved down to the citation. The version we're building now treats the citation as the atomic unit of evidence, keeps keywords as the "what to target" detail inside it, and keeps the prompt text itself as the closest thing we have to a content brief a customer didn't have to write themselves.

Further Reading

Every source below is linked to its own first-party page (company blog, official wire release, or peer-reviewed paper), not to an aggregator repeating someone else's number. One stat from an earlier draft, a "ConvertMate GEO Benchmark," was dropped after its domain failed to resolve at all; it appears to be a figure laundered across SEO content-mill sites with no verifiable primary source, and is replaced below with BrightEdge's directly-verified equivalent.

• AI Platform Citation Patterns: How ChatGPT, Google AI Overviews, and Perplexity Source Information - Profound, 2026. First-party breakdown of each platform's top-10 cited sources; the basis for keeping provider as a first-class dimension in the gap key.
• The 2026 State of AI Search - AirOps × Kevin Indig, 2026. Reports ~30% run-over-run and ~20% five-run brand visibility consistency, the baseline volatility our no-debounce, recurring-status design is built around.
• Earned media still drives 84% of AI citations - Muck Rack, 2025-2026. Analysis of 1M+ AI-cited links.
• Earned Media Still Drives Generative AI Citations as Press Release Visibility Grows - Muck Rack, official wire release, Dec 2025. Source of the 2% overlap between PR-pitched journalists and AI-cited sources.
• AI Overviews at the One-Year Mark: Presence, Size, and What They're Citing - BrightEdge, Feb 2026. Twelve months of daily tracking across nine industries; source of the ~17% organic-top-10 overlap figure.
• GEO: Generative Engine Optimization - Aggarwal et al., Princeton/Georgia Tech/Allen Institute for AI, KDD 2024 (peer-reviewed). The GEO-bench study behind the statistics/citations/quotations lift figures and the keyword-density finding.
• Do AI assistants prefer to cite fresh content? - Ahrefs, 2026. Analysis of 17M AI citations across seven platforms; source of the 25.7% freshness gap.

Footnotes

1. https://www.tryprofound.com/blog/ai-platform-citation-patterns "AI Platform Citation Patterns (Profound)" ↩

2. https://www.airops.com/report/the-2026-state-of-ai-search "The 2026 State of AI Search (AirOps × Kevin Indig)" ↩

3. https://muckrack.com/blog/what-is-ai-reading-may-2026 "Earned media still drives 84% of AI citations (Muck Rack)" ↩

4. https://www.globenewswire.com/news-release/2025/12/2/3198248/0/en/earned-media-still-drives-generative-ai-citations-as-press-release-visibility-grows.html "Muck Rack official wire release, Dec 2025" ↩

5. https://www.brightedge.com/resources/weekly-ai-search-insights/ai-overviews-one-year-presence-size-citing "AI Overviews at the One-Year Mark (BrightEdge)" ↩

6. https://arxiv.org/abs/2311.09735 "GEO: Generative Engine Optimization (Aggarwal et al.)" ↩

7. https://ahrefs.com/blog/do-ai-assistants-prefer-to-cite-fresh-content "Do AI assistants prefer to cite fresh content? (Ahrefs)" ↩