What is the Claude-User user agent?

Requests from Claude-User carry "claude-user" in the User-Agent header (matching is case-insensitive). The full string includes a version number that changes over time; Anthropic's documentation lists the current one. In robots.txt, the token is Claude-User.

How do I verify Claude-User?

Anthropic publishes the IP ranges Claude-User uses. A request is real when its IP is inside that list. Paste an IP into HadoSEO's free bot verifier to check it against the published data.

How do I block Claude-User in robots.txt?

Add "User-agent: Claude-User" followed by "Disallow: /" to your robots.txt. Blocking Claude-User does not block ClaudeBot or Claude-SearchBot: each has its own token and its own rule. robots.txt is a request, not a lock: a scraper using Claude-User's name ignores it, which is why verification matters.

Can I see when Claude-User visits my site?

Yes. HadoSEO logs every Claude-User request by page, checks it against Anthropic's published data, and flags requests that use the name from IPs Anthropic doesn't own. For a one-off look, the free log file analyzer reads a week of your server logs in the browser.

[ AI answer fetcher · Anthropic ]

Claude-User: Anthropic's AI answer fetcher.

The fetcher Claude uses when a person's question needs a live page. It reads your page while the answer is being written. Its intent is answer fetch: fetches your page live to answer a user's question.

answer fetchverifiable by published IP ranges

IP ranges last updated Oct 25, 2026

Check a Claude-User IP All AI crawlers

[ technical facts ]

operator: Anthropic
intent: answer fetch
user agent contains: claude-user
robots.txt token: Claude-User
verification: published IP rangesverified
official IP list: claude.com/crawling/bots.json
ranges in registry: none loaded (source unreachable at last refresh)
last updated: Oct 25, 2026
operator docs: support.anthropic.com/en/articles/8896518

[ verify ]

How to verify a real Claude-User request.

Anthropic publishes the IP ranges Claude-User uses. A request is real when its IP is inside that list.

01Check the User-Agent header contains "claude-user" (case-insensitive). That is only a claim: anyone can send it.
02Download Anthropic's published list (https://claude.com/crawling/bots.json) and check the request IP falls inside one of its ranges.
03Inside the list: the real Claude-User. Outside it: a request using Claude-User's name from someone else's server.

Skip the lookups: the free bot verifier checks one IP against the same registry, and the log file analyzer checks every Claude-User request in a week of access logs. Requests that fail are flagged as spoofed, not hidden.

[ robots.txt ]

Block or allow Claude-User in robots.txt.

Add one of these groups to the robots.txt at your domain root. The token matches case-insensitively. Anthropic runs other crawlers with their own tokens, so a rule for Claude-User leaves ClaudeBot (training) and Claude-SearchBot (search index) untouched.

block Claude-User

User-agent: Claude-User
Disallow: /

allow Claude-User

User-agent: Claude-User
Allow: /

robots.txt only binds crawlers that choose to follow it. A scraper sending Claude-User's user agent from its own servers won't, which is why HadoSEO checks the IP behind every request.

[ questions ]

Claude-User, answered.

[ free scan ]