Top fixes
- Crawler access (+2 points): Add a group for ClaudeBot, PerplexityBot, Amazonbot and the others with "Allow: /" (or drop the blanket "Disallow: /") if you want answer engines to cite you. How to fix
- Readable without JavaScript (+2 points): Your edge serves a challenge or error to non-browser fetchers; allowlist the AI crawlers you want (at least for the home page) or serve them a static version. How to fix
- Machine-readable surfaces (+1 point): Publish /llms.txt (a short Markdown guide to your key pages); one agent surface: /openapi.json, /.well-known/agent-card.json, or /.well-known/x402 if you sell to agents. How to fix
Ordered by points recoverable. Each area: 2/2 pass, 1/2 warn, 0/2 fail.
washingtonpost.com is graded F. The $49 AI Visibility Full Report turns the 2 failing checks above (crawler access, machine-readable surfaces) into a prioritized, specific fix list for washingtonpost.com, and tests 8 real buyer questions across ChatGPT-class models to show what AI answers say about you today.
Get the full report — $49 Stripe checkout asks for your brand name and category; the report is ready about 60 seconds after payment. Legal notices and the MCP census entry are not in this report (free: Compliance Desk check, census claim).
Crawler access (robots.txt)
0/2 · fail
3 of 8 AI crawlers may read the site, 5 disallowed
- GET /robots.txt -> HTTP 200, 5.7 KB, 35 user-agent groups
- Allowed: GPTBot (via *) (113 path rules), OAI-SearchBot (via *) (113 path rules), Google-Extended (via *) (113 path rules)
- Disallowed: ClaudeBot, PerplexityBot, Amazonbot, CCBot, Bytespider
- Sitemap declared: https://www.washingtonpost.com/sitemaps/sitemap.xml.gz, https://www.washingtonpost.com/sitemaps/news-sitemap.xml.gz, https://www.washingtonpost.com/sitemaps/author-sitemap.xml.gz (+4)
Fix: Add a group for ClaudeBot, PerplexityBot, Amazonbot and the others with "Allow: /" (or drop the blanket "Disallow: /") if you want answer engines to cite you.
Machine-readable surfaces
1/2 · warn
None of the 7 machine-readable surfaces is published (a sitemap is declared in robots.txt)
- /llms.txt: HTTP 520
- /sitemap.xml: HTTP 520
- /.well-known/x402: HTTP 403
- /.well-known/agent-card.json: HTTP 403
- /.well-known/mcp-registry-auth: HTTP 403
- /openapi.json: HTTP 520
- /ai.txt: HTTP 520
- Sitemap declared in robots.txt instead: https://www.washingtonpost.com/sitemaps/sitemap.xml.gz
Fix: Publish /llms.txt (a short Markdown guide to your key pages); one agent surface: /openapi.json, /.well-known/agent-card.json, or /.well-known/x402 if you sell to agents.
Readable without JavaScript
0/2 · fail
Home page is not available to a plain fetch (HTTP 520)
- GET https://washingtonpost.com/ -> HTTP 520 after 1 redirect (final: https://www.washingtonpost.com/), text/plain, 16 B
Fix: Your edge serves a challenge or error to non-browser fetchers; allowlist the AI crawlers you want (at least for the home page) or serve them a static version.
Structured data
not measured
Home page returned HTTP 520; structured data not measurable
- GET https://washingtonpost.com/ -> HTTP 520, text/plain
Fix: Let non-browser fetchers reach the home page first.
Legal notices (TAKE IT DOWN desk check)
not measured
Unavailable
- takeitdown.agentexchange.work/check.json: refused takeitdown.agentexchange.work: hosts on agentexchange.work cannot be graded from inside the same Cloudflare zone; every check would - unavailable
Fix: Re-run in a few minutes; the notice check could not be completed.
MCP census entry (index.agentexchange.work)
1/2 · warn
Exposes /mcp but is not in the census
- census unavailable (refused index.agentexchange.work: hosts on agentexchange.work cannot be graded from inside the same Cloudflare zone; every check would time )
- GET /mcp -> HTTP 520 (text/plain): an endpoint answers
- Index MCP probe record: refused index.agentexchange.work: hosts on agentexchange.work cannot be graded from inside the same Cloudflare zone; every check would time
Fix: Publish /.well-known/x402 with your paid routes so payment indexers can list you.
$49 AI Visibility Full Report
This grade is free and automated. The paid next step is the $49 AI Visibility Full Report (which brands a representative AI model, standing in for ChatGPT-class assistants, names when buyers ask about your category, with a prioritized fix list) from aivisibility.agentexchange.work, run for washingtonpost.com. It includes:
- 8 real buyer questions tested across ChatGPT-class models
- Competitor share-of-voice: who AI names, how often, versus you
- Full GEO site audit with prioritized, specific fixes
- Agent-Readiness Score: crawler access, llms.txt, schema, discovery manifest
- Custom 30/60/90-day action plan to get cited by ChatGPT, Perplexity and Google AI Overviews
- Shareable report, generated in about 60 seconds after checkout
Get the Full Report — $49 Stripe checkout asks for your brand name and category; the report is ready about 60 seconds after payment. Legal notices and the MCP census entry are not in this report (free: Compliance Desk check, census claim).
