ClaudeBot and Claude-SearchBot are separate Anthropic bots. ClaudeBot collects public web content that may contribute to model training, while Claude-SearchBot indexes content to improve Claude search results. You can disallow ClaudeBot while allowing Claude-SearchBot.
Anthropic documents three web-access roles: model development, search optimization, and user-directed retrieval. ClaudeBot is associated with public-web collection that could contribute to training. Claude-SearchBot navigates the web to improve the relevance and accuracy of search results. Claude-User supports requests initiated by Claude users.
For robots.txt policy, the key point is that the first two bots are independent. Blocking ClaudeBot does not require blocking Claude-SearchBot, and allowing Claude-SearchBot does not grant ClaudeBot access.
ClaudeBot
Purpose: collect web content that may contribute to model development and training.
User-agent token:ClaudeBot.
Full-site restriction: a ClaudeBot group with Disallow: /.
Meaning of opt-out: Anthropic states that restricting ClaudeBot signals that future site materials should be excluded from its AI model-training datasets.
The rule applies to compliant future crawling on the exact host. It does not delete prior copies, protect private data, or block clients that misidentify themselves.
Claude-SearchBot
Purpose: index and analyze public content to improve Claude search-result quality.
User-agent token:Claude-SearchBot.
Visibility effect: Anthropic says disabling it may reduce a site’s visibility and the accuracy of its representation in user search results.
Guarantee: allowing access does not guarantee that the site will be selected, cited, or ranked for a query.
Common selective policy
Publish separate groups when you want Claude search discovery but do not want ClaudeBot training access:
Add rules for Claude-User only after making a separate decision about user-requested access. Anthropic says disabling Claude-User prevents retrieval in response to a user query and may reduce visibility in user-directed web search.
Crawl-delay and subdomains
Anthropic states that its bots honor standard robots.txt directives and support the non-standard Crawl-delay extension where appropriate. Use a modest delay only when logs show that crawl rate is a real server problem. A very high value can slow useful discovery without solving underlying performance issues.
Publish the intended robots.txt file on every subdomain you want to control. A policy at www.example.com/robots.txt does not automatically apply to docs.example.com or another protocol and port.
How to test the policy
Open the public robots.txt file and confirm the exact token spelling.
Test a public URL as Claude-SearchBot and confirm it is allowed.
Test the same URL as ClaudeBot and confirm it is blocked.
Use the checker to detect group and path mistakes.
Review current Anthropic documentation before treating an old block list as permanent.
No. Anthropic describes ClaudeBot as a model-development crawler and Claude-SearchBot as a crawler for improving search-result relevance and accuracy.
Can I block ClaudeBot but allow Claude-SearchBot?
Yes. Put the two tokens in separate robots.txt groups, disallow ClaudeBot, and allow Claude-SearchBot.
What happens if I block Claude-SearchBot?
Anthropic says this prevents indexing for search optimization and may reduce the site’s visibility and accuracy in Claude user search results.
Does Anthropic support Crawl-delay?
Yes. Anthropic states that it supports the non-standard Crawl-delay extension where appropriate. Use it only when measured crawl load requires throttling.
Is Claude-User covered by the Claude-SearchBot rule?
No. Claude-User is a separate agent for user-directed retrieval. Decide and configure its access independently.
We use essential storage for security and core features. With your permission, we may also use analytics and advertising technologies. Rejecting optional technologies does not block access to the site.
Non-essential categories are off unless you choose to enable them. You can return to these settings at any time from the footer.
Global Privacy Control is active.Your browser has requested an opt-out from sale, sharing, and targeted advertising. Advertising remains disabled.
Strictly necessary
Supports security, server sessions, form protection, administrator sign-in, and remembering your privacy choice.
Analytics
Allows Google Analytics to measure visits and interactions so the site can be improved. It is not loaded before permission.
Advertising and cross-site measurement
Allows advertising technologies when they are configured. This may involve ad delivery, fraud prevention, measurement, personalization, or cross-context advertising.
Your choice is stored for 180 days using a first-party preference cookie. A material policy change can ask you to choose again.