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.

Public website pages available to Claude search while a separate AI training route is blocked

Copy-paste robots.txt example

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: Claude-User
Allow: /

What Claude-SearchBot does

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

  1. Publish the file at https://your-domain.com/robots.txt.
  2. Confirm that the Claude-SearchBot group contains the intended paths.
  3. Check that no broad User-agent: * rule accidentally blocks public content.
  4. Run the site’s robots.txt checker after deployment.

For a direct comparison of the Anthropic agents, see ClaudeBot vs Claude-SearchBot.

FAQ

What is Claude-SearchBot used for?

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.

Related tools

Related pages

Website with separate routes for blocked training crawling, open search discovery, and user-requested access ClaudeBot robots.txt Guide

ClaudeBot is Anthropic’s crawler for public web content that may contribute to model development and training. A ClaudeBot-specific Disallow rule signals that future material should be excluded from Anthropic training crawls. Claude-SearchBot and Claude-User are separate agents with different purposes.

Single user-requested AI fetch reaching a public webpage while private content remains behind server-side access control Claude-User robots.txt and User-Requested Access

Claude-User is used when a person asks Claude to retrieve web content. Anthropic says it honors robots.txt, but robots.txt is only a crawler preference—not security. Protect private pages with authentication and authorization.

Three separate Claude crawler routes blocked by independent robots.txt rules while regular search remains open Block Claude Crawlers robots.txt Template

To block Anthropic’s documented Claude agents, publish separate Disallow groups for ClaudeBot, Claude-SearchBot, and Claude-User. Blocking all three also removes training, Claude search discovery, and user-directed retrieval, so use only the groups that match your policy.

Separate ClaudeBot training, Claude-SearchBot discovery, and secondary user-request access routes ClaudeBot vs Claude-SearchBot: Training vs Search

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.

Public pages moving through AI search discovery and technical access toward possible source citation robots.txt for AI Search Visibility and Citations

To support AI search visibility, allow each provider’s documented search crawler—such as OAI-SearchBot, Claude-SearchBot, and PerplexityBot—while keeping Googlebot and Bingbot accessible. Robots.txt only permits crawling; it does not guarantee indexing, citation, ranking, or access through a firewall.