The AI Crawler & Bot Directory: Telemetry, Ingestion Mechanics & Robots.txt Directives

Zelitho Research · 13,971 Production Edge Sessions

The AI Crawler & Bot Directory: Telemetry, Ingestion Mechanics & Directives

An empirical reference guide to commercial LLM user-agents, based on verified edge logs across 110 continuous production days. Learn which bots drive live search citations versus offline training scrapes.

Sample Size: 13,971 Edge Sessions
•
Window: June 11 to September 30, 2026
•
Verification: Reverse DNS + ASN + TLS Validation
•
Core Metrics: LCV & CIR

The Great Decoupling: Live Inference vs. Model Pre-Training

For over two decades, search engine indexing operated on a single paradigm: crawlers ingested web pages into an inverted index to return ranked URL lists for human navigation. In 2026, web infrastructure split into two distinct bot categories with opposing economic models:

1. Live Runtime Inference Crawlers: Triggered synchronously when a human user submits a query to ChatGPT Search or Claude Artifacts. These crawlers ingest live HTML to verify factual claims and attach attributed footnote links. Blocking them removes your site from real-time AI answers.

2. Offline Batch Pre-Training Scrapers: Ingest millions of documents asynchronously to build training corpora for future foundational model weights. They do not generate live search referrals.

“Blocking all AI bots blindly in robots.txt cuts off live referral traffic from active search sessions. Allowing all bots without rate-limiting consumes server bandwidth without yielding user attribution.”

Master Bot Comparison: Observed Production Telemetry

Across our 110-day dataset ($N=13,971$), AI search crawlers drove 43.6% of all production edge requests (6,091 total bot requests), outpacing traditional Googlebot (1,012 requests) by 4.85 to 1. Below is the verified breakdown across commercial crawlers:

Bot User-AgentParent LabOperational RoleTrigger TypeObserved Hits (N=13,971)Executes JS?Recommendation
ChatGPT-UserOpenAILive Search GroundingSynchronous User Prompt2,970 (46.8%)No (SSR HTML)ALLOW FOR CITATIONS
GPTBotOpenAIBase Model TrainingScheduled Batch Sweep0 (Dormant)NoDISALLOW (OPTIONAL)
BytespiderByteDanceTikTok / Doubao LLM IndexContinuous High-Frequency1,827 (28.8%)NoRATE LIMIT / BLOCK
ClaudeBotAnthropicClaude Retrieval & TrainingPeriodic Directory Crawl164 (2.6%)NoALLOW (ROOT LINKS)
GooglebotGoogleTraditional Inverted IndexAlgorithmic Graph Traversal1,012 (15.9%)Yes (WRS Headless)STANDARD BASELINE

Core Architectural Takeaway: OpenAI’s training bot (GPTBot) logged zero visits throughout our entire tracking window, while its live search counterpart (ChatGPT-User) logged 2,970 visits. Enterprise teams can safely disallow GPTBot to protect IP without reducing live ChatGPT Search citations.

Detailed Crawler Profiles & Directives

Select a specific user-agent below to view its network parameters, verified IP/ASN ranges, crawl patterns, and copy-paste configuration directives:

Official Machine-Readable IP Feeds & Endpoints

To prevent scrapers from impersonating legitimate search agents, network engineers can cross-reference inbound requests against the official published IP endpoints maintained by each provider:

Crawler TokenProviderOfficial Published IP FeedVerification Standard
ChatGPT-UserOpenAIopenai.com/chatgpt-user.jsonPublished CIDR matching + rDNS (*.openai.com)
GPTBotOpenAIopenai.com/gptbot.jsonPublished CIDR matching + rDNS (*.openai.com)
OAI-SearchBotOpenAIopenai.com/searchbot.jsonPublished CIDR matching + rDNS (*.openai.com)
ClaudeBotAnthropicclaude.com/crawling/bots.jsonShared cluster CIDR list + robots.txt compliance
GooglebotGooglegooglebot.json (Google API)Forward-Confirmed Reverse DNS (FCrDNS)
BytespiderByteDanceNo public IP feed publishedEdge WAF user-agent filtering & ASN check

Frequently Asked Questions

Can I allow ChatGPT Search without letting OpenAI scrape my site for base model training?

Yes. OpenAI operates separate crawler tokens. You can disallow GPTBot in your robots.txt file to restrict training corpus ingestion while allowing ChatGPT-User to participate in live search queries and earn footnote citations.

Why does Bytespider consume more server bandwidth than Googlebot?

ByteDance uses high-concurrency recursive crawlers across multiple cloud providers without publishing centralized rate-control standards. In our 110-day benchmark, Bytespider generated 1,827 hits compared to Googlebot’s 1,012 hits, often running 15 to 40 requests per minute during batch ingestion cycles.

How can sysadmins distinguish legitimate AI bots from malicious scrapers?

Never whitelist crawlers solely by user-agent string. For OpenAI and Anthropic, match client IP addresses against their published JSON endpoints. For Googlebot, execute Forward-Confirmed Reverse DNS (FCrDNS) lookups to ensure the hostname resolves back to official Google domains.

Audit Your Server Logs for AI Crawler Ingestion

Discover which AI models are scraping your proprietary documentation without citing your brand. Zelitho measures your Live Citation Velocity and Crawl-to-Inference Ratio.

Explore Zelitho AI Growth Plans →