A citation scenario map is a working brief that connects one buyer question with a truthful claim, the evidence needed to support it, one canonical page, and a next action. It is a planning document for source-page work. It does not guarantee citation, ranking, traffic, or placement in ChatGPT, Google or Bing.
Scenario table
Use one row per question. Keep examples generic. Do not attach a named competitor or a client result you cannot show.
| Question | Claim to support | Evidence needed | Best source page | Next action |
|---|---|---|---|---|
| How does this service start? | Work starts only after a written action plan names the pages and questions in scope. | A dated proposal or onboarding note the client has approved. | The public service page that describes the starting process. | Add the start condition to visible HTML and keep schema aligned with that text. |
| When is a rebuild unnecessary? | An existing public URL can answer the question if the claim and evidence already belong there. | The current page HTML plus the evidence that supports the claim. | The strongest existing canonical page, not a new thin URL. | Improve that page instead of publishing a duplicate. |
| What proof exists today? | Only completed, client-approved checks or primary sources may be stated as fact. | First-party records or a reputable primary source the client can stand behind. | A proof or method page that already lists those checks. | Publish the evidence that exists and mark remaining gaps as gaps. |
| What should a buyer decide next? | The next step is a conversation about agreed scope, not a promised platform outcome. | The public offer, exclusions, and contact path already on the site. | The buying or contact page that states scope and next action. | Keep the decision page crawlable and internally linked from the source page. |
The Evidence-First Citation Method
The same seven steps used on the AI Citation Optimisation service page apply here, in more operational detail.
- Choose the buyer questions worth owning. Prefer questions a public page can answer with evidence you already have or can obtain with approval. Discard queries that require an untrue claim.
- Map each question to a precise, truthful claim. Write the claim in the same words you are willing to publish. If the claim needs a hedge, keep the hedge.
- Collect approved evidence. Use client-approved first-party proof or a reputable primary source. Do not invent statistics, reviews, or competitor statements.
- Build or improve one public page. One question should resolve to one canonical URL. Related WordPress and headless checks are on WordPress AEO eligibility and headless WordPress release evidence.
- Correct crawl and index eligibility. Confirm a public 200 response, one canonical, sitemap listing, and internal links from relevant pages such as AEO, Show up in ChatGPT, AI Search Optimization 2026, Trust and Contact. Eligibility is not an indexing guarantee.
- Apply structured data only for visible matching facts. Schema may repeat the service name, FAQs or breadcrumbs a person can already read. Do not invent special AI markup.
- Deliver a manual Citation Evidence Report. Record the agreed scenarios, completed work, dated observations where available, remaining gaps, and the next priorities. The report is not a dashboard or a citation count.
What a scenario map cannot do
A complete map does not guarantee citation, ranking, traffic, leads, revenue, Google AI Overview inclusion, or ChatGPT placement. Platforms choose sources. The map only makes the intended page clearer, eligible, and internally consistent. It cannot force a crawler to select that page. Public examples of finished delivery sit in the portfolio.
Sources
Record
Author and reviewer: The Dot Dev. First published 23 August 2026. Review when the cited publisher guidance changes.
