GEO-014 · P0Checker · robots
Allow answer-engine crawlers on public docs
Why: GPTBot and OAI-SearchBot are blocked at root. Acceptance: re-crawl confirms no blocking directive.
Example diagnostic pack · Fictional workspace
From an AI answer to an evidence-backed action plan.
This sample shows how CiteAura turns a public-site crawl and a labeled AI baseline into prioritized tickets, acceptance checks, and a client-ready delivery pack.
Example only: all domain names, prompts, rates, and ticket outcomes on this page are illustrative. A real workspace reports the sampled engines, sampling mode, raw answer replay, and evidence coverage that were actually measured.
76Technical audit score · example
18%AI mention rate · 24 labeled answers
4High-impact tickets created
3/4Acceptance checks passed
1. Evidence scope
The report keeps technical diagnosis separate from visibility measurement, so a customer can see what was checked and what remains unmeasured.
| Evidence | Result | Sampling / source label | Recommended next step |
|---|---|---|---|
| Public pages | 18 eligible pages | Manual · product surface crawl | Use page-level findings to scope tickets. |
| AI answers | 18% mention rate | API · web-grounded retrieval | Review raw answers and citation gaps before changing copy. |
| Machine files | llms.txt missing | Manual · public file check | Generate and review a machine-readable asset. |
| Competitor prompts | 2 takeover gaps | API · parametric knowledge | Confirm competitor facts, then assign a playbook. |
2. Action tickets with acceptance gates
Every recommendation has an owner, an evidence link, and a checker that can reopen the ticket after a regression.
GEO-021 · P1Checker · JSON-LD
Expose canonical product facts
Why: the product page has no structured entity graph. Acceptance: JSON-LD parses and matches approved facts.
GEO-025 · P1Checker · llms.txt
Publish a reviewed machine-ingestion file
Why: no llms.txt was found. Acceptance: the file is reachable and linked from the delivery manifest.
GEO-031 · P2Checker · citation
Close the highest-value citation gap
Why: two target prompts cite third-party pages first. Acceptance: a comparable re-sample records the before/after delta.
3. Delivery and verification
The final pack contains an audit report, execution plan, ticket log, acceptance checklist, draft risks, and build map. The pack is marked diagnostic-ready until implementation evidence is complete.
| Milestone | Status | What the customer receives |
|---|---|---|
| Diagnostic ready | Complete | Scope, findings, provenance, and prioritized actions. |
| Visibility baseline | Limited | Comparable samples with explicit engine and mode labels. |
| Implementation ready | Review required | Generated assets remain human-reviewed until facts and content are approved. |
See this workflow on your own domain.
Start with a free technical diagnostic. Add model keys later for a full AI visibility baseline.