Google AI Mode vs AI Overviews: Which Gets Cited More
Promptwatch citation share data from February to June 2026 shows Google AI Mode and AI Overviews citing different domains, with neither surface pulling away from the other.
Google has two AI search surfaces, and they do not cite the same domains. Google AI Overviews and Google AI Mode each have their own citation share chart in Promptwatch's data, and across the first half of 2026 neither pulled away from the other. The comparison is worth tracking because the two surfaces answer different queries and a brand can be cited in one and absent in the other.
The citation share reports (AI Overviews and AI Mode, published June 28, 2026) cover the top domains each surface cited in June 2026, with a May comparison. The top AI Overviews sources report rounds out the picture. For anyone who cares about showing up in Google's AI answers, the practical question is what a split between the two surfaces means for visibility.
The measured change
Promptwatch's monthly citation share reports list the top domains each surface cited, with their percentage share of total citations. AI Overviews shows the top 16 domains in June 2026. AI Mode shows the top 17. Each report includes a May comparison chart, so the month over month move is visible alongside the level.
The pattern across the first half of 2026 is divergence without a winner. AI Overviews and AI Mode cite overlapping but not identical sets of domains. Some domains gain share in one surface and lose it in the other over the same month. Neither surface holds a steady lead across the six months of data Promptwatch has published for the pair.
The reports are careful about what they count. The share is a domain's citations divided by total citations for that surface, in that month. A domain can gain share because the surface cited it more, or because it cited less of other domains. The two surfaces are tracked separately, so a domain that leads in AI Overviews is not necessarily a leader in AI Mode.
What the data does and does not tell you
The charts show which domains each surface cited most. They do not say why. A domain that leads in AI Overviews but not AI Mode is consistent with that domain answering the query types AI Overviews serve, which lean toward research and informational. A domain that leads in AI Mode but not AI Overviews is consistent with that domain answering the more transactional, conversational queries AI Mode serves.
The split is therefore consistent with the two surfaces answering different queries, not with one surface ranking the same domains higher. A domain that loses share in one surface can still be cited often in absolute terms, just less often relative to the domains that gained on that surface.
What the reports cannot tell you is whether your own domain is cited in AI Overviews, AI Mode, both, or neither. The data is aggregated and non identifiable. It shows the population level citation mix, not the citation mix for your prompts. For your own brand, the question is which surface cites you, and that is a question only your own tracking answers.
Why this matters for visibility work
The split changes what it takes to be cited. If AI Overviews and AI Mode cite different domains, the work that earns a citation in one is not always the work that earns a citation in the other. A page that ranks well in AI Overviews is not guaranteed to rank in AI Mode, and the reverse.
That makes the two surfaces a split target, not a single one. A visibility strategy built for AI Overviews alone misses the queries that AI Mode answers, and the citations that AI Mode hands out. The same is true in reverse for a strategy built for AI Mode alone.
What to do about it
The first move is to audit which surface cites your domain. If your tracked prompts return AI Overviews citations, the work is to keep your pages strong for AI Overviews. If they return AI Mode citations, the work is to keep your pages strong for AI Mode. If they return both, the work is both. If they return neither, the work is to earn a citation in at least one, which is a different task from holding a position in one you already have.
The second move is to build for the query type each surface answers. AI Overviews lean toward research and informational queries, where a reference source or a deep guide is the most useful. AI Mode leans toward transactional and conversational queries, where a product page or a direct answer is the most useful. The page that earns a citation in one is the page that answers the query type that surface serves.
The third move is to watch the two citation share reports over months, not on a single month. A domain that leads in June is not necessarily a domain that leads in May. The month over month move is the signal, and a single month is a snapshot. A domain that holds a steady share across months is a stronger signal than a domain that spikes in one.
How to measure it properly
Population reports like Promptwatch's tell you what each surface is doing across the whole web. They do not tell you what each surface is doing for your prompts. For that you need your own citation data joined to your own visibility data, split by surface.
That join is the part most visibility tools skip. A prompt tracker that reports whether AI mentions your brand will not tell you whether AI Overviews or AI Mode cites you, how the citation share changed month over month, or whether your pages are in the surface that gained. The per surface citation breakdown is the measurement that turns a population report from interesting context into something you can act on.
Promptwatch publishes that data as citation analytics. The feature tracks page level, domain level, Reddit citations, YouTube citations, offsite mentions, and citation type breakdowns, and it can be read per AI surface. For a report that shows the surface split at the population level, the matching move is to open the same citation view for your own pages, split by surface, and see whether your domain is cited in AI overviews, AI Mode, both, or neither.
The broader pattern
The surface split is one instance of a wider change in AI search. Google is not the only vendor with more than one AI surface. OpenAI has ChatGPT Search and the citation types and shopping surfaces around it. The pattern of one vendor running two surfaces that cite different domains is becoming more common, not less.
For visibility work, that means the number of retrieval surfaces to optimize for is growing, and the surfaces are not interchangeable. A page that earns a citation in AI overviews is not the same as a page that earns a citation in AI mode, and the two need separate work. A visibility strategy that treats Google's AI answers as one surface misses the split.
The practical response is to treat each AI surface as a separate target. The brands that notice which surface cites them, build for the query type that surface answers, and watch the share over months, are the ones that stay cited across both surfaces. The ones that only watch a single Google AI visibility score will see the split as a change in the mix, not as a change in their own visibility.
What to watch next
The reports are snapshots through June 2026. The open questions are whether either surface pulls away in July, whether the top domains keep diverging, and whether a new domain enters the top of either. Those are exactly the questions a per surface citation view answers for your own domain.
The dataset Promptwatch publishes is aggregated and non identifiable, and it is refreshed constantly. That makes it useful for spotting population level shifts like this one. It does not replace the need to track your own brand, your own prompts, and your own citations split by surface. The two work together: the public report tells you what is happening in the field, and your own tracking tells you whether it is happening to you.
For a team that wants to act on the surface split rather than just read about it, the workflow is to open the public reports for context, open the citation analytics view split by surface for your own domain, and connect the two. That is the measurement stack that turns a surface split into a visibility decision, and it is the stack Promptwatch is built around.