How to show up in Google AI Overviews is a narrower question than most guides admit. Google's eligibility rule is one sentence: the page must be indexed and allowed to show a snippet. There is no AI-specific markup to add and no file to upload. The work is deciding which passages deserve to be quoted, and removing anything that quietly forbids quoting.
Start by proving the page can be quoted
| Check | Where to look | Fix |
|---|---|---|
| Indexed | URL Inspection in Search Console | Request indexing, fix the canonical |
| Snippet allowed | Meta robots and X-Robots-Tag |
Remove nosnippet and max-snippet:0 |
| Enough quotable text | max-snippet value |
Remove the cap or raise it |
| Block not excluded | data-nosnippet wrappers |
Close the tag, narrow the block |
| Site control | Search Console Settings | Confirm the generative AI setting is include |
That last row catches teams that never touched their HTML. Since August 31, 2026, every property has a site-wide Search generative AI control, defaulting to include, and an exclude there overrides everything else.
Then cover the questions Google fans out to
An overview is assembled from several searches, not one. A query about a category may also trigger searches for pricing, setup and alternatives, and each is a separate chance to be the source.
The numbers support treating fan-out as the main opportunity. Ahrefs found, in a March 2026 study of 863,000 keyword results, that roughly 38 percent of cited pages ranked in the top 10, down from 76 percent in its July 2025 study. Its explanation is that more citations now come from the related searches than from the original result set.
Practically, that means building a list of follow-ups from People Also Ask, the sub-headings inside an overview, and the questions the currently cited pages answer.
Writing for extraction rather than for flow
AI Overviews quote statements, so each section should survive being lifted out of context.
- Put the question in the heading, in the words people search with.
- Answer it in the first sentence.
- Name the product instead of writing "it".
- Include the number, the date or the model name.
- Put background after the answer, not before.
A page written this way reads oddly to nobody. It simply front-loads the useful part.
What to stop doing
Four popular fixes do nothing, by Google's own account: an llms.txt file, special AI schema, Google-Extended rules, and a thin page for every possible follow-up question. The last one is worth a second thought, because it is the pattern Google's scaled content abuse policy targets.
Reading the data you actually have
Search Console mixes AI Overview links into the main Web search report, so a click from an overview arrives looking like an ordinary click. The separate generative AI report, available to every site since August 31, 2026, gives impressions by page, country, device and date, with no queries and no clicks.
That limitation is why teams without a dataset end up guessing. A tool such as seogeoaeo.ai's AI Citation Finder lists the pages cited for a topic, how often each appears and which sites are cited most, at 160 credits per run.
The order of operations
Fix eligibility first, since nothing else matters if the page is excluded. Then pick the ten queries closest to revenue and rewrite the sections that answer them. Then sample the overviews for those queries once a month and record which URLs appear.
FAQ
Does adding FAQ schema help?
Not for AI Overviews specifically. Google states there is no special markup, and the current guidance is that structured data should stay accurate and match visible text.
Why do overviews cite competitors I outrank?
Because the citation may come from a fan-out search you do not rank for. Cover the adjacent question on its own page or section.
Is a high position in the main report proof of an overview citation?
No. The main report includes overview links alongside classic results, so position and clicks do not separate the two.