Claude-SearchBot
Claude-SearchBot indexes web pages for an AI-powered search product operated by Anthropic. Unlike a pure training crawler, AI search crawlers are designed to drive users back to the original source via citations and links.
The crawl pattern looks similar to a traditional search engine: regular, broad, and bounded by your robots.txt directives. The difference is that ranking is done by an LLM, not a classic ranking algorithm.
Allowing Claude-SearchBot is generally how your site stays discoverable inside AI answer engines. The traffic it sends back is small but high-intent: users who clicked a citation usually wanted exactly what you wrote.
See Claude-SearchBot on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
Known UA examples
example 1
Verify by IP
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
Published IP ranges
Crawl frequency
Continuous
Honors robots.txt
Yes
Honors Crawl-delay
Yes
Anthropic runs 12 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Live-Fetch AI
4Training Crawler
2Agentic Browser
2Agentic Commerce
2AI Coding Tool
1AI Search Index
1- Claude-SearchBotYou are here
Share of AI bot traffic
1.6%
↑ 1500% vs 12 mo ago
% of top sites blocking it
9.0%
↑ 800% vs 12 mo ago
Top page categories crawled
AI Search Indexs as a category, share of all bot traffic
5.9%
↑ 556% vs 12 mo ago
Sum of every ai search index we have public stats on. Compare to Claude-SearchBot's individual trend above to see if it's pulling ahead of its category or falling behind.
Crawl-to-click ratio
52 : 1
For every 1,000 fetches, this agent sends ~19 human visits back. Cloudflare crawl-to-click data
Snapshot updated
2026-04
Connect Agent Analytics for daily, per-site numbers.
Source: Anthropic bot documentation, Cloudflare Radar AI Insights
Should I let Claude-SearchBot through?
In most cases, yes. AI search crawlers cite and link back. Allowing is how your content becomes discoverable inside AI answers. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Claude-SearchBot affect my Google rankings?
No. Claude-SearchBot feeds Anthropic's AI answer engine, which is a separate distribution channel from classical search. Blocking it removes you from citations inside Anthropic's product, but Google and Bing keep ranking you the same.
How do I confirm a request is really from Claude-SearchBot?
Two checks. The User-Agent header should match a known Claude-SearchBot string, and the request's source IP should fall inside Anthropic's published ranges. The User-Agent alone is trivially spoofable, so the IP check is what gives you confidence. Anthropic publishes the ranges so you can validate at the CDN or edge.
How is Claude-SearchBot different from Googlebot?
Both crawl the web, but they feed completely different surfaces. Googlebot powers Google Search, where you compete for ten blue links. Claude-SearchBot powers Anthropic's AI answer engine, where you compete for one of a handful of citations in a written-out paragraph. The crawl mechanics are similar, the consumption pattern is not.
How is Claude-SearchBot different from Anthropic's other bots?
Anthropic splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Anthropic family above to see which ones actually matter for your site.
What's the cleanest way to control Claude-SearchBot?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.