Google AI Overviews visibility for SaaS
A surface inside Search, built from the ranked results
An AI Overview is generated from pages already ranking for the query, drawn from Google's main index. It is a presentation layer on top of Search, not a separate system with its own corpus, which means conventional ranking remains the entry ticket.
It does not appear on every query. Google triggers one where it judges a synthesised answer more useful than a list of links, which skews towards informational and comparison queries, and away from navigational and transactional ones. Which of your queries trigger one is an empirical question, answered by checking, not by assuming.
The commercial problem it creates is well known and worth stating plainly: an overview answers the question on the results page, so the user often does not click. Being cited in one is worth real brand exposure and considerably less traffic than the equivalent conventional ranking.
Which crawler does what, and what blocking it costs you
Training crawlers and retrieval crawlers are different things. Blocking a retrieval crawler removes you from the answers. Blocking a training crawler does not. Getting the two confused is the most common self-inflicted AI visibility problem we find.
| User agent | Purpose | What blocking it costs you |
|---|---|---|
| Googlebot | Search index | Builds the index the overview is generated from. No index presence means no overview presence. |
| Google-Extended | Retrieval | Governs whether your content can be used to ground Google's AI surfaces, including AI Overviews. Blocking it removes you from them while leaving conventional rankings in place. |
Our own policy is published at surge45.com/robots.txt, with a line per agent and the reasoning in the file. If we are going to advise on crawler policy, our own should be readable.
How pages get pulled into an overview
Overviews cite a small number of pages, usually with links beside the generated text. Selection favours pages that answer the specific question directly and are already ranking well, but ranking first does not guarantee inclusion and being included does not require ranking first.
Selection is passage-level. The unit is the paragraph that answers the question, not the page as a whole, so page-level authority matters less here than the presence of a clean, self-contained answer somewhere on the page.
Overviews are also unstable. The same query can produce an overview one week and not the next, with a different source set. Point-in-time measurement is close to meaningless, and tracking needs to be continuous to say anything real.
Observed to change Google AI Overviews visibility
Ranking for the query in the first place
Overviews are built from ranked results. Conventional SEO is not a legacy concern here, it is the prerequisite.
A direct answer in the first paragraph of a section
Selection is passage-level. Answer the question, then qualify it. A buried answer does not get pulled.
Structured, extractable formatting
Clear headings, self-contained paragraphs, tables where a comparison is genuinely tabular. Not schema for its own sake.
Knowing which queries actually trigger one
A substantial share do not. Working on queries that never produce an overview is the most common wasted effort on this surface.
Sold for Google AI Overviews, and not worth buying
Expecting traffic to follow citation
Overviews reduce clicks. Being cited is brand exposure with modest traffic attached, and any report that presents it otherwise is misleading its reader.
Blocking Google-Extended to opt out
It removes you from AI Overviews and from Gemini, while your competitors stay in. It does not restore the clicks.
What we do on Google AI Overviews
- 1Establish which of your target queries actually trigger an overview, and drop the ones that never do.
- 2Track overview presence continuously, because the surface is unstable week to week.
- 3Restructure ranking pages so the answer sits in an extractable opening passage.
- 4Report citation and traffic separately, and be explicit that they move differently.
- 5Confirm Google-Extended is not blocking the surface.