A landing page can gain clicks in Google Search Console while its organic sessions stay flat in Google Analytics. Before changing the page or crediting an AI feature, trace how a visit gets from a search result into your report.
On November 12, 2026, Google Search Central added a guide to identifying Search traffic by the HTTP Referer header. The release was a documentation update. It gives analysts a way to inspect the source information their sites receive and explains why analytics totals can differ from Search Console. Search Central documentation changelog
Find out what the referrer can tell you
For a click from Search on the web, the header typically contains a Google origin such as https://www.google.com/ or a local Google domain. The Google app on Android can also send an Android app origin, depending on how it opens the link. The iOS app can send the same web origin as a browser.
The header omits the original search query and result URL path. Google Images and Discover can share these referrer values, and some clients suppress the header entirely. A Google origin is evidence about where the request came from, with limited detail about the experience that sent it. Google's traffic identification guide
Compare one landing page across your reports
Pick a page with enough traffic to see a pattern and choose a date range with complete data in both tools. Write down the Search Console property, search type and page filter. In GA4, use the matching landing page and the organic Google session segment. When one tool reports a canonical URL and the other records a visited variant, document how you matched them.
| Evidence | What it helps you check |
|---|---|
| Search Console clicks for the page | Whether observed clicks from organic results changed |
| Landing-page requests in edge or server logs | Whether the site received page requests with a recognizable Google referrer |
| GA4 organic Google sessions for the page | Whether on-site tracking recorded and classified visits as expected |
A click and a session happen at different stages. Compare how the numbers move over time and investigate a sustained change in their relationship. Leave ad traffic out of the organic comparison. Google's guide to comparing Search Console and Google Analytics
AI already decides how your brand shows up.
Every prompt, citation, and recommendation is a signal. igeo.ai turns that behavior into clear answers and the next action, whether that’s a page to rewrite, a schema to add, or a story to publish.
Follow the request through a redirect
Suppose a service guide moved to a new URL last week. Search Console clicks look steady, and the new page receives requests, but its organic sessions fell. Open a real search result for the guide in a test browser and follow the document requests in the Network panel.
- Record the URL from the result and the final landing URL. Inspect each redirect and check the final HTTP response.
- Compare the first and final landing-page requests in your logs. If a client-side redirect substitutes your own page as the referrer, that points the investigation toward the redirect.
- If the final request still carries a recognizable Google referrer, check when the analytics tag runs and how the traffic gets classified. Compare the behavior under the consent choices your site offers.
- Note differences between mobile and desktop, and count document requests separately from requests for images, scripts and styles.
This example gives you two places to investigate. A lost referrer calls for inspecting the navigation path. A retained referrer alongside missing or reclassified sessions calls for inspecting on-page collection and reporting rules. Google's guide to referrers and redirects
Report AI visibility and visits using their own evidence
Google says that activity from AI Overviews and AI Mode contributes to the overall Web search type in Search Console. A Google web referrer supplies an origin, so assigning a session to either AI experience requires additional evidence. In a GEO report, keep the Google organic trend alongside documented citations from monitored answers and identifiable visits from AI assistants. Google's guidance on measuring AI features
For example, if a buyer guide appears as a citation in a monitored answer and also receives more Google organic sessions, report both observations with their dates and sources. When a referral is missing, leave its origin unknown. That makes the report easier to revisit as collection methods and search experiences change. For a broader reporting setup, see our guide to measuring AI search visibility.
igeo.ai AI Traffic Analytics brings identifiable AI referrals and crawler activity alongside connected GA4 and Search Console data. Bring one landing page and one reporting discrepancy to an igeo.ai demo to see how those signals can support your investigation.