Free instant scan
Can AI actually read your site?
ChatGPT, Perplexity and Google’s AI pick a handful of sources they can read and trust, and ignore the rest. This scan checks the machine-readability layer of your site in seconds, no signup, no tricks, every check shown.

What we check
- AI crawler access, does your robots.txt block GPTBot, ClaudeBot or PerplexityBot? (Many sites do without knowing.)
- AI index files, llms.txt and llms-full.txt, the machine-readable index AI crawlers ingest cheaply.
- Rendering & indexability, does your raw HTML contain readable content or an empty JavaScript shell? Is there a noindex directive quietly telling engines to forget you? Mobile viewport?
- Structured data & entity, JSON-LD presence, schema richness, and sameAs entity links so AI can connect your site to your real-world identity.
- Search hygiene & trust, title and description quality, self-referencing canonical, Open Graph, sitemap depth and freshness, language, HTTPS, speed, and identity pages (About/Contact).
We run the same layer we sell: our llms.txt · our robots.txt. Scan us if you like.
The evidence behind the rubric
rubric v5 · reviewed 31 Aug 2026Do you actually test whether AI crawlers get through?
Yes, and most checkers don’t. Reading robots.txt only shows the policy; the enforcement lives in the CDN or firewall, which can 403 a bot the robots file "allows" (Cloudflare began blocking AI crawlers by default for new sites on 1 July 2025). So this scan also fetches your page live, identifying as GPTBot and PerplexityBot, and reports what the network layer actually serves them. One honest caveat: if a site allowlists only verified bots by IP, the vendors’ real crawlers may pass where our test is walled: which is why a wall here is reported with that caveat, and why we tell you to confirm in your server logs.
Cloudflare: AI crawlers blocked by default ↗ · OpenAI: official crawler docs ↗
Why is server-side rendering weighted heaviest?
Most AI crawlers fetch your raw HTML and do not execute JavaScript, Vercel measured this across its edge network: OpenAI’s and Anthropic’s crawlers do not render JS. If your content only exists after JavaScript runs, ChatGPT, Claude and Perplexity see an empty shell, so rendering and indexability carry 27 of 100 points, the largest single block in our rubric. The measurement is not small: Vercel analysed over 500 million GPTBot fetches and found zero evidence of JavaScript execution. Google’s Gemini is the one exception, because it rides Googlebot’s rendering service.
Does Google use llms.txt?
No. Google’s own search documentation says: “You don’t need to create new machine readable files, AI text files, or markup to appear in these features”, and its Search team confirmed verbally (July 2025) that llms.txt is not used and not planned. Anthropic and Perplexity, by contrast, publish their own docs in the format. Ahrefs measured 137,210 domains in May 2026: 97% of llms.txt files received zero requests. That is why we score it just 4 of 100 points, worth shipping because it costs minutes and two major AI surfaces use the format, but never the headline mechanism some agencies sell it as. (We have cut this weight twice now as the evidence came in. The rubric moves when the evidence does, which is the whole reason we publish it.)
Google: AI features documentation ↗ · Ahrefs: 137K-domain study ↗
Why two files: what is llms-full.txt for?
They serve two different machines. llms.txt is a menu: a few kilobytes an AI agent fetches to decide which of your pages answers a question, before fetching just that page. llms-full.txt is the whole book: your entire content in one file, for tools that ingest everything upfront. AI coding assistants, retrieval pipelines, and assistants that load full context in a single request. Where these files get fetched at all, measured traffic shows llms-full.txt is fetched more, with ChatGPT the most frequent visitor. One caveat we verified ourselves (11 Jul 2026): Anthropic’s own llms-full.txt is 90.1 MB and Perplexity’s is 3.8 MB, far too large for any model to ingest in one shot. The file only helps if it fits, so the ones we build stay small enough to be swallowed whole.
Mintlify: llms.txt & llms-full.txt docs ↗ · Mintlify × Profound: measured bot traffic ↗ · Anthropic’s live llms-full.txt (90 MB) ↗ · Perplexity’s live llms-full.txt (3.8 MB) ↗
Why is structured data worth so little here when every SEO guide pushes it?
Because the best available evidence does not support scoring it high, and we would rather lose the upsell than tell you something we cannot back. Ahrefs tracked 1,885 pages that added JSON-LD against 4,000 matched controls: the differences for ChatGPT and Google AI Mode were within noise, and AI Overviews citations actually fell 4.6%. A separate controlled test found ChatGPT and Perplexity tokenize JSON-LD as raw text rather than parsing it as data, and that they ignore markup describing anything not visible on the page. Some studies do find a lift (AirOps measured 38.5% vs 32.0% citation rates across 16,851 ChatGPT queries), so it is not nothing. We landed on 14 of 100 points across four checks: worth having, never a substitute for the answer being visible in the HTML. We used to score this at 21.
Ahrefs: 1,885 pages added schema, citations barely moved ↗ · Google: FAQ rich results deprecated (May 2026) ↗
Which AI crawler should I actually be worried about blocking?
The search one, and the names do not make it obvious. Every vendor runs at least two bots: GPTBot, ClaudeBot and PerplexityBot gather training data, while OAI-SearchBot, Claude-SearchBot, ChatGPT-User and Perplexity-User build and serve the answers people actually read. Opting out of training is a defensible business decision plenty of firms make deliberately. Blocking the search bots is how a firm disappears from ChatGPT without ever deciding to, and it usually happens because one line in robots.txt was written to keep AI out and nobody separated the two jobs. This scan names any blocked search crawler separately for exactly that reason. Bingbot belongs in the same list, because Bing’s index feeds Microsoft Copilot.
Why do some scores get capped?
Two failures make everything else moot. A noindex directive tells every engine to forget the page exists, so the score caps at 25. Blocking five or more AI crawlers in robots.txt means the engines that answer your customers cannot read the site at all, so the score caps at 55 regardless of how polished the rest is.
Who actually reads llms.txt, platform by platform
- ignores itGoogle (Search, AI Overviews, AI Mode) , Google’s own docs: “You don’t need to create new machine readable files, AI text files, or markup to appear in these features.” Confirmed verbally by Search team (Jul 2025). their documentation ↗
- reads itAnthropic (Claude) , Publishes its own documentation in the format: the file is live on their docs domain right now. docs.anthropic.com/llms.txt ↗
- reads itPerplexity , Ships BOTH llms.txt and llms-full.txt on its own docs site, click it and read it. docs.perplexity.ai/llms-full.txt ↗
- unconfirmedOpenAI (ChatGPT search) , Their official crawler documentation (GPTBot, OAI-SearchBot, ChatGPT-User) makes no mention of llms.txt, no commitment either way. platform.openai.com/docs/bots ↗
- reads itAI agents & dev tools (Claude Code, Cursor, Copilot, MCP) , The clearest confirmed consumers: agents fetch it to navigate sites, per the spec’s stated inference-time purpose. llmstxt.org ↗
Primary sources: Google's AI features documentation · Google Search team statement (Jul 2025) · Ahrefs 137K-domain log study · Vercel AI-crawler rendering data · llms.txt spec.
The crawlers this scan checks come from the vendors' own documentation: OpenAI · Perplexity · Google · Apple · Microsoft Bing. Every weight in this rubric traces to evidence: the same standard we hold our clients' content to.