Awesome GEO

AI crawler user agents and which to allow in robots.txt

The Awesome GEO crawler list holds 25 AI crawler user agents from 12 operators, read on 11 November 2026. Each of the 25 sits in one of four groups by what its operator says it does: search, training, user-triggered fetches or other jobs.

How this was measured

The readings come from the Awesome GEO catalog of 157 free platforms. A script fetches each platform’s robots.txt file and tests it against each AI crawler’s user agent. 147 of the 157 platforms were last checked on 11 November 2026. The other 10 were last checked on 26 March 2026: Chamber of Commerce, Clutch, CodeSandbox, MuckRack, Observable, Stack Overflow, Tumblr, XenForo Community, Yellow Pages and npm. The script re-checks every platform each Monday at 06:00 UTC.

“Blocked” means the platform’s robots.txt disallows that user agent for the profile page or home page that was tested. “Allowed” means it does not. A platform with no robots.txt file is counted as allowed. A robots.txt that could not be fetched is counted as no reading.

Awesome GEO is built and maintained by Dmitry (Dee) Kargaev, a design engineer and independent GEO researcher in Los Angeles. The list is published as data/crawlers.yaml in the deeflect/awesome-geo repository on GitHub. The raw readings are in the data/sites folder of that repository under a CC0-1.0 licence.

What the four groups mean

A search crawler builds the index an assistant cites from. Training crawlers collect text for model training. When a person asks the assistant about a page, a user-triggered fetcher loads it. The fourth group, other jobs, holds tasks outside those three.

The list has 8 user agents for search, 8 for training, 7 for user-triggered fetches and 2 for other jobs. A robots.txt rule names a crawler by its user agent token, written exactly as in the tables below. Two training tokens, Google-Extended and Applebot-Extended, send no requests of their own and exist only as robots.txt tokens.

User agents by group

The last two columns give the number of the 157 catalog platforms that allow or block each user agent.

User agentOperatorWhat it doesDocumentationAllowed byBlocked by
OAI-SearchBotOpenAISurfaces sites in ChatGPT search resultsLinked132 of 15721 of 157
Claude-SearchBotAnthropicImproves search result quality for ClaudeNone linked128 of 15719 of 157
BingbotMicrosoftBing’s standard crawler; handles most of Bing’s crawlingLinked143 of 1574 of 157
PerplexityBotPerplexitySurfaces sites in Perplexity search results; not used for trainingLinked130 of 15723 of 157
ApplebotAppleSearch in Spotlight, Siri and Safari; may also ground Apple AI answersLinked139 of 1578 of 157
meta-webindexerMetaIndexing for Meta AI search citationsNone linked128 of 15719 of 157
Amzn-SearchBotAmazonSearch experiences such as AlexaNone linked127 of 15720 of 157
DuckAssistBotDuckDuckGoFetches sources for AI-assisted answersLinked128 of 15719 of 157

Operator documentation: OAI-SearchBot, Bingbot, PerplexityBot, Applebot and DuckAssistBot.

Training

User agentOperatorWhat it doesDocumentationAllowed byBlocked by
GPTBotOpenAICollects content for model trainingNone linked108 of 15745 of 157
ClaudeBotAnthropicCollects content for model trainingLinked110 of 15743 of 157
Google-ExtendedGoogleGemini training and grounding; no effect on Google Search; robots.txt token onlyLinked113 of 15740 of 157
Applebot-ExtendedAppleOpts content out of Apple’s AI training; robots.txt token onlyNone linked110 of 15737 of 157
Meta-ExternalAgentMetaTraining and indexing for Meta AI productsLinked114 of 15733 of 157
AmazonbotAmazonGeneral crawling; content may be used for trainingLinked115 of 15732 of 157
CCBotCommon CrawlBuilds Common Crawl’s open web archiveLinked103 of 15744 of 157
BytespiderByteDanceWidely reported AI crawler; no official vendor doc foundNone linked105 of 15748 of 157

Operator documentation: ClaudeBot, Google-Extended, Meta-ExternalAgent, Amazonbot and CCBot.

User-triggered fetches

User agentOperatorWhat it doesDocumentationAllowed byBlocked by
ChatGPT-UserOpenAIFetches pages for user actions in ChatGPT and Custom GPTsNone linked131 of 15722 of 157
Claude-UserAnthropicFetches pages when a Claude user asksNone linked129 of 15718 of 157
Google-AgentGoogleAgents on Google infrastructure acting on a user’s requestLinked127 of 15720 of 157
Perplexity-UserPerplexityFetches pages when a Perplexity user asksNone linked127 of 15720 of 157
Meta-ExternalFetcherMetaFetches pages on user requestNone linked127 of 15720 of 157
Amzn-UserAmazonLive fetches on behalf of usersNone linked127 of 15720 of 157
MistralAI-UserMistralUser-requested fetches; no automatic crawling or trainingLinked128 of 15719 of 157

Operator documentation: Google-Agent and MistralAI-User.

Other jobs

User agentOperatorWhat it doesDocumentationAllowed byBlocked by
OAI-AdsBotOpenAIChecks landing pages of ads submitted to ChatGPTNone linked128 of 15719 of 157
Google-CloudVertexBotGoogleCrawls requested by site owners for Vertex AI AgentsNone linked122 of 15725 of 157

Which to allow

Search and user-triggered crawlers fetch pages for answers. Training crawlers collect text for training. If you want your site cited, that split is the one to read the tables by, and the choice between the groups is yours.

The robots.txt tool is a free generator and checker for AI crawler rules, with the crawlers grouped as Search, Training, User-triggered and Other. You can load a site’s current robots.txt, start from one of three presets and switch single crawlers between allowed and blocked.

Findings

  • In the Awesome GEO catalog of 157 platforms, Bytespider is the most blocked AI crawler user agent, blocked by 48 platforms, followed by GPTBot at 45 and CCBot at 44.
  • Bingbot is the least blocked AI crawler user agent in the catalog, blocked by 4 of 157 platforms, followed by Applebot at 8.
  • Across the 157 platforms, the number blocking a user agent runs from 4 to 23 for search, 32 to 48 for training, 18 to 22 for user-triggered fetches and 19 to 25 for other jobs.
  • OpenAI has the most user agents in the list with 4, ahead of Anthropic, Google, Meta and Amazon with 3 each.
  • 12 of the 25 user agents have an operator documentation page linked in the list.

Limits of the readings

The check reads robots.txt only. It does not see blocks made by a firewall, a CDN, a login wall or rate limiting, and it does not show whether a crawler obeys the file.

robots.txt rules can differ by path, so a platform that blocks the tested page may allow other pages. A reading says nothing about whether an AI assistant cites the platform.

The counts describe the 157 catalog platforms, not your site. For a given user agent the allowed and blocked counts need not add up to 157, because a platform whose robots.txt could not be fetched has no reading.

Revisions

  • 11 November 2026: first version of this page, read from the Awesome GEO catalog.