Gemini Traffic Index.
Daily trends in identifiable Google Gemini referral traffic.
Current state
Gemini traffic index is at 52% of tracked peak, with +10.9% over 30 days.
Share of AI traffic
Gemini accounts for 3.3% of all AI referral traffic across the panel.
7-day momentum
Short-term trend is -25.4% over the last 7 days versus the prior week.
Measure Gemini 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.
^(gemini\.google\.com|gemini|bard)$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.
Gemini source values and limits
gemini.google.com, gemini, bard- Treat gemini.google.com as the high-confidence source. Review the bare gemini and bard aliases in the raw export before grouping them.
- Google AI Overviews and some AI Mode clicks can remain google / organic. Standard GA4 cannot reliably separate those clicks from other Google organic sessions.
- Gemini app, Chrome, redirect, and privacy behavior can strip the referrer, which can move a real click into Direct.
Compare your Gemini 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 analyticsGemini 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 "gemini.google.com" or a current source alias, then normalized to the highest traffic day (= 100%). Updated daily at 00:00 UTC.
Gemini page views are identified on sessions where GA4 sessionSource matches gemini.google.com or a current Gemini alias. Google AI Overviews and Google organic visits are not counted as Gemini because the referrer does not provide a reliable split.
The 3,650 property count is the number of distinct GA4 properties with qualifying Gemini 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 Gemini referral traffic?
Gemini referral traffic is the page views recorded after someone clicks a link from the Gemini app or gemini.google.com. This index does not treat every Google organic visit as a Gemini visit.
In Google Analytics 4, the clearest identifiable source is "gemini.google.com". Google AI Overviews and some AI Mode clicks can remain inside google / organic, where standard GA4 reporting cannot reliably separate them from conventional Search clicks.
The Trakkr Gemini Traffic Index tracks identifiable Gemini referral page views daily across 3,650 GA4 properties with qualifying source data. It helps you compare the direction of your own Gemini traffic with the panel, while keeping Google organic as an acknowledged blind spot.
How much traffic does Google Gemini send to websites?
Gemini referral traffic varies by site and period. The live metrics above show its current share and movement across 3,650 GA4 properties with qualifying Gemini source data. Use the GA4 recipe on this page to compare the same measure on your own site.
Is Gemini referral traffic growing?
The direction changes over time. Use the current 7-day and 30-day values above instead of assuming a permanent growth rate, and compare them with a longer date range because short windows can be noisy.
How do you measure Gemini referral traffic?
Gemini traffic is measured from GA4 screen page views on sessions whose source matches gemini.google.com or a current Gemini alias. Trakkr aggregates the anonymized property data and normalizes the series to the highest-traffic day (= 100%) without exposing absolute panel volume.
Is Gemini traffic the same as Google AI Overviews?
No. This index counts identifiable Gemini sources such as gemini.google.com. AI Overviews and some AI Mode clicks can carry Google's standard organic referrer, so this page does not claim to isolate them from conventional Google Search traffic.
Does the Gemini 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 Gemini 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 Gemini traffic against the market
Connect Google Analytics to compare your Gemini trend with category baselines and source-mix shifts.