Can ChatGPT see your site?
See what AI crawlers and agents actually get: robots.txt rules for GPTBot, ClaudeBot and seven more, llms.txt, structured data, MCP, and pages that need JavaScript. 13 checks, graded A–F.
Every major AI crawler is blocked — the site is invisible to AI answers and agents.
~10 words visible without JavaScript. The page is effectively blank to non-rendering agents (most of them).
Automated clients get HTTP 403 — AI agents are being turned away at the door.
No valid JSON-LD found on the homepage. AI systems have to guess what your site is about.
Declared in robots.txt.
No feed advertised or found at /feed or /rss.xml. Feeds are the cheapest machine-readable channel you can offer.
Not found. llms.txt tells AI models which of your pages matter and how to describe you.
Requests with Accept: text/markdown still get HTML. Serving Markdown saves agents ~10× the tokens.
No OpenAPI spec at /openapi.json or /openapi.yaml.
No MCP manifest (/.well-known/mcp.json, /.well-known/mcp/server-card.json) or live /mcp endpoint. MCP is how AI assistants plug into services directly.
No /.well-known/ai-plugin.json manifest.
Not found at /agents.txt or /.well-known/agents.txt — an emerging convention for telling AI agents how to interact with your site.
No x402 support (HTTP-native payments for agents). Cutting-edge — very few sites have this.
Which AI systems your robots.txt lets in — blocked bots can’t read or cite your content.
The other half
Now check nytimes.com’s security grade.
SSL/TLS, security headers, DNSSEC, DMARC and more — the same A–F grading, free.