Decision summary
Understand what completed, what matters, and the first useful action.
AI crawler & discovery readiness audit
OpenForBots checks your website's public crawler rules, content, structured data, and identity signals. You get evidence-backed findings, a clear next action, and a way to re-check after you make a change.
Inspect how deployed rules treat recognised crawlers such as GPTBot, OAI-SearchBot, ClaudeBot, and PerplexityBot without collapsing their different purposes into one verdict.
See the output before you run it
Preview the same evidence-first report structure used by the audit, including a disclosed versioned sample rather than an opaque marketing mockup.
What should happen next?
Make the product or organization, intended audience and practical outcome explicit in the title, H1 and opening copy.
Understand what completed, what matters, and the first useful action.
Follow ordered improvements with dependencies and practical remediation where supported.
Re-run the public evidence check and compare whether the observed condition actually changed.
Audit → fix → verify
OpenForBots keeps the evidence available, but the first question is always what you should do next.
Inspect public crawler rules, delivery, content, structured data, and identity signals.
See which observed issue matters first instead of decoding a composite score.
Use the recommended change or generated remediation where the evidence supports one.
Run a fresh check and confirm the public evidence changed before calling the issue resolved.
Five dimensions
Five clear dimensions keep different kinds of website evidence understandable without collapsing them into one score.
What does the deployed crawler policy allow, and can the requested public resources be retrieved?
Does the initial response clearly explain the offer, audience, and practical outcome?
Are public declarations organised for reliable machine interpretation?
Are brand, organisation, authorship, and trust signals coherent and reviewable?
Does each action state what a later public audit must confirm?
Free focused tools
Use a focused checker when you already know the question, or jump to a generator when the missing signal is clear.
See how deployed robots.txt rules treat recognised AI crawler tokens.
Discovery filellms.txt checkerInspect whether an llms.txt file is available and what it exposes.
StructureJSON-LD generatorCreate machine-readable organisation or website identity data.
Remediationrobots.txt generatorBuild clearer crawler directives after you decide the access policy you want.
Explore by goal
Use a focused diagnostic, build the underlying mental model, or follow the end-to-end readiness checklist.
Inspect deployed robots.txt policy for documented AI crawler tokens before changing access rules.
Start with the concepts behind discovery, retrieval, citations, readiness, and their practical limits.
Review access, content, structure, identity, remediation, and verification as one workflow.
Need the technical detail?
Every conclusion remains connected to the evidence and limits behind it. OpenForBots keeps severity separate from evidence confidence. Public checks cannot prove provider indexing, citation, ranking, recommendation, or model use.
We audit ourselves — and publish the result
Technical readiness does not guarantee that an AI answer engine will discover, mention, or cite a source. The Citation Lab keeps a versioned prompt library and reports every completed observation, including negative and untested results.
Common questions
Yes. OpenForBots retrieves public website signals including robots.txt, the homepage response, initial HTML, JSON-LD, llms.txt, business clarity, and identity or trust signals. Completed anonymous audit snapshots are retained for up to 30 days under the published privacy policy.
Not by itself. OpenAI documents GPTBot and OAI-SearchBot as separate controls with different purposes. OpenForBots evaluates recognised crawler tokens individually instead of treating every OpenAI-related rule as the same decision.
No universal requirement has been established. OpenForBots inspects the file when it exists, but its absence is not treated as a critical failure or a guaranteed visibility problem.
No. OpenForBots evaluates observable public conditions. It cannot see a provider’s complete private index, ranking logic, retrieval process, or recommendation system.
The audit focuses on the initial public response and does not run an unrestricted browser session. A heavy client-rendering dependency may be reported as a possible concern, not as proof that a particular provider cannot render the page.
It checks whether the public page clearly exposes the organisation or product, category, intended audience, primary outcome, title, heading, and opening explanation. It does not claim to observe what a private model understands internally.