How to track AI Overviews

Why point-in-time tracking fails here

Conventional rank tracking works because rankings are comparatively stable: a position checked on Tuesday is usually a fair representation of that week. AI Overviews are not stable in that way. Whether one appears at all varies, and when it appears the source set varies too.

So a single check tells you whether an overview existed at that moment, which is a much weaker claim than it looks in a report. A series built from weekly single checks will show swings that are sampling noise and invite decisions based on them.

The three numbers worth tracking

Trigger rate

The share of your tracked queries that produce an overview at all, measured across the window rather than on one day. This is the size of the surface available to you, and it moves independently of anything you do.

Citation rate within triggered queries

Of the queries that do produce an overview, the share where you are cited. This is the number your work actually affects, and reporting it against all queries rather than triggered ones understates your performance.

Clicks on those queries

Tracked separately and expected to fall where you win. An overview answers the question on the results page. Being cited is brand exposure with modest traffic attached.

How to build the series

1. Fix a query set and hold it constant. Changing it mid-period starts a new series.
2. Check each query several times across a month rather than once, and report the rate across checks rather than a snapshot.
3. Record the cited sources every time, not just whether you were there. Source concentration is where the actionable finding usually is.
4. Segment by query type. Informational queries trigger overviews far more often than transactional ones, and blending them hides both signals.
5. Pull Search Console clicks and impressions for the same query set over the same window, so the traffic effect sits next to the citation effect.
6. Annotate model and surface changes when they happen, so a step change has an explanation attached rather than a theory.

Reading the traffic impact honestly

The pattern to expect on queries where you start being cited is impressions flat or up, clicks flat or down, and position unchanged. That combination reads like a failure in a conventional SEO report and is not one.

The corresponding pattern where an overview appears and you are not cited is impressions up, clicks down, position unchanged. That is a real loss, and it is worth separating from the first case, because the two look almost identical in Search Console.

The only way to tell them apart is to know whether you were cited, which is why the tracking above exists. How to show up in AI Overviews covers what to do about the second case.

Frequently asked questions

Does Search Console report AI Overview data?

Not separately. Overview impressions and clicks are folded into the standard Search performance report, which is why you need external tracking to know whether an overview appeared and whether you were in it. See how to monitor AI search visibility for the wider method.

How many queries should we track?

Enough that a few queries flipping does not move the rate. Under about thirty, week-to-week variance dominates. A hundred is comfortable for most SaaS categories.

Sources

1. Google Search Console, performance report documentation. What Search Console does and does not separate out.