Claude-User: Anthropic's fetch for a person
Claude-User belongs to Anthropic. It opens a page at the moment a person asks an assistant about it. It doesn't crawl on its own. When it is turned away, the assistant can't read your page while answering, so it answers from memory or from other sites.
| Operator | Anthropic |
|---|---|
| Used for | Claude |
| Type | Fetch for a person |
| robots.txt name | Claude-User |
| User agent | Not published by the operator |
| Published IP ranges | https://claude.com/crawling/bots.json |
| Blocked by top sites | 8% of 740 (study) |
| Official documentation | support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from- |
Anthropic documents the robots.txt name but not a full user-agent string.
Allow or block Claude-User in robots.txt
To block it on the whole site:
User-agent: Claude-User
Disallow: /To allow it explicitly (useful when a rule for all bots would block it):
User-agent: Claude-User
Allow: /Anthropic says its bots honour robots.txt. Disallowing this one stops Claude retrieving your pages in response to a user question, which may reduce your visibility there.
robots.txt is a request, not a wall. A CDN or firewall rule can turn a bot away even when robots.txt allows it, and nothing in the file will show that.
The free check requests your home page as a browser and as AI bots, reads your robots.txt and shows what gets blocked. No sign-up.
Check my siteIs it really Claude-User?
Anyone can send a request with this bot's name. Anthropic publishes the IP ranges its requests come from, so a request that carries the name from another address is an impostor. PageLens checks every request from this bot against that list.
See Claude-User on your own site
Claude-User doesn't run JavaScript, so analytics scripts never record it. AI Visibility in PageLens reads it from your server or CDN and shows which pages it requested, when, and which requests ended in a 404.