AI search traffic: live data and measurement.
View daily market data for ChatGPT, Claude, Gemini, Perplexity and other AI sources, or use the GA4 and PostHog workflow to measure identifiable AI traffic to your own site.
Index at 69% of peak, +1.7% over 30 days
Claude+25.8%
Perplexity-11.2%Find AI referral traffic in your own GA4
Start with identifiable referrers, then keep a separate view of the traffic GA4 cannot attribute. This recipe mirrors the source matching used by the public panel while keeping uncertain aliases visible for review.
Reference: Google’s GA4 landing page report and PostHog web analytics.
Traffic acquisition report
- Open Reports, then Acquisition, then Traffic acquisition.
- Set the primary dimension to Session source / medium and compare the last 30 days with the previous period.
- Add a filter for Session source, choose Matches regex, and paste this expression.
- Add Landing page + query string as a secondary dimension. Review Sessions, Engaged sessions, Key events, and Total revenue.
^(([a-z0-9-]+\.)*chatgpt\.com|chat\.openai\.com|openai\.com|chatgpt|openai|(www\.)?perplexity\.ai|perplexity|(www\.)?claude\.ai|claude|anthropic|gemini\.google\.com|gemini|bard|copilot\.microsoft\.com|copilot|bing-chat|deepseek\.com|deepseek|grok\.com|x\.ai|grok|you\.com|phind\.com|phind|poe\.com|poe|meta\.ai|meta-ai)$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.
| Platform | Known hostname or source | Current collector aliases | What to check |
|---|---|---|---|
| ChatGPT | chatgpt.com, chat.openai.com | chatgpt, openai, openai.com | Review broad OpenAI aliases before grouping them with ChatGPT. |
| Perplexity | perplexity.ai | perplexity | A missing referrer can move an app click into Direct. |
| Claude | claude.ai | claude, anthropic | The broad Anthropic alias can include tagged campaigns. |
| Gemini | gemini.google.com | gemini, bard | Google AI Overviews and some AI Mode clicks can remain google / organic. |
| Copilot | copilot.microsoft.com | copilot, bing-chat | Do not group ordinary bing / organic traffic into Copilot. |
| DeepSeek | deepseek.com | deepseek | Low-volume rows can be volatile over short periods. |
| Grok | grok.com, x.ai (frontend mapping) | grok | The panel collector currently recognizes values containing grok. Its exact browser hostname is not verified, and x.com is deliberately excluded from the filter. |
| Other supported sources | you.com, phind.com, poe.com, meta.ai | phind, poe, meta-ai | The collector recognizes you.com, phind, poe, and meta-ai. meta.ai exists in its normalize map but not its current collection regex, so review it. |
Calculate your AI traffic share
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 analyticsAI referral traffic by source
Visible sources rescaled so the highest visible point = 100%.
Aggregated screen page views from 4,813 anonymized GA4 properties with qualifying AI source data. Visible chart lines are rescaled to the highest visible point. Source mix = % of identified AI referral page views (30d). Updated daily 00:00 UTC.
Who sends the most AI traffic?
Share of identified AI referral page views, past 30 days
ChatGPTChatGPT
GeminiGeminiClaudeClaudePerplexityPerplexity
GrokGrok
DeepSeekDeepSeekSingle-source deep dives
Which sectors get the most AI traffic?
30-day AI referral traffic performance across 6 verticals
If a source is rising
Expand citation-ready pages for that source's query style and prioritize prompts where your brand is absent.
If a source is declining
Audit source influence shifts and update authority pages before referral traffic loss compounds.
If you are benchmarking
Track your own source mix weekly and compare it against market share movement to prioritize GEO effort.
What is the AI search traffic index?
The AI Search Traffic Index is a daily-updated benchmark of identifiable AI referral page views. It tracks GA4 screen page views on sessions attributed to ChatGPT, Claude, Gemini, Perplexity, Copilot, DeepSeek, Grok, You.com, Poe, Phind and other supported source values across 4,813 anonymized properties.
Important: this index measures referral traffic, not citation share. A source can drive high referrals while your brand still has weak citation coverage across recommendation prompts.
The multi-source chart rescales the visible lines to the highest visible point. Source mix is calculated as each platform's percentage of identified AI referral page views over the trailing 30-day period. The index updates every day at 00:00 UTC.
Why track AI search traffic?
Referral traffic shows which identifiable AI sources sent people to a website. It does not measure prompts, citations shown without a click, or visits whose referrer was stripped. Marketers, SEOs, and growth teams can use it alongside citation and conversion data to monitor channel movement without treating one measure as the whole visibility picture.
Data sources and methodology
The pipeline filters GA4 sessionSource against the published source values and aliases, then aggregates the screenPageViews metric from matching sessions. All property-level data is anonymized before aggregation. The 4,813 count is the number of distinct GA4 properties with qualifying AI-source data in the current panel, not a denominator for every property connected to Trakkr.
Which AI search engine sends the most traffic to websites?
Use the current source ranking on this page. It orders the panel by each platform's share of identifiable AI referral page views over the latest 30-day period, so the answer can change as the data changes.
What does the AI Search Traffic Index measure?
The index aggregates GA4 screen page views on sessions whose source matches a current AI platform source or alias. It reports normalized trends and source mix across 4,813 properties with qualifying AI referral data, without exposing absolute panel volume.
Is AI referral traffic growing?
Read the current 7-day and 30-day changes shown above rather than assuming a permanent growth rate. The direction can change by period and platform, and short windows are sensitive to source mix and panel changes.
Does the index show AI traffic as a percentage of all website traffic?
No. The source ranking shows each platform's share of identified AI referral page views, not AI traffic as a share of all website traffic. Use the calculator and GA4 recipe on this page to establish that baseline for your own site.
How do you track traffic from different AI platforms?
The panel filters GA4 sessionSource using current platform domains and aliases, then aggregates screen page views from matching sessions across 4,813 anonymized properties. The source table on this page publishes the operational values and flags broad aliases that need review.
How is market share calculated?
Market share is each platform's percentage of all identified AI referral page views in the panel over the most recent 30-day period. It is a source-mix measure, not a share of all web traffic or AI usage.
Why can an AI click appear as Direct in GA4?
In-app browsers, app-to-browser handoffs, redirects, privacy settings, and referrer policies can remove the source before GA4 records the visit. Those clicks can appear as Direct, and standard GA4 data cannot reliably reconstruct the missing source.
Can GA4 separate Gemini and Google AI Overview traffic?
GA4 can identify a referral such as gemini.google.com when the referrer is preserved. Google AI Overviews and some AI Mode clicks can remain google / organic, so standard GA4 cannot reliably split those visits from conventional Google organic traffic.
Does an AI source row reveal the prompt or citation?
No. A source row identifies the sender when the referrer survives. It does not contain the prompt, answer, cited passage, or citation position that caused the click.
How can I check my AI search traffic in Google Analytics?
Open Reports, Acquisition, then Traffic acquisition. Use Session source / medium, add the anchored source regex published on this page, compare the last 30 days with the previous period, and break the result down by Landing page + query string.
How can I measure AI referral traffic in PostHog?
Start in Web analytics and review Acquisition or Referrers for known AI domains. Then create a funnel whose entrance pageview is filtered by $referring_domain, use a real conversion event as step two, and break the entrance pageview down by $pathname to compare landing pages.
How can I track AI traffic to my own website?
Start with the GA4 or PostHog workflow on this page. If you connect Google Analytics to Trakkr, the Visitors view categorizes identifiable AI referrers and reports landing pages and conversions alongside the public market panel.
Track AI search traffic to your website
Connect Google Analytics to see how much traffic ChatGPT, Claude, Gemini and Perplexity send to your site.