On demand · Anthropic
Claude-User
Fetches a page because a Claude user asked about it. One request per user action, not a crawl. Blocking it stops Claude reading your pages when a user pastes a link.
- Operator
- Anthropic
- Purpose
- User-triggered fetchers
- Feeds
- Claude (live browse)
- robots.txt token
Claude-User- Honours robots.txt
- Honours robots.txt
- Documentation
- support.anthropic.com
What it looks like in server logs
A representative user-agent string. Version numbers change; the Claude-User token does not. Paste your own log line into the user-agent checker to confirm a match.
Mozilla/5.0 (compatible; Claude-User/1.0; +https://www.anthropic.com)How to block Claude-User
Add this to the robots.txt at the root of your domain. Robots.txt is advisory: it works only on crawlers that choose to read it. This one is honours robots.txt according to its operator.
User-agent: Claude-User
Disallow: /
To block every user-triggered fetcher at once, or to block training while keeping AI search citations, use the robots.txt generator.
How to allow Claude-User while blocking others
A more specific User-agent group wins over a wildcard. Place this above any User-agent: * block that disallows paths, and Claude-User keeps full access.
User-agent: Claude-User
Allow: /
How to verify a genuine hit
The user-agent string is self-asserted: anyone can send it from a laptop, and scrapers routinely impersonate well-known crawlers to slip past filters aimed at unknown ones.
No published IP ranges; verify by behaviour only.