How to allow, verify or block Claude (Anthropic)
Leave Claude-User unblocked in robots.txt. Anthropic says its bots follow robots.txt directives, so no extra rule is needed.
Checked October 20, 2026. Claude in Chrome acts inside the user's own browser and sessions, and our sources do not say whether it sends a Claude-User token there.
How it identifies itself
| Signal | Value | Documented by the maker |
|---|---|---|
| user-agent | Claude-User | Yes support.claude.com |
| ip-list | https://claude.com/crawling/bots.json | Yes support.claude.com |
- Allow it
- Leave Claude-User unblocked in robots.txt. Anthropic says its bots follow robots.txt directives, so no extra rule is needed.
- Verify it
- Compare the source IP with the list at claude.com/crawling/bots.json. Anthropic says a match means the request came from Anthropic.
- Block it
- Add a robots.txt group for Claude-User with Disallow: /. Anthropic says its bots honor robots.txt and advises it over IP blocking, which it says may not hold as an opt-out.
robots.txt lines for Claude (Anthropic)
Copy the group you want for Claude-User. The most specific matching group wins over your * group.
Let it in
User-agent: Claude-User
Allow: /Keep it out
User-agent: Claude-User
Disallow: /What we can and can't confirm
Every signal above is published by the maker. Even so, a user agent string is easy to fake, so check requests against the maker's IP list or signature where one exists before you treat them as genuine.