Most guides on ranking in AI Overviews describe a lever Google says does not exist. No AEO schema, no Overview-specific markup, no ranking system sitting beside Search. I have read Google's documentation on this closely, and it is blunter than the industry around it.
What there is instead: a narrow eligibility gate that quietly disqualifies pages, a retrieval mechanism that matches you against questions nobody typed, and an outcome that splits four ways rather than one. This post covers each.
AI Overviews SEO: Google says there is no special lever
Google's guidance for site owners is direct. Structured data, it says, isn't required for generative AI search, and there's no special schema.org markup you need to add. Keep using schema for rich results. Do not expect it to move Overviews.
Google's AI features documentation covers both AI Overviews and AI Mode, which Google launched as a separate tab in 2025 and has been expanding since. Both draw on the same index. Neither has a ranking system of its own.
The same document puts generative features inside the existing system rather than next to it. They are "rooted in our core Search ranking and quality systems," assembling answers from the Search index with retrieval-augmented generation. So the honest version of "how to rank in AI Overviews" starts with being retrievable in ordinary Search, which is not glamorous and is what the evidence supports.
That does not make the question empty. It moves it. The work is ordinary; the measurement is not, and that distinction is what our methodology is built around.
The eligibility gate nobody checks
Before ranking is a question at all, there is a binary one. To appear in generative features, a page must be indexed and eligible to show in Search with a snippet.
One word in that sentence does more damage than most audits catch. Google's advice is that nosnippet, data-nosnippet, max-snippet and noindex set your display preferences, and more restrictive permissions limit how your content is featured in its AI experiences.
The full list of what those directives do is in Google's snippet documentation and its robots meta tag reference. They were designed for controlling how much of a page shows in a blue-link result. They now also control whether a page can feed an Overview at all.
So a max-snippet:0 left over from a scraping worry, or a data-nosnippet
wrapped around the one paragraph that actually answers the question, removes
you from Overviews while leaving your blue-link ranking exactly where it was.
No rank tracker will show it. Check these first, because no amount of content
work survives them.
I found one of these on a client site last year. They had spent four months rewriting category pages and could not understand why nothing moved. One meta tag.
Query fan-out: you are answering questions nobody asked
The mechanism worth understanding is what Google calls query fan-out. The model generates a set of related queries alongside the one the person typed, fetches results for all of them, and assembles one answer.
The consequence runs against instinct. You are not competing for one query. You are competing for a spread of related ones you never see, and a page that answers a narrow question thoroughly can be pulled into an Overview for an adjacent question it never targeted.
That is why choosing which prompts to track matters more than it looks. We offer a search-volume check on each suggestion, and the useful finding is how often it comes back empty: the question-shaped phrasings people actually put to an assistant mostly have no measurable search volume at all, because nobody types them into a search box. A keyword tool cannot tell you what to track here, which is why the thing worth measuring is the answers. Choosing the set is the decision every downstream number inherits.
The three things people do instead
Nearly every "AEO checklist" reduces to one of three moves. Each is either contradicted by Google's documentation or unsupported by anything anyone has measured.
Adding schema to chase Overviews. Covered above. Google's structured data guidance is about eligibility for rich results, a different surface with its own requirements. Worth doing. Not this.
Google does attach one condition to schema that is easy to get wrong: it has to match the visible content. Markup describing a price, rating or author the page does not show is a quality problem, and the penalty for getting it wrong is larger than any upside from getting it right.
Rewriting everything "answer-first." There is a real idea buried here. Retrieval works on passages, so a claim written out in one sentence is easier to lift than the same claim spread over a table and three subheadings. But converting an entire site into question-and-answer format optimises for a mechanism nobody outside Google has measured, and it usually makes the pages worse to read. The version worth keeping is narrow: say the thing, in a sentence, near where it is asked.
Publishing more. Volume is the reflex when a brand finds it is absent, and it is the wrong response to the most common finding. Being cited without being named means Google found you, judged you relevant, linked you, and still described someone else as the answer. The gap is in how your category gets described, not in how much you have written about it. That is why we report how you are described as its own number rather than folding it into a mention count.
How to optimize for AI Overviews: what actually moves them
Google's own ordering here is duller and more honest than most alternatives, and it is the same advice it has given for years in its helpful content guidance. Creating content people find unique, compelling and useful "will likely influence your website's presence in generative AI search in the long run more than any of the other suggestions in this guide."
Beneath that, in rough order of how often we see it matter:
- Fix snippet eligibility. Binary, and invisible to rank tracking.
- Answer the question on the page, in plain sentences. Retrieval works on passages. A claim buried in a comparison table is harder to lift than the same claim written out.
- Work on the pages that already brief your category. In most categories the heavily cited domains are review sites, comparison posts and forums, not vendor sites. Being accurately described there beats another post on your own blog.
- Watch the framing, not just the mention. An Overview can name you as the expensive option, and that is a content problem upstream of Google.
How to tell whether any of it worked
This is where most AI Overview advice stops, and it is the part we can speak to with data.
An Overview is generated at the moment of the search. Two checks minutes apart can name different brands with nothing having changed. A before-and- after screenshot is not evidence. What you need is a rate across repeated checks with the number of checks attached, and roughly two weeks before reading a direction into anything. "Ranking" in an Overview is not a position either. Each check lands in one of four states: no Overview shown, shown with you absent, cited but not named, or named. Each implies different work.
It also means an Overview being inconsistent is not the same as it being wrong. That distinction gets its own piece: are AI Overviews accurate?
To track AI Overviews this way, fix the queries, stay in one market and record all four states on a schedule. RankHound, the AI visibility platform brands use to get recommended by AI, runs it for you. Its AI Overview tracking checks again on a fixed schedule and reports the four states separately rather than averaging them into a score, so you can see whether what you changed worked.
