AI-visibility audit — sample report
1 · The five signals
GPTBot and PerplexityBot receive HTTP 403 from the WAF while Googlebot passes — the site is invisible to major answer engines at the fetch layer.
No AI crawler is disallowed; robots.txt is consistent with the WAF intent but not with its behavior (see above).
Article schema present on 12 of 34 key pages; no Organization @id graph, so entity signals don't consolidate.
3 of 10 money pages open with an extractable 40–60-word answer; the rest bury the answer below the fold.
No llms.txt; competitors A and B both serve curated files with described links.
2 · Prompt-sampling log (excerpt — 3 of 8 prompts)
| Prompt | Named by | Note |
|---|---|---|
| best {category} software for smb | Perplexity ✗ · GPT-4o ✗ · Gemini ✓ | Named only by Gemini, position 4 of 6 |
| {brand} vs {competitor} | Perplexity ✓ · GPT-4o ✓ · Gemini ✓ | Cited via third-party review, not own site |
| is {category} worth it | Perplexity ✗ · GPT-4o ✗ · Gemini ✗ | Zero visibility — competitor C owns this set |
The full report logs all 24 answers with dates, positions, and which competitor took each slot — that's the baseline your re-check is measured against.
3 · The roadmap, staged by impact
4 · This page exports like the real report
Every paid report ships in three formats. Try them on this demo right now:
You are an engineer working on the website demo-client.com. Below is an AI-visibility (GEO) audit — the signals that decide whether AI answer engines (ChatGPT, Perplexity, Google AI Overviews) can crawl, understand and cite this site. Implement the fixes. ## Audit findings ### Sitewide signals - [FAIL] Crawler reachability: GPTBot and PerplexityBot receive HTTP 403 from the WAF... - [WARN] Structured data: Article schema on 12 of 34 key pages; no Organization @id graph... - [FAIL] llms.txt: absent; competitors A and B both serve curated files... ## Implementation rules 1. Fix reachability FIRST — every other fix scores zero until crawlers get HTTP 200. 2. One Organization @id graph sitewide; connect Article.publisher to it. […continues with per-fix acceptance criteria — the full version ships with every report]
You are an engineer working on the website demo-client.com. Below is an
AI-visibility (GEO) audit — the signals that decide whether AI answer
engines (ChatGPT, Perplexity, Google AI Overviews) can crawl, understand
and cite this site. Implement the fixes.
## Audit findings
### Sitewide signals
- [FAIL] Crawler reachability: GPTBot and PerplexityBot receive HTTP 403 from the WAF...
- [WARN] Structured data: Article schema on 12 of 34 key pages; no Organization @id graph...
- [FAIL] llms.txt: absent; competitors A and B both serve curated files...
## Implementation rules
1. Fix reachability FIRST — every other fix scores zero until crawlers get HTTP 200.
2. One Organization @id graph sitewide; connect Article.publisher to it.
[…continues with per-fix acceptance criteria — the full version ships with every report]