?st_source=ai_overview<\/code>, added to the end of URLs that appear within Google’s AI Overviews and AI Mode responses. The observation was first shared on LinkedIn and showed up across multiple examples, including links cited inside the source list that AI Mode displays alongside its answers.<\/p>\nThe purpose, as described in the original report, is to function as an attribution marker. By stamping every AI Overview and AI Mode link with a recognizable tag, a publisher can filter analytics for that parameter and isolate the traffic arriving from Google’s generative surfaces, rather than mixing it in with regular web results.<\/p>\n
What it looks like in practice<\/h2>\n
A link that would normally resolve to a destination article, for example https:\/\/example.com\/article<\/code>, would instead resolve to something like https:\/\/example.com\/article?st_source=ai_overview<\/code> when reached through an AI-driven result. The same pattern was reported inside AI Mode, where the generative answer links to outside sources.<\/p>\nScreenshots from the person who first noticed the change showed the tag in several different result layouts, not just the inline citations inside an AI Overview. The parameter appeared even in the “links mentioned in the source” list, which is the secondary reference block AI Mode displays beneath its answer.<\/p>\n
Could this be replicated?<\/h2>\n
Attempts to reproduce the same behavior across several browsers did not surface the parameter on identical queries. The discrepancy suggests the test is limited to specific users, sessions, or regions, which is a common pattern for Google’s search experiments. Google’s standard practice is to A\/B test new link structures against a slice of traffic before deciding on a full launch, so a partial rollout is consistent with normal product experimentation.<\/p>\n
What this means for site owners and analytics<\/h2>\n
If the parameter ships broadly, the practical benefit is a clean line in analytics between a click that originated inside an AI Overview and one that originated in the traditional blue-link results. Right now, those visits are difficult to separate because both arrive as Google Search referrals and look the same in log-level data.<\/p>\n
With a stable parameter, a publisher can build a segment in Google Analytics, a filter in a server log, or a dedicated dashboard tile for st_source=ai_overview<\/code>. That makes it possible to track click-through rate, conversion behavior, and revenue specifically tied to Google’s AI surfaces, rather than estimating the share of traffic that comes from AI Overviews through indirect inference.<\/p>\nIt also gives SEO teams a direct measurement of how visible a site is inside AI Overviews, which has become a meaningful secondary visibility signal alongside classic organic ranking. Knowing the click count, the query distribution, and the landing pages that AI citations send traffic to would let a site tune content for the prompts that AI Overviews answers most frequently in its niche.<\/p>\n
AI visibility tracking tools that monitor citation frequency in generative results are a related way to keep tabs on this, and a comprehensive website audit will show how the analytics setup is configured to capture parameters like this when they ship.<\/p>\n
Why Google would add it<\/h2>\n
Attribution inside AI results is a known gap for both Google and the publishers it cites. Without a tag on the link, an AI Overview click looks identical to any other referrer from the same domain, and there is no built-in way to count those visits. A parameter solves that without changing the visible layout of the AI Overview or the way the link itself is rendered to the user.<\/p>\n
For publishers, that clarity turns into a planning input: which topics are pulling citations in AI Overviews, which pages are receiving the resulting clicks, and how that traffic compares to the impressions already visible in Google Search Console. None of that is possible to read today without manual tagging or third-party estimation.<\/p>\n
FAQ<\/h2>\nWhat is the ?st_source=ai_overview<\/code> parameter?<\/h3>\nIt is a query parameter appended to the end of URLs that appear inside Google’s AI Overviews and AI Mode answers. The marker would let a publisher identify clicks that originated from Google’s AI-driven surfaces when reviewing analytics.<\/p>\n
Does this change anything for users searching on Google?<\/h3>\n
No visible change to the search page has been reported. The parameter sits at the end of the link URL, so a click still loads the destination page the same way it would without the tag.<\/p>\n
Can site owners see AI Overview traffic in analytics today?<\/h3>\n
Not through a dedicated channel. AI Overview clicks arrive as Google Search referrals with no marker, so they currently blend with regular organic clicks and have to be inferred from patterns rather than measured directly.<\/p>\n
Try the AI visibility report<\/h2>\n
![\"SEOScanPro,](\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\")
<\/a><\/p>\nThe AI visibility report runs a full technical audit of a site and shows the measured result behind every check. Open the AI visibility report<\/a>.<\/p>\n
![\"SEOScanPro,](\"https:\/\/seoscanpro.ai\/shots\/og-home.jpg\")
<\/a><\/p>\n