Free · no sign-up
Can AI assistants read your site at all?
llms.txt, AI-crawler access, structured data: what the bots actually see when they fetch your homepage. Thirty seconds. No account.
Six checks
Readiness is whether you can be cited.
We fetch your homepage, robots.txt and llms.txt once, as ourselves, and run the same six checks on every site. No LLM involved. Deterministic. Nothing stored.
Readiness tells you if you can be read; the Snapshot tells you whether you're actually cited. Run one — $121.
What each check means
| Check | Pass | Why it matters |
|---|---|---|
| AI-crawler access | robots.txt allows the answer-time crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User, Claude-User, Perplexity-User) | Blocked crawlers cannot fetch the page a citation would point to. Blocking training crawlers only (GPTBot, ClaudeBot, Google-Extended) is a legitimate choice and shows as a review item. |
| Homepage response | A 200 with text/html within a few seconds | Crawlers have short patience budgets. |
| Visible page content | 600+ characters of text in the HTML before JavaScript runs | Most AI crawlers do not execute JavaScript. A client-rendered app is an empty shell to them. |
| Structured data | JSON-LD naming who you are (Organization, LocalBusiness, SoftwareApplication…) | The cheapest way to state your identity unambiguously. |
| llms.txt | A plain-text /llms.txt | Optional. A concise one tells assistants what you do in your own words. |
| Indexing signals | A canonical link, no noindex | Citations point at one URL; noindex tells everything to stay away. |
Method details are on the methodology page.