Claude-SearchBot robots.txt Rules for Claude Search
Claude-SearchBot is Anthropic’s automated search crawler. Allowing it can help public pages appear in Claude search results; blocking it can reduce that visibility. Control it separately from ClaudeBot and Claude-User.
Claude-SearchBot is Anthropic’s crawler for discovering and analyzing public web content used to improve the relevance and accuracy of Claude search responses. It is not the same agent as ClaudeBot, which is associated with model-development crawling, or Claude-User, which retrieves a page after an individual user asks Claude to access it.
This separation lets a publisher make a precise choice: keep Claude search discovery available while opting out of future training crawls. Anthropic states that its bots honor standard robots.txt directives and that disabling Claude-SearchBot may reduce a site’s visibility and accuracy in user search results.
Recommended selective policy
For many publishers, the useful configuration is to block ClaudeBot but allow Claude-SearchBot. The example on this page does exactly that and keeps Claude-User available for user-directed retrieval. You can generate a broader policy with the robots.txt generator and test the published file with the checker.
If you want Claude search excluded completely, replace the Claude-SearchBot Allow: / line with Disallow: /. To exclude only sensitive sections, list those paths under the Claude-SearchBot group instead of blocking the whole host.
What blocking changes—and what it does not
Blocking Claude-SearchBot concerns Anthropic’s search discovery. It does not block Googlebot, Bingbot, or ordinary search indexing unless your robots.txt file also contains rules for those agents. It also does not protect confidential content: authentication, authorization, and server-side access controls are still required for private pages.
Crawl rate and subdomains
Anthropic documents support for the non-standard Crawl-delay directive where appropriate. Use it only when request frequency is a real server concern. Robots.txt applies per host, so a rule on example.com does not automatically cover docs.example.com or another subdomain.
How to verify the result
Publish the file at https://your-domain.com/robots.txt.
Confirm that the Claude-SearchBot group contains the intended paths.
Check that no broad User-agent: * rule accidentally blocks public content.
Anthropic uses Claude-SearchBot to discover and analyze public web content for better search relevance and accuracy in Claude search experiences.
Can I allow Claude-SearchBot while blocking ClaudeBot?
Yes. They use separate robots.txt tokens, so you can allow Claude-SearchBot for search discovery and disallow ClaudeBot for model-development crawling.
Will blocking Claude-SearchBot affect Google Search?
No, not by itself. Google Search uses Googlebot. Google visibility changes only if your robots.txt rules also restrict Googlebot or use an overly broad group.
Does Claude-SearchBot support Crawl-delay?
Anthropic documents support for the non-standard Crawl-delay directive where appropriate, although it should be used only when crawl frequency is a genuine concern.
Do I need separate rules for subdomains?
Yes. Robots.txt is scoped to a specific host, protocol, and port, so each subdomain that needs a policy should expose its own robots.txt file.
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.