Skip to content
RankX AI
RankX AI Docs
Google Results

AI Overviews

How often Google shows an AI Overview for your tracked keywords, whether your brand is in it, and the three verdict states that must not be merged.

An AI Overview is the summary Google shows above the ordinary results for some queries. RankX AI captures it on your tracked keywords, at the same time as the position check, and records how often one appeared and whether your brand was named or cited inside it.

This is a different surface from the five AI assistants and is measured a different way. It is written in full as "AI Overviews" everywhere in the product and in these docs, never abbreviated.

Where the data comes from

The rank tracker, on tracked keywords. Not the AI-visibility run, and not your prompts.

That single fact answers most questions about this screen:

  • A Website with no tracked keywords has an empty AI Overviews section, no matter how many prompts it has.
  • Adding keywords widens this surface. Adding prompts does not.
  • The cadence is your rank-check cadence: your plan's floor, or 7 days while on trial, whichever is slower.

What is recorded

For each check on each tracked keyword:

Whether an overview appeared at all. This is the first figure, and it is about the query rather than about you. A category where Google summarises everything is a different competitive problem from one where it summarises nothing.

Whether your brand was named inside it, when one appeared.

Whether your site was cited inside it, which is a separate thing from being named. See AI Overview Citations.

Three verdict states, never merged

StateMeaning
MentionedAn overview rendered and your brand was named in it
Not mentionedAn overview rendered and your brand was not named
UnknownAn overview was detected but not captured

Unknown is a real third state and it is not a negative. Merging it into "not mentioned" would manufacture absences that were never measured, and it would make your presence rate wrong in the one direction that flatters nobody. See null is not zero.

Separately, a check where no overview rendered is not a failure to measure. The check ran and found none, and that is a fact about the query.

Reading it

Start with presence rate, not with your own mention rate. How often Google summarises your category decides how much this surface matters at all. A category with overviews on 10% of your tracked queries is a smaller problem than one at 80%, whatever your mention rate inside them.

Then read mention rate against presence. Being absent from 100% of overviews on a query set where overviews appear rarely is a much smaller finding than being absent from a set where they appear on everything.

Watch the pairing with position. A page that ranks well and is absent from the overview above it is a specific, workable problem: Google found your page and its summary layer did not use it. That is usually a content-shape problem rather than a ranking one, and AI Readiness's answer category is where to look next.

Do not treat presence as stable. Whether Google shows an overview for a given query changes, sometimes substantially, when Google changes the model behind it. A drop in presence rate across many keywords at once is usually Google, not you.

What it costs

The AI Overview capture is a speculative hold placed when the rank check runs, and released in full if no overview rendered. So a tracked keyword settles at one of two prices depending on whether Google showed a summary that day, never in between.

That is why the rate card carries it as a separate line with an explicit condition rather than folding it into the rank check. See the credit cost reference.

What this screen cannot tell you

Why Google chose the sources it did. RankX AI records what was cited, not the retrieval decision.

Anything about queries you do not track. Overviews are captured on tracked keywords only.

Whether an overview cost you a click. RankX AI does measure the click-through difference on queries where an overview appears, but that lives in Search Console because it needs Google's own click data, and it refuses to conclude on a sample too small to support one.

Where to go next