Measurement

How to Track AI Overviews in 2026: Free Checks, Trackers Compared, and the Four-Layer Measurement Stack

· · 26 min read · Updated 23 October 2026

To track AI Overviews, start with Google’s own generative AI performance report in Search Console for impressions, add a citation check (by hand for a small keyword set, or with an AI Overviews tracker once you need trends), and treat every click figure as an estimate. No single source covers presence, citation and clicks together.

Almost every guide on this topic opens with the same claim: Google tells you nothing, so buy a tool. That claim expired in 2026. Google shipped a dedicated generative AI performance report inside Search Console, and its documentation now states that as of 31 August 2026 the insights have rolled out to all websites worldwide.

It does not solve the problem. It reports impressions and withholds clicks, which means the hardest question (what has this cost me?) still has to be inferred. But it changes where you start, and it changes what you should be paying for.

For what that inference is actually worth, the six-site study behind this guide prices one impression against 24.5 million of them: a blended 0.86% click-through rate, and 37 queries at a top-ten average position that returned no clicks at all.

This guide covers the free ways to check AI Overviews, a comparison of the trackers that currently rank for the job, the four-layer measurement stack rebuilt around what Google now reports, and a sampling method that decides how much any of those numbers can be trusted. If you need the basics first, start with what AI Overviews are and how they choose sources.

Key takeaways

  • Google’s Search Console generative AI performance report covers AI Overviews and AI Mode, but reports impressions only, with no click data at all. There is no AI Overview value in the Performance report’s Search appearance filter, so do not go looking for one.
  • Ranking first does not mean being cited. Each overview draws on several sources, so rank and citation are separate signals that need separate tracking.
  • Free checkers from Ahrefs, Semrush, SE Ranking and Seobility each answer a narrower question than their names suggest. Know whether a tool counts keywords or prompts, and mentions or citations, before you compare its numbers with anything.
  • Citations are volatile: 45.5% of the sources cited in an AI Overview are entirely new between observations, per Ahrefs’ volatility study. A tracker is only as good as the sample it runs, so fix the keyword panel, the location and the cadence before you read a trend.
  • Click impact cannot be measured, only estimated. A regex proxy in Search Console gets close enough to report, provided you label it as an estimate.

What “tracking AI Overviews” actually means

“Tracking AI Overviews” collapses four separate measurements into one phrase, and most of the confusion in this topic comes from not naming them apart.

Presence. Does an AI Overview appear for this query at all? This is a property of the SERP, not of your site.

Your citation. When one appears, is your URL among the sources? This is the measurement people assume rank tracking already covers. It does not.

Competitor citation. Who is cited when you are not? This is where content gaps become visible.

Click impact. What has the overview cost you in clicks on queries where you rank well? This is the number leadership asks for, and the only one no tool can measure directly.

The gap between the first two is the point. Keyword.com’s analysis of 5.46 million AI Overviews found that even the #1 organic result was cited inside the overview only about 40% of the time, because each overview typically draws from roughly 5.5 sources rather than the top of the page. Rank and citation are correlated but distinct.

Rank still matters, though, and heavily. In that same dataset, citation rate fell from 36.8% for pages ranked 1–3 to 21.5% for 4–10, 9.4% for 11–20, and 1.7% for 51–100. Top-three pages were cited roughly 22 times more often than pages in the fifties. So rank is a strong prior on citation, and a poor substitute for measuring it.

Free ways to check AI Overviews

Before paying for an AI Overviews tracker, use the free checks. They answer most of the questions a small site has, and they tell you what a paid tool would need to add to be worth it.

A manual check, done properly

Manual checking is the most direct AI Overviews checker there is, and the one every tool is trying to automate. The protocol matters more than the effort. Keyword.com’s manual method is a sound baseline: an incognito window logged out of Google, a fixed location and language (the &gl= and &hl= URL parameters do this), SERP-altering extensions switched off, and the same time of day each week.

Log one row per check, never a summary. The columns I use:

ColumnExample valueWhy it is there
date2026-10-06Trends need dates, and dates need a fixed time zone
keywordwhat is crawl budgetThe panel must stay the same from week to week
run1A second run on the same day measures volatility
aio_presentYPresence, a property of the SERP
our_url_citedNYour citation, the number you actually care about
competitor_urlsexample.com/guideWho is cited instead of you
screenshotlinkEvidence when a number is questioned later

Twenty to twenty-five keywords is a reasonable start. The limits are cost and noise: Keyword.com puts a proper check at two to three minutes per keyword, and the answers change between runs, so a manual log is a diagnostic, not a monitoring system. The sampling section below says how many rows you need before the log can show a change.

Search Console: the generative AI report, not a search appearance filter

The first free check is already in your property. The generative AI performance report shows impressions from AI Overviews and AI Mode, grouped by pages, countries, devices and dates. Grouping by page gives you the list of URLs Google is willing to show in generative features, which is the closest free thing to a citation list.

What you will not find is an AI Overview option in the standard Performance report’s Search appearance dimension. Google’s list of Search appearance types covers features such as review snippets, videos, merchant listings and translated results, and AI Overviews is not among them. That matches Google Search Central’s statement that AI features are reported within the “Web” search type of the ordinary Performance report, mixed in with everything else.

Two filters in the standard report are still useful for AI Overview work. The branded and non-branded queries filter separates searches that include your brand name, which is the first thing to strip out before you look for AI Overview-shaped queries. And the query filter accepts regular expressions, which is how Layer 2 below builds its click-impact proxy. If you would rather pull these rows programmatically, the Search Console API guide covers the setup.

Free AI Overviews checkers from SEO tools

Four of the tools ranking for “AI Overviews checker” have a free entry point. Each one answers a narrower question than the name suggests, so read what the free version actually returns.

  • Ahrefs’ free AI Overviews tracker needs no sign-up and returns a limited preview from Ahrefs’ Brand Radar index: how many AI Overviews mention your brand across the keywords and prompts Ahrefs tested, mentions over time, and your top five topics, cited domains and cited pages. It measures your brand against Ahrefs’ query set, not your own keyword list.
  • Semrush’s free AI visibility checker can be run three times a day without registering, and covers ChatGPT, Gemini, AI Mode and AI Overviews together. Semrush’s dedicated AI Overviews visibility checker returns a visibility score, mentions, cited pages and competitor gaps, but its check button routes through a Semrush sign-up.
  • SE Ranking’s AI Overviews tracker page lets you check five keywords for free, choosing desktop or mobile, country, location and language, and shows the overview’s sources for a keyword you supply. It is the closest free equivalent of a manual check with the location pinned.
  • Seobility’s AI Overview tracker is part of its ranking monitoring. On the free Basic plan you only see whether an AI Overview appears for your monitored keywords; the full answer text, cited sources and their order need a Premium plan.

These are fine for a first look. None of them gives you a stable, repeatable sample of your own keywords at a cadence you control, which is what a trend needs.

The site’s own tools, and what they do not do

The AEO Article Analyzer on this site is free for three analyses a month. It is not a tracker. It scores an article against the structural patterns answer engines tend to quote, which makes it the check you run after tracking has told you a page is shown but not cited. Use trackers to find the gap and the analyzer to diagnose the page.

Bing’s free citation data

One free source deserves more attention than it gets. Microsoft’s Bing Webmaster Tools announcement introduced AI Performance in February 2026 as a public preview, showing when your site is cited in AI-generated answers across Microsoft Copilot, Bing’s AI summaries and select partner integrations, including which URLs are referenced and how citation activity changes over time. That is citation-level data Google does not give you, for free, on a different but overlapping surface.

AI Overviews trackers compared

Once you need trend data across more than a couple of dozen keywords, or competitor citation share becomes a reporting line, an AI Overviews tracker earns its cost. The table below compares the tools that currently rank for “AI Overviews tracker” and “AI Overviews tracking”, on the features each vendor documents on its own page, read in September 2026. I have left prices out deliberately: several of these pages quote different figures in different places, and the AI visibility tools guide keeps dated pricing for the wider category.

ToolFree optionWhat it tracks for AI OverviewsUnit of measurementBest fit
Ahrefs Brand RadarFree preview, no sign-upDaily mentions and citations, competitor share of voice, prompts rivals win that you do not, custom promptsAhrefs’ keyword index and prompt index, plus your own promptsBrand-level visibility against a large pre-built query set
Semrush AI Visibility ToolkitFree checker (limited daily runs)Visibility score, mentions, cited pages, AI Overview text per query, competitor opportunitiesSemrush’s prompt and query databaseTeams already running Semrush who want AI Overviews next to other engines
SE RankingFive keywords freeAI Overview presence, your position in it, other cited sources, cached SERP copies, day-by-day changes, API and MCP accessYour own tracked keywords, by country and languageKeyword-level tracking with the location pinned
SeobilityBasic plan shows presence onlyPresence, full answer text, cited URLs and their order, whether you are cited and at which position, next to classic rankingsYour own monitored keywords, updated daily on PremiumSmall sites that want presence and citation inside a rank tracker
Keyword.com14-day trialAI Overview flag in rank tracking, cited URL per keyword, top five cited pages and their share, brand mentionsYour own tracked keywordsAgencies reporting AI Overviews alongside rankings
Peec AINone on the checker sidePrompt-based visibility across several AI models, with the sources each answer citesPrompts you define, by countryMulti-engine brand visibility; see the review for Google coverage

The column that matters most is the unit of measurement. Keyword-based trackers (SE Ranking, Seobility, Keyword.com) answer “is my page cited for the queries I rank for?”, which is the SEO question. Prompt- and index-based tools (Brand Radar, Semrush’s toolkit, Peec AI) answer “how visible is my brand across a large set of questions?”, which is the brand question. Their numbers are not interchangeable, and a visibility score from one cannot be compared with a citation rate from another.

Three questions settle most tool choices. Can you load your own keyword list and pin country, language and device? Does it store the raw answer and the cited URLs, or only a score? And can you export the rows? If the answer to the last one is no, you cannot audit the number, and you cannot join it with Search Console. If you want to build the collection yourself instead, a SERP API that returns the AI Overview block does the fetching (see the SEO APIs comparison), and the Ahrefs API to Google Sheets setup shows the spreadsheet plumbing for pulling API data on a schedule.

The four-layer stack at a glance

Checkers and trackers answer the citation question. The full measurement stack has four layers, each answering a different question with a stated accuracy limit.

LayerAnswersCannot tell youSetup cost
1. GSC generative AI reportHow often your links appeared in AI Overviews and AI Mode, by page, country, device and dateClicks, CTR, which query, whether you were cited or merely surfacedMinutes
2. GSC regex proxyEstimated click impact on AI-Overview-shaped queriesConfirmation that an overview actually fired for a given queryAn hour, repeatable monthly
3. GA4 + GTM text fragmentsSession-level evidence that specific pages received AI Overview clicksComplete coverage, and it bundles Featured Snippet and PAA clicks inHalf a day of GTM work
4. Third-party citation trackingWhich URLs are cited, and who is cited instead of youAnything about clicks or revenueOngoing subscription or a disciplined manual log
The four-layer AI Overviews measurement stack: layer 1 the GSC generative AI report, layer 2 a GSC regex proxy, layer 3 GA4 plus GTM text fragments, and layer 4 third-party citation tracking, each labelled with the question it answers and its setup cost.
Each layer answers a different question, at a different cost, and no single layer is sufficient on its own.

Two rules hold across all four. First, trends beat snapshots: AI Overviews have a 70% chance of changing from one observation to the next, per Ahrefs’ study of 43,000 keywords. Second, no layer is a substitute for another. Anyone selling you one as the complete picture is selling you a subscription, not a measurement.

Stat card: AI Overviews have a 70% chance of changing between observations, per Ahrefs' November 2025 study of 43,000 keywords.

Layer 1: The Search Console generative AI report

Start here, because it is free, first-party, and most published guides predate it.

What the report gives you

The report covers both AI Overviews and AI Mode. According to Google’s Search Console documentation, impressions are counted as how many times links to your site were shown to a user in a generative AI feature on Google Search. Two results from the same site inside one feature count as a single impression at property level.

You get the report’s four grouping options: Pages, Countries, Devices and Dates, plus a search type filter that splits text-based from multimodal web searches. That is genuinely useful. Grouping by page tells you which URLs Google is willing to surface in generative features.

What it deliberately withholds

Clicks. There is no click column, no CTR, and no queries dimension in those four groupings. You can see that a page appeared; you cannot see whether anyone came, or what they searched.

That is not an oversight to work around later. It is the shape of the data, and it dictates the rest of the stack. It also means the report cannot be read like a standard performance report. An impressions line that rises while organic clicks stay flat is the expected pattern here, not an anomaly, and it is the same dynamic behind zero-click searches generally.

Note also that the standard Performance report has not changed. Google Search Central states that AI Overviews and AI Mode are reported within the “Web” search type, so AI-driven clicks have always been mixed into your organic numbers, and still are.

If you don’t see the report

Google’s documentation says the report is now available to all websites, but it also lists two reasons a property may not show it: the rollout reaching properties over time, and a site that has not received enough impressions in generative AI features. The second is the common one for small or new sites. If it is missing, check again next month and move to Layer 2, which you need regardless, because Layer 1 has no click data.

Layer 2: The regex proxy for click impact

Because no Google surface reports AI Overview clicks, click impact has to be inferred from query shape. The method is crude and defensible, in that order. For a statistical estimate of the click impact, with position-matched control queries and a confidence interval, see quantifying AI Overview CTR impact.

The query filter

Build a query filter in Search Console that isolates the queries an AI Overview is likely to have fired on. Three conditions, applied together:

  • Include informational queries. A “matches regex” filter on question starters and explainer modifiers: ^what |^how |^why |^when |^where |^who |^which | guide|tutorial|definition|examples?|vs\.?|versus| best way|difference between|meaning of. This is the highest-yield condition, because Ahrefs’ analysis of 150,000 AI Overview keywords found 99.2% of AI Overview keywords are informational in intent.
  • Include long conversational queries. A second pass with ^(?:\S+\s+){9,}\S+$ catches queries of ten words or more, which read like prompts rather than keywords.
  • Exclude branded and commercial terms. Use the non-branded query filter where your property has it, or a “doesn’t match regex” filter on your brand and product names, plus one on commercial modifiers such as price|pricing|cost|cheap|buy|discount|coupon|review.

Then set a date comparison across a rollout or a period you care about, export both ranges, and compare CTR at the query level.

How much accuracy do you give up by guessing? Less than you would expect. In Ahrefs’ own before-and-after test, regex-guessed AI Overview keywords showed a CTR drop of 3.76 percentage points, a 42% relative decline, against 3.98 points and 44% for confirmed AI Overview keywords, a relative difference of about 2%. The proxy is close enough to report, provided you label it a proxy.

For scale context, Ahrefs’ 300,000-keyword CTR study found the presence of an AI Overview correlated with a 34.5% lower average clickthrough rate for the top-ranking page, comparing March 2024 with March 2025. That is a correlation across a large sample, not a measured loss on your site: useful as a benchmark, not as a forecast.

Reading stable rank with falling CTR

The pattern worth building a standing alert on is a query where average position holds, impressions hold or rise, and CTR falls. That combination points at the SERP rather than at your page.

It matters because it changes the response. A ranking loss calls for content and link work; an on-SERP answer absorbing the click does not. Diagnose it wrong and you spend a quarter rewriting pages that were never broken.

Layer 3: GA4 and GTM text fragments, the only click-level signal

This is the one method that identifies individual sessions as AI Overview arrivals. It is also the fiddliest, and the one where implementation quality decides whether the data is worth anything.

When Google deep-links from an AI Overview to a cited passage, it often appends a text fragment to the URL: #:~:text=. That fragment is your signal.

You cannot catch it with a URL filter. As Ahrefs’ walkthrough of the fragment method sets out, GA4 cannot see #:~:text= strings because they are resolved client-side, so isolating those sessions requires Google Tag Manager: a custom JavaScript variable that reads the fragment from document.location.hash, passed into GA4 as an event parameter, then registered as a custom dimension so it becomes reportable.

Four steps, in order:

  1. Custom JavaScript variable in GTM that returns the decoded fragment text, or undefined when absent.
  2. Trigger on page view where that variable is defined.
  3. GA4 event, named something unambiguous like serp_fragment_arrival, passing the fragment text and page path as event parameters.
  4. Register the parameters as custom dimensions in GA4 Admin. Skip this and the data is collected but not queryable, which is the most common way this implementation quietly fails.

Then two limits you have to state whenever you report the number.

Coverage is partial: not every AI Overview link carries a fragment, so this is a sample, not a census. And the fragment is not exclusive to AI Overviews. Ahrefs’ caveat on the method notes that text-fragment URLs also appear when users navigate from Featured Snippets and People Also Ask boxes, so those clicks land in the same bucket.

The honest framing for a client report is “sessions arriving from an on-SERP answer feature”, not “AI Overview clicks”. It is the same discipline that makes full-funnel tracking trustworthy: name what the number measures, not what you wish it measured.

Layer 4: Citation tracking, and when you actually need it

Two questions remain that no Google surface answers: which of your URLs is cited inside the overview text, and who is cited when you are not. The free checks and trackers above are the tools for this layer.

The surface is volatile. In the Ahrefs volatility study above, only 54.5% of cited URLs overlapped on average between consecutive responses. A citation you record on Monday tells you little about Tuesday. This is also why citations you have already won need re-checking rather than filing; AI citation decay is a live risk, not a one-off audit finding.

And manual effort scales badly. Keyword.com’s cost estimate puts a proper manual check at two to three minutes per keyword, which makes 100 keywords a 15-hour weekly commitment. At that point a subscription is cheaper than the analyst.

So the decision rule comes down to scale. Track manually while you are validating a hypothesis on a small keyword set. Pay for automation once you need trend data across more than about 25 keywords, or once competitor citation share becomes a reporting line rather than a curiosity. The tool choice matters far less than whether you are tracking the same keyword set consistently, which is what the next section is about.

Once tracking tells you a page is present but never cited, the work moves from measurement to optimisation: clearer answers near the top of the page, structured formatting, and the schema and entity signals covered in structured data for AI search and how to rank in Google AI Overviews.

Methodology: sampling so the numbers mean something

Every AI Overviews tracker, paid or manual, is a sampling exercise. It runs a set of queries at some moments from some location and reports what it saw. Whether a month-on-month change is real depends on that sample far more than on the tool, and most dashboards do not show you the sample at all.

Fix the panel before the first check

The keyword panel. Choose it in advance and freeze it. Stratify it so one group cannot dominate: split by intent (informational, comparison, commercial) and by your current position band (1–3, 4–10, 11–20), because citation rates differ sharply by rank, as the Keyword.com figures above show. Add keywords in a new panel version rather than editing the old one.

Location, language and device. Pin all three. An overview in the UK on mobile is a different observation from one in the US on desktop, and pooling them hides both.

Repeats and cadence. Run each keyword at least twice per period, separated by an hour or more, so you have a measure of within-period variance. Weekly for volatile queries, monthly for stable ones, on the same day and time.

Scoring rules. Write down what counts as a citation before you score anything. Does a link to a different page on your domain count? Does a brand mention without a link? The answers are yours to choose, but they must not change between months.

The same logic, applied to brand mentions in ChatGPT and Gemini rather than Google’s overviews, is worked through in full in the AI share of voice methodology, including why prompts, not repeats, are the unit to grow.

How many checks before a change is real

Your citation rate is a proportion: citations divided by checks where an AI Overview appeared. Its uncertainty follows from the number of those checks. The table gives the width of the 95% Wilson interval at two citation rates, computed with the script below.

Checks with an AI OverviewInterval width at a 50% citation rateInterval width at a 20% citation rate
2040 points34 points
5027 points22 points
10019 points16 points
20014 points11 points
40010 points8 points

The practical reading: a 25-keyword panel checked once a month cannot show you a ten-point change in citation rate. It can show you which pages are never cited and which competitors keep appearing, and that is often the more useful output. If you need a trend line leadership can rely on, you need hundreds of checks per period, which is the real argument for a tracker.

A citation-rate calculation you can run on the log

This reads the manual log described earlier (or any tracker export with the same columns) and prints the monthly citation rate with its interval:

import csv
import math
import sys
from collections import defaultdict


def wilson(k, n, z=1.96):
    """95% Wilson score interval for k successes in n trials."""
    if n == 0:
        return (0.0, 0.0)
    p = k / n
    denom = 1 + z * z / n
    centre = (p + z * z / (2 * n)) / denom
    half = z * math.sqrt(p * (1 - p) / n + z * z / (4 * n * n)) / denom
    return (max(0.0, centre - half), min(1.0, centre + half))


# Log columns: date, keyword, run, aio_present (Y/N), our_url_cited (Y/N)
checks = defaultdict(lambda: [0, 0, 0])  # month -> [checks, aio, cited]
with open(sys.argv[1], newline="") as f:
    for row in csv.DictReader(f):
        month = row["date"][:7]
        c = checks[month]
        c[0] += 1
        if row["aio_present"] == "Y":
            c[1] += 1
            if row["our_url_cited"] == "Y":
                c[2] += 1

for month, (n, aio, cited) in sorted(checks.items()):
    lo, hi = wilson(cited, aio)
    rate = cited / aio if aio else 0.0
    print(f"{month}: AIO on {aio}/{n} checks; cited in {cited}/{aio} "
          f"= {rate:.0%} (95% CI {lo:.0%} to {hi:.0%})")

Run it as python3 cite_rate.py aio-log.csv. On a five-row test file it prints 2026-10: AIO on 4/5 checks; cited in 1/4 = 25% (95% CI 5% to 70%), which is the point: four observations tell you almost nothing, and the interval says so. Report the interval next to the rate every time.

Wiring the four layers into one report

Four layers in four interfaces is not a measurement system; it is four tabs nobody opens. The layers have to land in one view before anyone acts on them.

The pipeline I build for clients pulls the Search Console API for both the generative AI impressions series and the regex-filtered query set, GA4 for fragment-tagged sessions by landing page, and a CSV export from whichever citation tracker is in use, joined on URL into a single reporting layer. If you want the build detail, the Looker Studio SEO dashboard walkthrough covers the same plumbing.

Watch the row limits when you automate: the generative AI report inherits the same 1,000-row limit as the standard report, and dates are grouped in Pacific Time, which will shift your daily buckets if you report in European time.

Four numbers are worth putting in front of leadership. Generative AI impressions, trended. Citation rate on your tracked keyword panel, with its interval. The count of queries showing stable rank with falling CTR. Fragment-tagged sessions by landing page. Weekly scan, monthly baseline, quarterly review. Annotate the dates you changed anything, because without annotations you will be guessing at causation within two months.

What you can honestly claim from this data

This is the part that decides whether your reporting survives scrutiny, so be explicit about which numbers are measured and which are inferred.

Measured. Generative AI impressions, from Google’s own data. Fragment-tagged sessions, for the subset of clicks that carry a fragment.

Inferred. All click loss. Every click-impact number in this stack is an estimate derived from query shape and CTR movement. Report it as an estimate with the method named.

Sampled. Citation rate and citation share, on a volatile surface, from whatever panel and cadence your tracker runs at. Report the sample size with the number.

Two overclaims to avoid. Do not treat a single check as a trend: give it at least four weeks before you call a direction, and note that Google’s documentation for the report excludes Search Labs experiments and marks the newest data as preliminary, with values that can still change within hours. And do not convert inferred click loss into a revenue figure without labelling every assumption in the chain; the moment that number gets quoted back to you without its caveats, you own it.

AI Overviews are not AI referrals: measure them separately

These are two different measurements, and conflating them is the most common error in this area.

AI Overview visibility happens inside Google. It mostly produces no click, it is measured with the four layers above, and success looks like citation rate.

AI assistant referrals arrive from another domain (ChatGPT, Perplexity, Claude, Copilot), land in GA4 as referral traffic, and are measured with a custom channel group. Success there looks like sessions and conversion rate.

Different surfaces, different tooling, different success metrics. If you need the referral half, how to track AI referral traffic in GA4 covers that setup end to end. If you would rather have the whole stack built and wired into one report, that is part of full-funnel tracking.

Frequently asked questions

Can you track AI Overviews in Google Search Console?

Partly. Search Console has a generative AI performance report covering AI Overviews and AI Mode, grouped by pages, countries, devices and dates, and Google says it is now available to all websites. It reports impressions only, with no click, CTR or query data, and there is no AI Overview option in the standard report’s Search appearance filter.

What is the best free AI Overviews checker?

For your own keywords with the location pinned, SE Ranking’s free five-keyword check is the closest to a proper manual check. For a brand-level snapshot with no sign-up, Ahrefs’ free AI Overviews tracker returns mentions, cited domains and cited pages from its own query set. Neither replaces a fixed keyword panel checked on a schedule, which is what a trend needs.

Do I need a paid AI Overviews tracker?

Only for citation-level data at scale. Google reports whether your pages appeared, but not which URLs the overview cited or who was cited instead of you. Manual checking covers that for around 20 keywords; past roughly 25, and certainly once competitor citation share becomes a reporting line, automation is cheaper than analyst time.

How often do AI Overviews change?

Often enough that snapshots are misleading. Both the overview text and the sources it cites change between observations, as the volatility figures above show, with roughly half the cited URLs turning over from one response to the next. Track the same keyword panel on a fixed cadence and read trends over at least four weeks.

Can I see AI Overview clicks in GA4?

Not natively, and not with a URL filter. AI Overview clicks arrive as ordinary Google organic traffic. The workaround is to detect the #:~:text= fragment with a Google Tag Manager custom JavaScript variable and pass it to GA4 as an event parameter registered as a custom dimension, accepting that coverage is partial and that Featured Snippet and People Also Ask clicks get counted alongside.

How many keywords should I track to start?

Start with 20 to 25 informational, non-branded queries tied to pages that matter commercially, split across position bands. That is small enough to check manually while you learn what the data looks like, and large enough to show which pages are never cited. It is too small to detect a modest change in citation rate, so expand the panel before you report trends.