# AI Overview tracking: how to see where Google shows your pages

> Every way to track whether your pages appear in Google AI Overviews and AI Mode: what Search Console, rank trackers, analytics and logs show, and what each one misses.

Updated 2026-11-07 · Technical SEO · HTML version: https://getreport.app/guides/ai-overview-tracking

AI Overview tracking works by combining sources, because no single one sees everything: Search Console's Generative AI report counts how often Google showed your pages in AI Overviews and AI Mode, SERP trackers and manual checks show which of your chosen queries cite you, and your analytics and logs see the resulting visits only as ordinary Google traffic. This page belongs to our [guide to Google AI Mode and AI search](https://getreport.app/guides/google-ai-mode); if you want to be cited more often rather than measure it, read [how to rank in AI Overviews](https://getreport.app/guides/google-ai-overviews-seo) first. Below: the limits of each method, a weekly routine, and a test on our fixture log showing what a Google click leaves behind.

![The path from Googlebot's crawl to a visit, with the tracking method that sees each step: logs see Googlebot, Search Console counts AI impressions, trackers sample queries, and the click arrives as a plain google.com referral](https://getreport.app/guides/img/ai-overview-tracking/diagram.svg "Every method sees one step of the path. None sees all of it.")

## Quick answer

- **Search Console's Generative AI report** (Performance → Generative AI) is the only source of real counts: impressions of your links in AI Overviews and AI Mode, by page, country, device and date. It shows no queries and no clicks.
- **Clicks from AI features are in the regular Performance report**, inside the Web search type totals, with no filter to split them from blue-link clicks.
- **SERP trackers and manual checks** show whether a query's AI Overview cites you, only for the queries, places and moments they sample.
- **Analytics cannot single out AI Overview visits.** They arrive with the referrer `https://www.google.com/` and count as Google organic.
- **Server logs show no AI Overview crawler**, because there is none: Google uses Googlebot, and Google-Extended is a robots.txt token that never appears in a log.
- **Track weekly** in one sheet: Google's counts next to your samples.

## What can you actually track about AI Overviews?

Three questions sit behind "am I in AI Overviews?", each needing a different tool:

1. **How often does Google show my pages in AI features?** Only Google knows; Search Console tells you, per page.
2. **For which questions am I cited, and who is cited instead?** Google does not say; you ask the questions yourself, by hand or with a tracker.
3. **Do those appearances send visitors?** Analytics see the visits but cannot tell an AI Overview click from a blue-link click.

The diagram shows why: Google crawls with the same Googlebot, picks from the same index, and the person who clicks arrives through the same google.com door as everyone else. Only the step Google counts for you carries an AI label.

## What does Search Console show for AI Overviews and AI Mode?

**The Generative AI performance report.** Google announced it on its Search Central blog in June 2026, and its help page says it reached all websites worldwide by 31 August 2026. It counts impressions: how many times a link to your site appeared in AI Overviews or AI Mode. You can break that down by page, country, device and date. It has no queries, no clicks, no click-through rate and no position. Search Labs experiments are excluded, Discover has its own report, and two of your URLs in one answer count as one impression in the chart total.

**The regular Performance report.** Google's documentation says impressions and clicks from AI Overviews and AI Mode are included in the overall Web search type. There is no search appearance filter for them. Google's help page on position adds one detail: an AI Overview occupies a single position, and every link inside it gets that position, so a citation at the top can lift a page's average position for that query.

Practical consequences:

- Do not add the two reports together. The Generative AI impressions are already inside the Web totals.
- Read the Generative AI report per page and per week. AI impressions rising while Web clicks stay flat means shown more, not clicked more.
- If the report is empty for a site with real Search traffic, check Settings → Search generative AI. An opted-out site gets no AI impressions; small sites may simply have too little data.
- Recent days can be preliminary, and Google logged a data issue for 13 to 17 August 2026 that it later fixed. Compare whole weeks.

Two checks guard the eligibility side, because a page that is not indexed cannot appear in any AI feature:

> **Check: The page can be indexed.** To appear in search, a page must return HTTP 200, carry no noindex directive and be allowed in robots.txt. If any of the three fails, the page is invisible to searchers.
>
> 1. Open the technical detail to see which condition fails, then fix that one; the individual findings above have the steps.
> 2. After the fix, request indexing in Google Search Console to speed things up.

> **Check: The page is not set to noindex.** A noindex directive tells Google to drop this page from search results. Unless that is intended, every visit from search is lost.
>
> 1. Remove noindex from the robots meta tag and from the X-Robots-Tag header, unless the page should stay out of search.
> 2. In WordPress, untick Settings → Reading → "Discourage search engines" and check the page's SEO plugin settings.

## How do you check an AI Overview by hand?

A manual check is the cheapest way to answer "does this query cite me today?", and the easiest to misread. Do it the same way every time:

1. **Use a private window, signed out of Google.** That removes most personalisation, but not location: Google still estimates it from your IP address.
2. **Fix the location and language.** The same query from Zagreb and from London can show different answers, or an AI Overview in only one. Record where you checked from.
3. **Check mobile and desktop separately** if both matter to you; Search Console splits by device for the same reason.
4. **Expand the answer.** Many AI Overviews hide part of the text and some sources behind "Show more". A source behind it still counts as cited.
5. **Write down what you saw immediately**: whether an AI Overview appeared, whether your page was linked, which URL, and which other sites were linked.

Expect volatility: an AI Overview can appear in the morning and be gone by noon, and the cited sources can change between two searches, because Google generates the answer per search. One check is an anecdote; the same check weekly is a trend. For AI Mode, ask the same question in the AI Mode tab and record only the first response, since follow-ups change it.

## What do third-party AI Overview trackers measure?

SERP trackers that record AI Overview presence run a fixed list of queries on a schedule, store the results page, and report whether an AI Overview appeared and which domains it linked. Many rank trackers offer it, and dedicated tools exist. They share the same limits:

- **They sample.** They see only the queries you give them, from the locations and devices you configure, at the moment they run. Check how often yours runs and whether it records AI Mode too.
- **They search as a stranger.** Trackers usually query from data-centre addresses with no signed-in user, set to a chosen country or city. Consistent, good for trends, but not what a signed-in customer sees.
- **They cannot see Google's numbers.** Their "visibility" scores come from their own sample, often weighted by estimated keyword volumes.
- **Some expand the answer, some do not.** If citations behind "Show more" are not captured, the tool undercounts.

A tracker is a sampling instrument: good at "did our citation on ten money queries vanish this week?", bad at "how visible are we?". Read vendor market statistics as directional findings from that vendor's sample.

## Why do AI Overview clicks look like normal Google traffic?

As far as your site can tell, they are normal Google traffic. When someone clicks a link in an AI Overview or AI Mode, their browser requests your page with a `Referer` header of `https://www.google.com/` (the origin only, with no hint of which part of the page was clicked). Analytics report it as Google / organic.

The one visible difference is a text fragment. Links from AI Overviews often end in `#:~:text=`, which tells the browser to scroll to and highlight the quoted passage. That does not help your tracking either: fragments are never sent to the server, and the Scroll to Text Fragment specification has browsers remove the `:~:` directive from the URL before page scripts run, so analytics scripts do not see it. A tag manager variable reading `location.hash` should therefore record nothing in browsers that follow the specification.

GA4 now has its own channel for AI assistants: in May 2026 Google announced an AI Assistant channel in the default channel group, which groups visits referred by assistants such as ChatGPT, Gemini and Claude. Google's own AI features are not in it, because their clicks come from google.com. Our [AI referral tracking](https://getreport.app/tools/ai-referral-tracking) tool builds a custom channel for the assistants you choose; the same limit applies.

> **Free tool:** [AI referral tracking for GA4: a ready channel group](https://getreport.app/tools/ai-referral-tracking): Free AI referral tracking for GA4: a channel group regex for ChatGPT, Perplexity, Claude, Gemini and Copilot visits, plus Looker Studio formulas to copy.

What analytics can still tell you: did Google organic sessions or conversions change on the pages whose AI impressions rose? Correlation, not attribution, but the best available.

## What do server logs show for AI Overviews?

Less than people hope. There is no separate Google crawler for AI Overviews or AI Mode: they are built from the Search index, which Googlebot fills. Google-Extended is a robots.txt product token, not a user agent; Google says it has no separate HTTP user agent string and crawling uses existing Google user agents. You will never find it in a log.

Google-Agent, added to Google's user-triggered fetchers in March 2026, identifies Google-hosted AI agents browsing for a user. It tells you an agent opened your page, not that an AI Overview cited it.

A log shows two useful things: that real Googlebot keeps fetching the pages you want cited, and the shape of the clicks from google.com. [Detecting AI crawlers in your server logs](https://getreport.app/guides/detect-ai-crawlers-in-server-logs) covers the other operators, whose bots do carry their own names.

### The test: what a Google click leaves in a log

We ran this on our fixture of the example-shop.hr shop, served locally at `localhost:4101`. First, a request shaped like a click from an AI Overview, with Google's referrer and a text fragment:

```bash
# Terminal: request a page as a Google click would, with a text fragment
curl -sv -o /dev/null -e "https://www.google.com/" \
  "http://localhost:4101/shipping/#:~:text=Delivery%20to%20Croatia" 2>&1 | grep '^> '
```

```
> GET /shipping/ HTTP/1.1
> Host: localhost:4101
> User-Agent: curl/8.5.0
> Accept: */*
> Referer: https://www.google.com/
```

The fragment never leaves the client: the server receives `GET /shipping/` and a referrer of `https://www.google.com/`. Browsers behave the same way.

Then we queried the fixture access log (`fixtures/logs/access.log`, 3,000 synthetic lines in nginx combined format covering 1 to 14 September 2026, written to mirror a small shop's real log):

```bash
# 1. Every referrer value from Google
awk -F'"' '$4 ~ /google\./ {print $4}' access.log | sort | uniq -c

# 2. Google user agents in the log, including the ones people search for
grep -oE 'Googlebot-Image|Googlebot/2\.1|Google-Extended|Google-Agent|GoogleOther' access.log | sort | uniq -c

# 3. Where the "Googlebot" requests came from (first two octets)
grep 'Googlebot/2\.1' access.log | awk '{split($1, a, "."); print a[1] "." a[2] ".*"}' | sort | uniq -c
```

```
    306 https://www.google.com/

    137 Googlebot-Image
    640 Googlebot/2.1

     57 185.220.*
    583 66.249.*
```

All 306 requests from Google carry the identical referrer, 245 of them for pages and the rest for scripts and images those pages loaded. Nothing tells an AI Overview click from a blue link or an image result. Google-Extended and Google-Agent return zero, as Google-Extended will on any log. And 57 "Googlebot" requests come from an address range that is not Google's: borrowed names, which you confirm with the reverse DNS check in [how to verify Googlebot](https://getreport.app/guides/verify-googlebot-fake-googlebot). Our [log analyser](https://getreport.app/tools/log-analyser) does the same counting in your browser without uploading the file:

> **Free tool:** [Log file analysis for SEO: free log analyzer](https://getreport.app/tools/log-analyser): Free log file analysis for SEO in your browser: see what Googlebot and AI crawlers fetch, the 404s they hit and which bots are fake. Nothing is uploaded.

Behind a CDN such as Cloudflare, your origin log may show the CDN's addresses; use the CDN's logs or the forwarded IP header instead.

## Which tracking method should you use?

| Method | What it shows | What it misses | Cost | Effort |
| --- | --- | --- | --- | --- |
| Search Console Generative AI report | Impressions in AI Overviews and AI Mode, by page, country, device, date | Queries, clicks, CTR, position, competitors | Free | Low: read weekly |
| Search Console Performance report (Web) | Clicks and impressions including AI features | Any split between AI features and blue links | Free | Low |
| Manual checks | Whether a query shows an AI Overview and cites you, right now, from one place | Every other query, location, device and moment | Free | High per query |
| SERP and AI Overview trackers | Presence and cited domains for your query list, on a schedule, over time | Google's real counts, signed-in results, queries not on the list | Paid, usually by keyword count | Medium: set up once |
| Analytics (GA4 or similar) | Google organic visits and what they do on your site | Which visits came from an AI feature | Free | Low |
| Server logs | Googlebot fetching the pages, Google referrer clicks, fake bots | Any AI Overview signal: there is none to log | Free | Medium |

For most sites, Search Console plus a short manual list is enough. Add a tracker when you need daily history on more than about 20 commercial queries, or competitors' citations at scale.

## A weekly AI Overview tracking routine

Fifteen to thirty minutes, same day each week:

1. **Search Console, Generative AI report.** Last 7 days against the previous period; copy the 20 pages with the biggest change.
2. **Search Console, Performance report.** Copy Web clicks for the same pages and dates.
3. **Manual or tracker check.** Check the two or three queries each page should answer, the same way every week, and record presence, your citation and who else is cited.
4. **Analytics.** Note Google organic sessions and conversions for the pages that moved.
5. **Eligibility.** For any page that dropped out entirely, confirm it is still indexed and has no `noindex` or `nosnippet`, then look at the content.

A sheet layout that keeps weeks comparable (illustrative rows, using our fixture shop's pages):

| Week | Page | Query checked | Location, device | AI Overview shown | Cited (URL) | Others cited | AI Mode cited | GSC AI impressions (7 days) | GSC Web clicks (7 days) | Notes |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 2026-W45 | /shipping/ | delivery times to Croatia | Croatia, mobile | Yes | Yes | 2 | No | 410 | 37 | Quotes table |
| 2026-W45 | /care/ | waterproof leather boots | Croatia, desktop | No | n/a | n/a | Yes | 160 | 9 | AI Mode only |

One row per page, query and check; never overwrite a week. After four to six weeks you have Google's counts per page next to your own observations per query.

## How to check that a page can appear at all

Before you track a page, make sure it can appear: indexed (URL Inspection, or [our fix page on indexability](https://getreport.app/learn/indexability)) and with nothing blocking snippets. The AI crawler check shows what your robots.txt says to Google-Extended and other AI tokens, and whether your text needs JavaScript:

> **Free tool:** [AI crawlers check: GPTBot, ClaudeBot and llms.txt](https://getreport.app/tools/ai-crawler-check): See what your robots.txt tells 18 AI crawlers, such as GPTBot, ClaudeBot and PerplexityBot, whether your llms.txt is valid and what needs JavaScript. Free.

**What passing looks like:** URL Inspection says the URL is on Google, the indexable check passes, no `nosnippet` or `max-snippet:0` appears in the HTML or the `X-Robots-Tag` header, and the Search generative AI setting in Search Console is not set to opt out. Then a zero in the Generative AI report means "not chosen yet". The [AI crawlers fix page](https://getreport.app/learn/ai-crawlers) explains each robots.txt group.

## How we tested

Tested by the getReport team on 16 October 2026. We ran curl 8.5.0 against our local fixture of the example-shop.hr shop (served at `localhost:4101`, not the live site) to confirm what a request with Google's referrer and a text fragment sends, and ran the awk and grep queries above on `fixtures/logs/access.log`, a synthetic 3,000-line log we keep for tests. Search Console's reports are described from Google's help pages and blog as of October 2026, not from a real property. We did not test any paid SERP tracker, did not query Google for AI Overviews programmatically, did not test text fragment handling in each browser, and did not verify the GA4 AI Assistant channel inside a live property.

## Questions people ask

### How do I track AI Overviews for my keywords?

Use two sources together. Search Console's Generative AI report gives Google's impression counts per page, but not per keyword. For keywords, check each query by hand in a signed-out private window from a fixed location, or use a SERP tracker that records AI Overview presence and cited domains on a schedule. Record both weekly in one sheet so page-level counts sit next to query-level observations.

### Does Search Console show clicks from AI Overviews?

Yes, but not separately. Google counts clicks from AI Overviews and AI Mode in the Web search type of the regular Performance report, together with blue-link clicks, and offers no filter to split them. The Generative AI report shows impressions only. To estimate the effect, compare Web clicks for pages whose AI impressions rose against the weeks before.

### Can I see which queries trigger an AI Overview citing my site?

Not in Search Console. As of October 2026 the Generative AI report shows pages, countries, devices and dates, but no queries. To find queries, test the questions each page answers by hand or with a tracker that records cited domains. Bing Webmaster Tools offers grounding queries for Copilot answers, which can hint at topics but not at Google's.

### Why does the AI Overview change every time I search?

Google generates the answer for each search instead of storing it, so the wording and the linked sources can differ between two searches minutes apart. Location, language, device and signed-in history change it further. That is why one check proves little: repeat the same check, the same way, on a schedule, and read the trend.

### Can GA4 separate AI Overview visits from other organic search?

No, not on its own. A click from an AI Overview or AI Mode arrives with the referrer https://www.google.com/ and is reported as Google organic, the same as any search click. The highlight fragment some links carry is removed before analytics scripts run. Compare organic sessions on pages whose AI impressions changed in Search Console instead.

### Does Google-Extended show up in server logs?

No. Google-Extended is a token you use in robots.txt to control whether Gemini models can use your content for training and grounding. Google says it has no separate user agent; pages are fetched by existing Google crawlers. Seeing no Google-Extended requests is normal, and blocking it does not remove you from AI Overviews.

### Is there a free AI Overviews tracker?

Search Console's Generative AI report is the free official one, and it is the only source of real impression counts. Manual checks in a private window cost only time. Paid SERP trackers add scheduled checks across many queries and locations. getReport does not track AI Overview appearances; its free tools check whether your pages can be crawled and cited.

## Sources

- [AI features and your website](https://developers.google.com/search/docs/appearance/ai-features), Google Search Central (accessed October 2026)
- [Introducing Search Generative AI performance reports in Search Console](https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports), Google Search Central Blog (June 2026)
- [Generative AI performance report (Search)](https://support.google.com/webmasters/answer/16984139?hl=en), Search Console Help (accessed October 2026)
- [What are impressions, position, and clicks?](https://support.google.com/webmasters/answer/7042828?hl=en), Search Console Help (accessed October 2026)
- [List of Google's common crawlers](https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers), Google for Developers (accessed October 2026)
- [Search generative AI control](https://support.google.com/webmasters/answer/16908024), Search Console Help (accessed October 2026)
- [Scroll to Text Fragment](https://wicg.github.io/scroll-to-text-fragment/), WICG draft specification (accessed October 2026)