CrawlPact

Claude-User

User-agent token
Claude-User
Purpose
User-triggered
Status
active
Last verified
2026-07-24

Anthropic documents Claude-User as the crawler that lets Claude access a website when a user directs it to do so as part of their query — a user-initiated request, not a bulk crawl.

Why this is different from ClaudeBot

Claude-User is tracked separately from the training-purpose ClaudeBot and the search-purpose Claude-SearchBot. A website can restrict one without restricting the others — CrawlPact’s “Allow Search, Block Training” preset relies on exactly this kind of distinction.

Site-owner controls

Standard robots.txt disallow rules apply. See /limitations for what a robots.txt rule can and cannot guarantee.

Example robots.txt configuration

To disallow Claude-User specifically, without affecting any other crawler:

User-agent: Claude-User
Disallow: /

If no dedicated User-agent: Claude-User group exists in a domain's robots.txt, this crawler falls back to whatever the wildcard User-agent: * group says (RFC 9309) — see robots.txt syntax basics for how group selection works.

Official source: https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler

Verified against the source above as of 2026-07-24 — see how CrawlPact verifies crawler information.

See how this applies to your own site

Run a free audit to check your declared AI crawler policy against your own domain, or use the AI crawler checker to check this one crawler specifically.

Audit a domain

Analytics preferences

CrawlPact uses optional Google Analytics and Microsoft Clarity on public marketing pages to understand which content is useful and how visitors actually use it. Neither is used in the authenticated app or admin areas. You can accept or decline analytics without affecting the service.