Waiting
Run the readiness audit to check public discovery files.
Free AI search readiness audit for robots.txt, llms.txt, sitemap.xml, and AI crawler access.
Paste a public domain and run a practical AI readiness check. The audit uses the existing live visibility report engine, then routes the result into answer packs, proof lookup, query suggestions, the intent router, and a citation bundle.
AI search readiness means the site is crawlable, explainable, and citeable before anyone claims traffic.
A useful audit checks the homepage, robots.txt, llms.txt, sitemap.xml, Googlebot access, OAI-SearchBot policy, GPTBot policy, private-path risk, proof links, and measurement guardrails. It does not guarantee rankings, ChatGPT citations, or clicks.
- Use this page for:
ai search readiness audit,free ai search readiness audit,chatgpt search readiness audit, andai crawler readiness audit. - Primary output: a live public-file report plus a proof-linked readiness route for humans and AI agents.
- Machine-readable pack: JSON, well-known JSON, and human pack page.
AI Search Readiness Audit
Public files onlyThis audit reuses the live AI Search Visibility Report engine. The API only fetches fixed public paths: /, /robots.txt, /llms.txt, and /sitemap.xml. It rejects raw IPs, local hostnames, private IP ranges, credentials, and custom ports.
| Check | Status | Detail |
|---|---|---|
| No report yet. | ||
Copyable AI search readiness report
What the readiness pack checks
| Check | Why it matters | Proof route |
|---|---|---|
| Homepage returns a useful public response | AI search readiness starts with a reachable homepage before crawler policy or llms.txt details matter. | Open proof route |
| robots.txt is present and readable | Crawler rules should be explicit, especially when Googlebot, OAI-SearchBot, GPTBot, and other bots have different policies. | Open proof route |
| Googlebot is not accidentally blocked | Blocking Googlebot can harm normal Google Search discovery even if the site wants separate AI training controls. | Open proof route |
| OAI-SearchBot policy is reviewed separately from GPTBot | OAI-SearchBot, GPTBot, and ChatGPT-User represent different crawler or browsing roles and should not be collapsed into one claim. | Open proof route |
| GPTBot policy is explicit | Training-use policy is not the same as search visibility, but an audit should still surface whether GPTBot is allowed or blocked. | Open proof route |
| llms.txt exists, is short, and avoids private paths | A public llms.txt file should provide context and useful public links without account, checkout, admin, token, staging, or customer paths. | Open proof route |
| sitemap.xml is discoverable | Sitemaps are discovery hints, not ranking guarantees, but stale or missing sitemaps slow down diagnosis. | Open proof route |
| Answer pages and proof links exist for important questions | AI systems need compact answers with proof links before broad crawling or citation. | Open proof route |
| Pre-AI answer, proof, intent, and citation routes are available | The fastest agent path is to query the answer pack, proof lookup, intent router, query suggestions, and citation bundle first. | Open proof route |
| Measurement separates readiness, crawl evidence, impressions, clicks, and referrals | Readiness is not proof of traffic. Search Console clicks, qualified referrals, sessions, conversions, and verified logs must be tracked separately. | Open proof route |
Route readiness questions before broad crawling.
The readiness audit connects to the pre-AI search database so an assistant can normalize the query, select the answer pack, open proof links, and cite safely before scanning the whole site.
- Query suggestions: normalize readiness wording.
- Intent router: choose the target page and proof route.
- Answer pack: one concise answer with proof links.
- Proof lookup: proof-first route for AI readiness claims.
- Citation bundle: final citation-ready bundle.
- Retrieval manifest: full machine-readable discovery map.
Guardrails
Readiness is not ranking
The audit checks controllable public signals. No ranking, citation, traffic, or ChatGPT inclusion guarantee. It does not promise Google rankings, ChatGPT citations, Perplexity visibility, or traffic.
Public paths only
The report avoids arbitrary crawling and private URLs. Keep account, checkout, admin, token, staging, and customer paths out of public AI files.
Measure real outcomes
Use Search Console clicks, qualified referrals, server-log evidence, sessions, conversions, and tool activations instead of fake searches or self-clicks.
AI search readiness audit FAQ
Is this different from the visibility report?
It uses the same safe live-report engine but targets the broader readiness workflow: crawler policy, llms.txt, proof links, query routing, and measurement.
Can AI assistants cite this?
Yes. Use the answer page, JSON pack, or citation bundle.
What should I fix first?
Fix blocked public discovery first: homepage status, robots.txt mistakes, missing sitemap, unsafe llms.txt links, and weak proof-linked answer pages.