There is no separate door. What decides it is the same crawl, plus a page worth quoting.
Appearing in Google AI Overviews requires no separate opt-in: eligibility follows standard Googlebot crawling and indexing, so a page must be indexed, allow snippets, and state its answer in a quotable form.
The most common question about AI Overviews assumes there is a switch somewhere — a file to publish, a crawler to allow, a submission to make. There is not. Google’s own documentation is unusually blunt about it, and once you accept that, the work becomes clear and a great deal less mysterious.
An AI Overview is the generated block at the top of some Google results pages, above the ranked links. It is written by a model from pages Google already holds in its Search index, and it carries supporting links to a handful of them. AI Mode is the conversational surface built on the same machinery.
Two things follow, and they are the two most people get wrong. The overview is not a separate index — it draws on the Search index you are already in or already absent from. And being linked beside an overview is a citation, not a ranking: you are named because a sentence on your page was useful, not because you held a position.
No, and this is the part worth reading twice. Google Search Central’s guidance on AI features in Search states that “there are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary”. The documented route in is the ordinary one: be crawlable, be indexed, be eligible for regular Search snippets, and publish content that is genuinely useful.
That sentence kills a whole category of vendor product. An AI Overviews submission service, an overview-specific schema type, a special file that gets you into the box — Google says none of it exists. What does exist is the unglamorous work of being indexed, being a plausible candidate, and being written in a way that is easy to lift from.
The honest caveat: no amount of correct work guarantees a citation. Generated answers are non-deterministic, the set of linked sources varies between runs of the same query, and Google does not promise inclusion to anybody. You can make yourself a strong candidate. You cannot buy the slot.
It does not, and this is the single most expensive misunderstanding in the area. Google’s crawler documentation says plainly that Google-Extended “does not impact a site’s inclusion in Google Search nor is it used as a ranking signal in Google Search”. Google-Extended is a control over whether your content may be used for training future Gemini models and for grounding in some of Google’s other systems. It is not the crawler that feeds Search, and Search is what feeds AI Overviews.
The failure mode is predictable. A company blocks every AI-sounding user agent during a security review, adds Google-Extended to the list, and wonders months later why nothing changed in Search. The opposite error is worse: it allows Google-Extended, believes the AI Overviews work is done, and never checks whether Googlebot itself can reach the pages that matter.
| Control | What it governs | Effect on AI Overviews |
|---|---|---|
Googlebot in robots.txt | Crawling for Google Search | Decisive. Blocked means not indexed means not eligible |
noindex | Whether the page is in the index at all | Decisive. Removes the page from every Search surface |
nosnippet / max-snippet | Whether Google may show text from the page | Restricts what can be shown from you in generated answers |
data-nosnippet | Specific passages within a page | Excludes those passages from being shown |
Google-Extended | Gemini training and grounding in other Google systems | None. Not a Search crawler, not a ranking signal |
If you take one table away from this guide, take that one. Four of those five controls do something to your Search visibility. The one everybody argues about does not.
The relationship is real but it is not a straight line, and treating it as one leads to bad decisions in both directions.
Ranking is the gate. A page Google has not indexed, or ranks nowhere for the query, is not in the candidate pool the overview is generated from. Conventional SEO is a prerequisite and there is no clever way around it — which is the unfashionable position taken on the AEO versus SEO page.
But ranking is not the selector. Within the candidate pool, what gets quoted is whatever answers the question most directly and most cleanly. A page ranked fourth that opens with a plain, complete, checkable statement can be the one cited while the page ranked first — a 4,000-word narrative that circles the topic for six paragraphs before saying anything — is not. This is why a site can watch its rankings hold steady while its visibility inside generated answers moves independently.
The practical reading: ranking buys you a ticket into the room. Extractable writing decides whether anyone repeats what you said.
The unit that gets lifted is not the page. It is the sentence or the small block. Structure the page so those units exist and are easy to find.
A worked example. A pricing page headed “Pricing” with a three-column card layout and no prose gives a model nothing to say. The same page with a heading reading “How much does a Core retainer cost?” and a first line reading “A Core retainer is £2,000 per month and covers the audit, monthly measurement and up to eight pages of implementation” gives it a complete sentence to repeat. Same information. Only one version can be quoted.
The snippet controls cut both ways. nosnippet, max-snippet and data-nosnippet are the documented ways to limit what Google may display from your page, and they apply to generated answers as well as to classic snippets. Publishers sometimes reach for them to stop their content being summarised. That works — and the same setting removes the text Google would have used to cite you. Decide deliberately, not as a side-effect of a policy written about something else.
Not separately, and you should stop looking for the report. Google Search Central states that clicks from AI Overviews and AI Mode are included in the overall Search traffic in the Search Console performance report, under the standard “Web” search type. There is no AI Overviews filter, no dedicated search type and no breakdown by surface.
The same limitation applies in your analytics. A click from an AI Overview arrives as ordinary Google organic traffic, because it is ordinary Google organic traffic — same referrer, same medium, indistinguishable at the session level from a click on a blue link two positions below. No amount of GA4 configuration separates them, and any tool claiming to report your AI Overviews traffic precisely is inferring it, not measuring it.
This is not a gap that will be closed by better tracking on your end. It is a property of how the traffic is delivered.
Working out which column a question falls into saves a great deal of wasted effort.
| Can be measured | Cannot be measured |
|---|---|
| Whether your page is indexed and eligible at all | How many of your Google clicks came from an overview |
| Whether an overview appears for a query you care about, by observing it | How often the overview appeared, across all users, over time |
| Whether you are among the linked sources, in a given observed run | Whether you are cited for every user who asked that question |
| Total impressions and clicks for the query in Search Console | The split of those impressions between the overview and the ranked list |
| Movement in impressions and clicks after a change you shipped | Clean attribution of that movement to the overview specifically |
What is left is observation, done properly. Pick the questions your buyer actually asks, run each one several times rather than once, record how often an overview appears and how often you are among its sources, and hold the question list steady so the next run is comparable. A single check is a screenshot. A repeated protocol is a measurement. How we run and log those checks →
Pair that with the Search Console numbers for the same queries. You will not get attribution, but you will see whether total impressions and clicks moved after you changed the page, which is the decision the measurement exists to support.
Because the answer was given above the links. If a query has a short factual answer, an overview that supplies it removes the reason to click for the people who only wanted that fact. That is a real effect and pretending otherwise is not useful.
Two things follow. The loss is concentrated in the queries you were least likely to convert — definitional questions, quick lookups, people who wanted a number. And restricting your way out of it does not recover the click: it removes your name while the answer still gets written, from somebody else’s page, describing your category without you in it.
The defensible response is to move up the page structure rather than down: make sure you are the cited source on the questions where being named leads somewhere, and accept that the trivial lookups were never the business. Where this fits in the wider shift →
In this order, because each step is cheap and each one unblocks the next.
nosnippet, max-snippet and data-nosnippet, and find out who added them and why.That sequence costs a few days and closes the failures that account for most absences. If you would rather have it done to your site than do it yourself, the free AI visibility check runs the access tests, reads the snippet directives and reports who is cited instead of you, and there is a longer walk-through of the same ground in the practical AEO guide.
No. Google Search Central states there are no additional requirements to appear in AI Overviews or AI Mode and no special optimisations are necessary. Eligibility follows standard Search indexing, so the route in is being crawlable, indexed and eligible for ordinary snippets.
No. Google's crawler documentation says Google-Extended does not impact a site's inclusion in Google Search and is not used as a ranking signal. It governs Gemini training and grounding in some of Google's other systems, which is a separate question from Search eligibility.
Not separately. Google states that clicks from AI Overviews and AI Mode are included in the overall Search traffic in the performance report under the Web search type. There is no dedicated filter, so the clicks cannot be isolated from ordinary organic traffic.
Not necessarily in the top position, but the page does need to be indexed and a plausible candidate for the query. Ranking gets you into the pool; what gets quoted is whichever page answers the question most directly and cleanly, which is not always the highest-ranked one.
Schema helps a machine understand what a page is and who published it, which supports being identified correctly. It is not an entry requirement for AI Overviews, and no schema type exists that requests inclusion. Treat it as clarity work rather than as a lever.
For short factual queries, often yes, because the answer is given above the links. The people lost were mostly the ones who wanted a fact rather than a vendor. Restricting snippets does not recover those clicks; it removes your name while the answer still gets written from someone else's page.