AI Search

AI Overviews Overview

The site-level scorecard for Google's AI Overviews. It answers the question every SEO is asking in 2026: how much traffic is AI taking from me? Numbers here come from Search Console's searchAppearance dimension — real impressions and clicks attributed to the AI Overviews bucket, alongside your non-AIO baseline so you can see the gap.

Data availability. This report depends on Google returning an AI Overviews value in Search Console's searchAppearance dimension. Google added that bucket in 2026 and coverage is still rolling out; as of September 2026 most properties — including sites with heavy AI Overview exposure — get no AIO rows from the API at all. When Google returns nothing, this report shows a "no AI Overviews impressions detected" notice rather than zeros, and no "estimated clicks lost" figure is computed. Treat it as a monitor that switches on when Google's data does, not as a number you can rely on today.

What it measures

  • AIO impressions — times your site appeared inside an AI Overviews answer.
  • AIO clicks — clicks attributed to those AIO appearances.
  • AIO CTR — AIO clicks ÷ AIO impressions.
  • Non-AIO baseline — clicks, impressions and CTR for every other appearance type your site qualified for in the same window. This is the comparison group.
  • Estimated clicks lost — (non-AIO CTR − AIO CTR) × AIO impressions. Floored at zero. The upper bound on what AIO cost you relative to your own baseline.

How we compute it

  1. Search Console returns daily totals by searchAppearance dimension. We pull this with one API request per day (the dimension cannot be combined with others) and store it in gsc_search_appearance_day.
  2. We bucket every row whose appearance value matches AI Overviews (we match aioverview case-insensitive, stripping underscores, to handle both the aiOverview and AI_OVERVIEW enum spellings Google has used).
  3. Every other appearance type is summed into the non-AIO baseline.
  4. The KPI headline and chart roll up the window. The table breaks the same numbers down by day.

How to read each row

  • AIO Impressions climbing — Google is increasingly putting you in AIOs. Good in reach, but watch the CTR.
  • AIO CTR < Non-AIO CTR — the classic AIO erosion pattern. Users get their answer in the SERP and don't click through.
  • AIO CTR ≥ Non-AIO CTR — your AIO snippets are actually pulling their weight. Rare in 2026 but possible for branded or transactional intent where the user wants to land on your page.

What to do with it

  1. Watch the trend — if AIO impressions ramp without a CTR collapse, AIOs are net-positive for you in this window.
  2. If estimated clicks lost is large, jump to AIO Erosion (Suspected) to see which queries are driving it.
  3. Cross-reference with AIO-Resistant Pages to find the templates that are working and copy them to underperforming pages.

Caveats & limits

  • Google's AI Overviews bucket in searchAppearance is a 2026 addition and its reporting is impression-led. History from before Google started emitting it has no AIO rows, and many properties still return none — see the availability note above.
  • "Estimated clicks lost" assumes the user would have clicked at your non-AIO CTR if AIO hadn't been there. That's a fair upper bound, not a precise loss — some AIO impressions wouldn't have converted at all.
  • Search Console can be 2–3 days behind realtime; recent dates in the trend are subject to backfill.

Related reports