AIO Delta

Guide

How to find the queries losing clicks to AI Overviews

2026-10-21

Knowing that "AI Overviews reduce clicks" doesn't help much on Monday morning. What helps is a list: these 30 queries lost clicks while your rankings held, sorted by how many clicks went missing. That list tells you which pages to look at first and which drops you can ignore.

Search Console can't produce that list directly. It counts AI Overview clicks inside the Web search type without separating them (Google). Its Generative AI performance report shows AI Overview and AI Mode impressions by page, but has no clicks and no query dimension (Google). So the job is to infer affected queries from the data you do have. Here's the method, then a shortcut.

The signal

For one query, compared across two periods of equal length, look for:

  1. Average position held or improved. A ranking loss explains a click loss by itself, so leave those queries out.
  2. Impressions held or rose. If impressions fell, demand or visibility changed instead.
  3. CTR fell, and clicks fell with it.

This matches the case Google describes in its traffic-drop guide: impressions stay the same while clicks drop, which points to something on the results page, such as another feature or a more appealing result (Google, Debugging drops). Search Console Help puts it as checking for "a drop in CTR without a matching drop in impressions" (Google, traffic drops).

The signal doesn't prove an AI Overview is the cause. It narrows thousands of queries down to a few dozen worth checking.

Step 1: Get both periods in one export

In Performance > Search results, use the date filter's Compare tab to set two equal periods, for example the last 28 days against the previous 28 (Google, filtering and comparison). Open the Queries tab, then use the export button to download the table (Google, Performance report). The export has clicks, impressions, CTR and position for both periods.

If you want the page behind each query, add a page filter and export again, or use the Search Analytics API, which can return query and page together.

Coverage limits: the interface table stops at 1,000 rows and doesn't include anonymized queries (Google, Google). On a large site, export by folder (filter pages by a URL prefix) or use bulk data export so the long tail isn't lost.

Step 2: Remove noise before you filter

  • Brand queries. Use Search Console's non-branded query filter if your property has it (Google), or remove brand terms with a regex.
  • Tiny queries. A query going from 3 clicks to 1 isn't a trend. Set a floor such as 100 impressions in the current period.
  • Known events. Remove queries tied to launches, outages, news spikes or seasonal peaks. If the drop lines up with last year's pattern, it's seasonality.

Step 3: Apply the test

Add columns for position change, impression change, CTR change and estimated missed clicks, then keep rows where:

  • position change ≤ +1 (no worse than about one place)
  • impression change ≥ 0
  • CTR change ≤ −20% relative, and clicks fell

These thresholds are a starting point, not an industry standard. Tighten them if you get too many rows and loosen them if you get none.

Estimated missed clicks = current impressions × previous CTR − current clicks.

For example: a query had 2,000 impressions at 5% CTR (100 clicks) last period, and now has 2,200 impressions and 55 clicks. At the old CTR you'd expect 110 clicks, so the estimate is 110 − 55 = 55 missed clicks. It's a counterfactual: it assumes the old CTR would have held. Use it to rank the list, not to report an exact loss.

Step 4: Group the survivors

A list of 80 queries is easier to act on when grouped:

  • By page. Several flagged queries often share one URL, and that page is your unit of work.
  • By intent. Definitions, how-tos, comparisons, pricing. Ahrefs found AI Overviews trigger mostly on informational queries (Ahrefs), but Semrush has reported them growing on commercial results too (Semrush).
  • By value. Which of these queries ever led to sign-ups or sales? Check conversions in your analytics.

Step 5: Confirm on the results page

For the top queries in each group, search in a private window from your main market and note:

  • whether an AI Overview appears
  • whether your page is one of its links
  • what else sits above your result

Write down the date. AI Overviews vary by user and change over time, and Google keeps changing their layout. In October 2026 it announced more prominent links inside AI Overviews and AI Mode (Google). Rank trackers that record SERP features can automate this check if you already pay for one.

Then check the pages behind those queries in the Generative AI performance report (Pages dimension). If a page's AI-feature impressions rose while its clicks fell, that's supporting evidence. If the Overview cites competitors and not you, your page won't appear there at all, which is useful to know too.

Step 6: Keep a running log

Save each export with its date range and the filtered list. Over a few months you'll see which queries keep losing clicks, which recover, and whether changes you made helped. Seer Interactive's data shows CTR on AI Overview queries can move noticeably within months (Seer), so one snapshot isn't the full story.

The shortcut: run the free check

Steps 2 to 4 take the most time. The free AIO Delta check does them for you on an export you download yourself:

  1. In Search Console, set Compare dates (for example, last 28 days vs previous period) and export the Performance report.
  2. Upload the export, or paste the queries or pages table, on the check page. No login, no Google connection.
  3. You get the rows where position held or improved and impressions didn't fall but CTR and clicks did, ranked by estimated missed clicks with the formula above.

The results are estimates from your own data, not figures from Google, and AIO Delta isn't affiliated with Google. Once you have the list, our guide on what to do about pages that lose clicks to AI Overviews covers the next steps.

FAQ

Can Search Console list the queries that show an AI Overview? No. AI Overview data is counted inside Web search in the Performance report, and the Generative AI report shows impressions by page only. You have to infer affected queries from changes in CTR.

What is the signal that a query is losing clicks to an AI Overview? Average position held or improved, impressions held or rose, and CTR and clicks fell between two comparable periods. Then a manual search confirms whether an AI Overview appears for that query.

How many queries can I analyze from the Search Console interface? The table shows up to 1,000 rows and leaves out anonymized queries, according to Google. For more coverage, use the Search Analytics API or bulk data export.

Is the estimated number of lost clicks exact? No. It's current impressions times the previous period's CTR minus current clicks. That assumes your old CTR would have held, which is a simplification. Use it to rank queries, not as an exact count.

Does the free check need access to my Search Console account? No. The AIO Delta check works on a Performance export you download yourself. There's no login and no Google connection for the free check.

Sources