Primary related guide or tool
Continue the workflow with this related LLMs.txt Kit resource.
/data/ai-crawler-user-agents.htmlAI crawler user-agent cheat sheet
A compact cheat sheet for common AI and search crawler user-agent tokens and what to check before changing access.
Fast answer
If your goal is to recognize common crawler tokens before editing robots.txt, start with this framing: many teams copy blocklists without knowing which crawler does what. The useful deliverable is a crawler-token review checklist.
This page is intentionally conservative. It treats crawler files, URL inspection, feeds, and server logs as discovery and measurement aids, not as guaranteed ranking levers.
When to use this playbook
Use it when webmasters reviewing crawler tokens need a concrete next step and a page that can be linked from a hub, a community answer, a README, or a launch checklist. The page should help someone make a decision even if they never buy anything or contact the site owner.
The strongest pages in this topic cluster have three traits: they answer one narrow question, they include a copyable artifact, and they link to the relevant tool or proof page so the reader can act immediately.
Recommended workflow
- List the crawler tokens relevant to the site.
- Read official docs before blocking.
- Separate search, training, user-triggered, and archival crawlers.
- Test robots.txt after changes.
Pre-publish checklist
- OAI-SearchBot reviewed.
- GPTBot reviewed.
- Googlebot reviewed.
- Google-Extended reviewed.
- PerplexityBot reviewed.
Copyable working note
Use this as a starting point in a ticket, README, client note, or launch log. Edit it to match the real site before publishing.
Token
Documented purpose
Current rule
Desired rule
EvidenceWhat not to count as proof
Do not count this setup as traffic by itself. A submitted sitemap, an IndexNow receipt, a crawler log hit, or an indexing request can show discovery work, but none of them proves rankings, impressions, clicks, conversions, or AI citations. Organic proof should come from Search Console, analytics, qualified referral evidence, or server logs interpreted for the right purpose.
The main pitfall for this topic is: Assuming every AI-looking user agent has the same purpose.
Related resources
Next supporting resource
Continue the workflow with this related LLMs.txt Kit resource.
/data/ai-crawler-policy-benchmark.htmlAll free tools
Continue the workflow with this related LLMs.txt Kit resource.
/tools/Proof dashboard
Continue the workflow with this related LLMs.txt Kit resource.
/proof.html