- ✓Report Claude’s documented bots by purpose, not as one machine audience.
- ✓Keep user-requested retrieval separate from the later human click.
- ✓Connect observable referrals to content use and outcomes with explicit attribution rules.
Classify Claude’s actors before counting
Anthropic’s names describe materially different purposes.
Anthropic documents ClaudeBot for collecting web content that may contribute to model development, Claude-SearchBot for search quality, and Claude-User for access at a user’s direction. These requests belong in server or CDN reporting.
A human visit begins only when a person’s browser reaches the site. Even Claude-User should not be counted as a visitor because the fetch is performed by a machine on the user’s behalf.
| Actor | Purpose | Analytics class |
|---|---|---|
| ClaudeBot | Model development | Crawler |
| Claude-SearchBot | Search quality | Search crawler |
| Claude-User | User-directed retrieval | Agent / fetcher |
| Browser referral from Claude | Human click | AI referral |
Measure the browser visit as acquisition
When a Claude referrer is present, preserve it through the same first-party journey used for other sources.
Record source, landing page, actions, conversion, and value. Use a normalized Claude provider label while retaining enough raw evidence to audit classification changes.
If referral information is missing, keep the visit Direct or otherwise unknown. A simultaneous increase in ClaudeBot requests is interesting context, not proof that the direct visit came from Claude.
- Observed Claude source
- Landing page
- Meaningful action
- Conversion and value
- Attribution window
- Unknown coverage
Measure policy effects separately
Robots controls can change machine access without directly changing human demand.
Anthropic states that its bots honor robots.txt and documents the consequences of restricting each token. Log the policy version that applied when a request was allowed or denied.
When traffic or citations change after a policy update, compare crawler access, answer visibility, and observed human referrals as separate series before drawing a conclusion.
Evidence noteProvider bot names and behavior can change; the Anthropic help article is the current verification reference for this directory.
Methodology and verification.
Last verified August 17, 2026. The page is updated when the underlying analytics or provider documentation changes materially.
- 01
Reviewed the linked primary documentation and separated provider claims from observations a website can verify.
- 02
Kept human referrals, sampled answer visibility, machine requests, and modeled influence in separate evidence classes.
- 03
Marked limitations wherever the available source or request data cannot support a provider-level conclusion.
Verify the evidence.
Provider behavior and analytics definitions change. These are the primary references reviewed for this page.
Questions teams ask.
Is Claude-User a human visitor?+
No. It is a machine fetch performed at a user’s direction. A later browser click is a separate human referral event.
Can Claude referrals appear in GA4?+
Yes when usable referral information reaches the site. Google’s May 2026 announcement names Claude among popular assistants covered by the new measurement view.
Should ClaudeBot be blocked?+
That is a publisher policy decision. Evaluate model-development, search-visibility, licensing, capacity, and business goals separately for each documented bot.