AI crawler directory — all 28 bots

Every AI crawler we track: user-agent token, vendor, purpose, whether it honors robots.txt, and how to verify a hit is genuine. Compiled July 2026 from vendor crawler docs (21/28 vendor-doc verified, 7 checked against community lists and our own production logs).

TokenVendorPurposeAppears in logs?robots.txtVerificationDocs
AI2BotAllen Institute for AITrainingyeshonors robots.txtnone publisheddocs
AmazonbotAmazonTrainingyeshonors robots.txtpublished IP listdocs
Amzn-SearchBotAmazonAI searchyeshonors robots.txtpublished IP listdocs
Amzn-UserAmazonUser actionyesclaims robots compliancepublished IP listdocs
anthropic-aiAnthropicTrainingyesclaims robots compliancenone publisheddocs
Claude-SearchBotAnthropicAI searchyeshonors robots.txtpublished IP listdocs
Claude-UserAnthropicUser actionyesclaims robots compliancepublished IP listdocs
ClaudeBotAnthropicTrainingyeshonors robots.txtpublished IP listdocs
ApplebotAppleAI searchyeshonors robots.txtIP list + rDNSdocs
Applebot-ExtendedAppleTrainingrobots.txt token only — never in logshonors robots.txtn/a — robots.txt tokendocs
BytespiderByteDanceTrainingyesignores robots.txtnone publishednone
cohere-aiCohereTrainingyesignores robots.txtnone publishednone
CCBotCommon CrawlTrainingyeshonors robots.txtIP list + rDNSdocs
DiffbotDiffbotTrainingyesignores robots.txtnone publisheddocs
DuckAssistBotDuckDuckGoAI searchyeshonors robots.txtpublished IP listdocs
Google-CloudVertexBotGoogleUser actionyeshonors robots.txtIP list + rDNSdocs
Google-ExtendedGoogleTrainingrobots.txt token only — never in logshonors robots.txtn/a — robots.txt tokendocs
GoogleOtherGoogleTrainingyeshonors robots.txtIP list + rDNSdocs
PetalBotHuaweiAI searchyesclaims robots compliancerDNSdocs
meta-externalagentMetaTrainingyesclaims robots compliancepublished IP listdocs
meta-externalfetcherMetaUser actionyesignores robots.txtASN / RDAPdocs
MistralAI-IndexMistral AIAI searchyesclaims robots compliancepublished IP listdocs
MistralAI-UserMistral AIUser actionyesclaims robots compliancepublished IP listdocs
ChatGPT-UserOpenAIUser actionyesclaims robots compliancepublished IP listdocs
GPTBotOpenAITrainingyeshonors robots.txtpublished IP listdocs
OAI-SearchBotOpenAIAI searchyeshonors robots.txtpublished IP listdocs
Perplexity-UserPerplexityUser actionyesignores robots.txtpublished IP listdocs
PerplexityBotPerplexityAI searchyesclaims robots compliancepublished IP listdocs
Why two bots "never appear in logs": Google-Extended and Applebot-Extended have no HTTP user agent. The actual page fetches happen under Googlebot/Applebot UAs; these tokens exist purely as robots.txt User-agent: lines that control whether already-crawled content may be used for AI training. A log line matching either name is a spoofer.

The three purposes

Training — Content is copied into datasets used to train foundation models. Blocking costs you nothing in traffic today; allowing is a donation of your content to model weights with no citation or referral in return.

AI search — An AI search index that can cite and link your pages in answers (ChatGPT search, Perplexity, Claude search, Alexa, Siri). Blocking removes you from those answer surfaces — for most sites these are wanted crawlers.

User action — A live fetch made because a human asked the assistant about your page right now. Closest thing to a real visitor; several of these (Perplexity-User, meta-externalfetcher) ignore robots.txt by design because the request is user-initiated.

AnswerFootprint crawler analytics — bot roster compiled July 2026 from vendor crawler docs and published IP lists (21/28 vendor-doc verified). The analyzer runs 100% client-side — your logs never leave this browser. User-agent strings can be spoofed; treat UA matches as a first pass and verify by IP before acting. Errors in the bot data: report them.