Prompt gap analysis: map buyer questions to pages

By Abiot Y. Derbie - Founder, RankEcho - Updated 2026-09-07

What is the scope of prompt gap analysis?

The unit is a registered buyer question and user job, its required answer facets, and an owned-page mapping. The analysis asks whether one intended canonical page visibly provides the required information; it does not infer a gap from a provider response or a sitewide score.

Keep the original prompt, any provider-derived search, and the observed answer separate. Query fan-out, query rewriting, sampled grounding phrases, keyword estimates, and traffic each describe different objects and do not establish a content-coverage defect.

Which prompt inputs must be frozen first?

Register the panel and rubric before inspecting pages so convenient wording cannot redefine the gap.

The linked prompt portfolio template registers prompt identity and scope, but it does not carry page-and-facet mappings, content locators, page versions, facet rationales, or evidence pointers. Attach a companion mapping record keyed by prompt ID before classifying coverage.

• Prompt ID, verbatim prompt, source and collection date, audience, buyer stage, locale or language, inclusion reason, and exclusion rule.
• Required answer facets with a source or product rationale for each one.
• Candidate canonical URL, visible page locator, ownership decision, saved page version, and evidence pointer.
• Generated prompt ideas may enter as candidates only; they are not measured demand or observed gaps.
• No prompt count, aggregate coverage threshold, or page-per-query rule is universal.

What must the companion prompt mapping record contain?

Keep the template's prompt ID as the join key. For every required facet, retain the registration source, inclusion rationale, evidence pointer, before and after visible locators, intended canonical path, page version, and canonical-resolution evidence.

The table below is the synthetic companion mapping for G01–G04. Its synthetic-evidence strings are artifact identifiers, not live URLs or external proof.

How are prompts mapped to canonical pages?

Inspect rendered visible content rather than infer coverage from a title, schema object, or URL. Record the exact heading, table, or paragraph locator for each supported facet, follow redirects, and confirm the intended canonical owner.

Count a facet once even when the same wording repeats. When several pages claim the same user job, retain duplicate ownership as its own state rather than treating repetition as stronger coverage.

Which coverage states must stay separate?

Assign one state from the frozen page-and-facet evidence. Excluded or invalid prompts remain outside any aggregate.

What does the worked synthetic prompt matrix show?

SYNTHETIC EXAMPLE — Northstar S1, its pages, sources, surfaces, and observations are fictional; this is not RankEcho data, customer data, provider evidence, or a benchmark.

The four registered prompts produce one covered, one partial, one duplicate, and one missing row. Five of seven required facets are visibly supported before the fix: 5/7 = 71.4%. That aggregate is descriptive, not importance-weighted and not a RankEcho product score.

How is one gap selected for Fix?

A fix handoff needs an existing target page, exact missing facet, support boundary, proposed semantic delta, acceptance test, competing explanations, and rollback. G02 qualifies because its canonical owner and standard interval are established while the material shock exception is missing.

G03 still needs a canonical-ownership decision and G04 still needs evidence and page-ownership work. Neither is silently folded into the G02 edit.

Which false positives and overlap risks should stop the diagnosis?

Stop when the claimed gap is only a generated prompt, provider rewrite, sampled grounding phrase, keyword estimate, missing answer, title mismatch, schema-only statement, or traffic trend. None demonstrates missing visible page coverage on its own.

The Prompt Gap Finder generates starter ideas; AI Citation Gap Analysis classifies target-owned source absence in observed answer cells; Prompt Intelligence describes the product capability. This guide owns the separate manual prompt-to-page-and-facet mapping.

Which deterministic validation checks complete Find?

Complete Find from the registered mapping and exact handoff. Do not wait for a citation, ranking, referral, impression, or traffic change.

How does prompt-gap analysis hand off to Prove?

Carry G02, both required facets, the exact target page, saved before version, source boundaries, and V01–V06 cell definitions into the bounded change and later repeat record.

The Find classification is complete before later observations exist. Site traffic is a separate outcome and is not required for the handoff or publication.

Who maintains this prompt-gap guide?

Written and maintained by Abiot Y. Derbie. Published 2026-09-07; sources checked 2026-09-07; last updated 2026-09-07. The worked records are synthetic.

Recheck provider descriptions, prompt provenance, canonical mappings, and visible-content locators before applying the method. Send material corrections through the contact page.

Sources reviewed

Provider eligibility and measurement claims below were checked against primary documentation. These records do not establish a universal selection formula, causation, or a guaranteed ranking, impression, recommendation, or citation.

Frequently asked questions