Claude Traffic Index.
Daily trends in identifiable Anthropic Claude referral traffic.
Current state
Claude traffic index is at 80% of tracked peak, with +336.7% over 30 days.
Share of AI traffic
Claude accounts for 5.4% of all AI referral traffic across the panel.
7-day momentum
Short-term trend is +3.4% over the last 7 days versus the prior week.
Measure Claude referrals in your own GA4
Start with GA4's current AI Assistants channel, then audit the underlying sources and keep traffic that analytics cannot attribute in a separate evidence layer. The public panel's source mix is a panel benchmark, not global market share.
Reference: Google’s default channel definitions, Google’s GA4 landing page report and PostHog web analytics.
Traffic acquisition report
- Open Reports, then Acquisition, then Traffic acquisition. Check Session default channel group = AI Assistants first.
- Set the primary dimension to Session source / medium and compare the last complete month with the previous month.
- Add a Session source Matches regex filter to audit recognized assistant hostnames. Use the broad collector expression only when you can inspect aliases.
- Add Landing page + query string as a secondary dimension. Review Sessions, Engaged sessions, Key events, and Total revenue.
^((www\.)?claude\.ai|claude|anthropic)$Use a Matches regex filter on Session source. Keep the anchors so tagged campaigns do not match by accident.
Free-form exploration
Views align with this index's GA4 screen-page-view measure. Sessions and key events answer a different question: what happened after the click.
Measure AI landing pages and conversions in PostHog
Use the same source domains, but measure the entrance page and the conversion event in one funnel. This keeps referral volume separate from what visitors did after the click.
Referral and landing-page report
- Open Web analytics, set the last 30 days, and review Acquisition or Referrers for the AI source domains in the table below.
- Compare visitors, sessions, views, and conversion goals by referring domain. Keep broad aliases separate until you have checked the raw values.
- Open Product analytics and create a funnel. Make the first step
$pageview, filtered where$referring_domainmatches the AI source regex. - Use your real signup, lead, checkout, or purchase event as step two. Break down the entrance
$pageviewby$pathnameto compare landing pages.
PostHog fields to use
Filter the entrance event, not every funnel step. A conversion event may not carry the original referrer property.
Claude source values and limits
claude.ai, www.claude.ai, claude, anthropic- Treat claude.ai as the high-confidence source. The bare anthropic alias can include manually tagged campaigns that did not come from Claude.
- A click opened through an app, redirect, or privacy-preserving browser can lose its referrer and appear as Direct.
- GA4 does not expose the Claude prompt or answer behind the click. Use landing-page changes and your own conversion events as separate evidence.
Compare your Claude source mix
Use GA4 Views for an apples-to-apples comparison with this public index. The index does not expose an industry baseline for AI views as a share of all website views.
Enter your last 30 days of views to create a baseline before connecting anything.
Keep blind spots and bots in separate reports
- In-app browsers, app-to-browser handoffs, redirects, privacy settings, and referrer policies can strip the source. Those visits can appear as Direct or have an empty referrer.
- Gemini referrals can show as gemini.google.com, but Google AI Overviews and some AI Mode clicks can remain google / organic. Standard web analytics cannot reliably isolate them from conventional Search clicks.
- Treat dark AI traffic as an unmeasured remainder, not a number to relabel. Report identifiable AI referrals as the observed minimum and keep Direct and unassigned movement as a separate watchlist.
- A source domain identifies the sender when the referrer survives. It does not reveal the prompt, answer, citation, or citation position that caused the click.
- AI crawlers are bots, not human referrals. Keep crawler activity in server or CDN logs, and exclude known bots and internal traffic from visit and conversion reporting.
Connect the same workflow to Trakkr
Trakkr’s Visitors view connects Google Analytics, categorizes identifiable AI referrers, and reports landing pages and conversions alongside visibility data.
See Trakkr’s traffic analyticsClaude Traffic index since tracking started
Normalized to peak = 100%. Last updated: August 27, 2026
About this data
This index aggregates anonymized GA4 screen page views from properties connected to Trakkr by their owners. Page views are included when the session source matches "claude.ai" or a current source alias, then normalized to the highest traffic day (= 100%). Updated daily at 00:00 UTC.
Claude page views are identified on sessions where GA4 sessionSource matches claude.ai or a current Claude alias. The source-specific property count can be smaller than the overall panel, so short-window changes can be more volatile.
The 2,157 property count is the number of distinct GA4 properties with qualifying Claude source data in the current payload. It is not a denominator for every property connected to Trakkr.
The data is first-party and aggregated. Site owners connect their own Google Analytics, and no individual visitor is identified.
What is Claude referral traffic?
Claude referral traffic is the page views recorded after someone clicks a web citation or link from Claude. In Google Analytics 4, the clearest identifiable source is "claude.ai".
A Claude source row tells you where the click came from, but it does not reveal the conversation, prompt, or cited answer that produced the click. Compare landing pages and key events separately if you need to judge traffic quality.
The Trakkr Claude Traffic Index tracks identifiable Claude referral page views daily across 2,157 GA4 properties with qualifying source data, surfacing panel-wide movement that one site cannot show in isolation.
How much traffic does Claude send to websites?
Claude referral volume varies by site and period. The live metrics above show its current movement across 2,157 GA4 properties with qualifying Claude source data. This index does not infer traffic quality from the source alone.
Is Claude referral traffic growing?
The direction changes over time. Read the current 7-day and 30-day values above, and use a longer comparison window when the source-specific property count is small.
How do you measure Claude referral traffic?
Claude traffic is measured from GA4 screen page views on sessions whose source matches claude.ai or a current Claude alias. Trakkr aggregates anonymized property data and normalizes the series to the highest-traffic day (= 100%) without exposing absolute panel volume.
Why is Claude traffic smaller than ChatGPT traffic?
The current source ranking reports what the panel measures: relative referral page views and the number of properties with qualifying source data. It does not contain platform-wide usage or answer click-through rates, so it cannot assign one cause to the difference.
Does the Claude index include an industry breakdown?
Only when the current payload contains source-by-industry cells that clear its minimum property threshold. The page hides that section when no qualifying breakdown is available instead of estimating it.
How can I track Claude traffic to my own website?
Use the GA4 recipe and calculator on this page before signup. You can then connect your Google Analytics property to Trakkr to categorize identifiable AI referrers and compare your source mix with the public panel.
Benchmark your Claude traffic against the market
Connect Google Analytics to compare your Claude trend with category baselines and source-mix shifts.