Getting Cited in AI Overviews: Your Control and Google's

Google's AI features page for site owners is short on rules, and that is the point. It says that to be eligible as a supporting link in AI Overviews or AI Mode, a page "must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements. There are no additional technical requirements."

The same page says there are no additional requirements "nor other special optimizations necessary." It also says "Indexing and serving isn't guaranteed." Eligibility gets you into the pool. It does not get you picked.

What Google does not document matters just as much:

• How AI Overviews choose which eligible pages to cite.
• How often an Overview triggers for a given query.
• Which model version runs AI Overviews. As of October 2026, Google says only that AI Overviews and AI Mode "may use different models and techniques."

For a line-by-line reading of that page, see Google's AI features documentation, digested. The practical consequence is simple: your job is to make sure you are eligible, then stop paying for promises about the rest.

Four on-page controls can keep content out of AI Overviews. Google documents them as the way to limit how content appears in its AI features. Each one is easy to set by accident, often in a template.

• noindex removes the page from the index, so it can't be eligible at all.
• nosnippet blocks snippets, and snippet eligibility is part of Google's rule.
• max-snippet:0 has the same effect as nosnippet.
• data-nosnippet on an HTML element hides that section from snippets and AI answers.

A tag like this in a shared header will quietly remove every page that uses it:

<meta name="robots" content="nosnippet">

Say you run a dental clinic in Austin and a developer added data-nosnippet to a wrapper div to hide a cookie banner. If that div also wraps your services list, Google can still index it, but it won't quote it. Check the rendered HTML of your key pages, not just the CMS settings.

If a page is indexed and still never shows up, the reasons are usually outside these controls. Our page on why an indexed page never appears in AI Overviews walks through them.

There is no robots.txt token that blocks AI Overviews or AI Mode specifically. Google's position is that AI is built into Search, so robots.txt rules for Googlebot are the control. Block Googlebot and you lose Search, AI Overviews included. Allow it and you have met the crawling part of eligibility.

Google-Extended is a separate token, and it is widely misunderstood. Google's common crawlers documentation says it governs training and grounding for Gemini Apps and Vertex AI, and that it "does not impact a site's inclusion in Google Search nor is it used as a ranking signal." Blocking Google-Extended does not remove you from AI Overviews. Allowing it does not add you. More detail is in our note on Google's common crawlers and Google-Extended.

A page that robots.txt blocks from Googlebot can't be fetched, which raises its own edge cases. See whether a robots.txt-blocked page can appear in AI Overviews.

One thing works differently from other engines. Googlebot renders JavaScript, so client-side rendering is far less of a risk on Google than it is for the crawlers behind ChatGPT or Claude. That is a separate check covered in getting cited by ChatGPT.

Google added a control in Search Console that lets a property opt out of AI Overviews, AI Mode and generative AI features in Google Discover. Three facts about it matter.

1. It is opt-out, not opt-in. Google describes inclusion as "the default control for all properties." You don't need to request anything. Our answer on whether you need to opt in covers this.
2. Child properties inherit. The default for a child property is "Inherit control from parent." If someone opted out the domain property, every child property follows, even if nobody on your team touched it.
3. Nobody outside can see it. No crawler and no third-party tool can read this setting. Only someone with Search Console access can.

Google's help documentation has described the control as rolling out to a subset of website owners, so you may not see a toggle yet. Google also says the setting isn't a ranking or inclusion signal for other parts of Search, and that opting out of display doesn't stop your content from helping power Search more broadly.

The check takes a minute: open the parent property, read the setting, then check each child. Our guide to Google's AI features control shows where it lives.

Once you are eligible, the rest is Google's decision.

• Triggering. AI Overviews often don't appear at all. Google decides per query.
• Link selection. Google doesn't publish how it picks supporting links.
• Rank. Organic rank is a loose proxy at best. Ahrefs found that 37.9% of URLs cited in AI Overviews also appeared in the first 10 results, in its March 2026 study. That leaves most citations coming from outside the top 10.
• Position inside the answer. As of October 2026, Search Console's generative AI report shows impressions only, with no clicks, click-through rate or position. Any tool that reports your "AI Overview rank" has nothing from Google to check it against.

Two things have some support in the evidence. Stating a specific fact (a price, a number, a one-line definition) on a fetchable page gives Google a sentence it can quote. And when Overviews cite other sites for your topic, being named on those sites is associated with appearing in the answer. Neither comes with a promised effect.

Much of the advice sold for AI Overviews has primary sources against it.

• Schema markup. Google says structured data isn't required for generative AI search. Ahrefs' matched-control test of 1,885 pages found AI Overview citations fell 4.6% after schema was added. Existing markup does no harm, so there's no need to remove it. It just isn't a lever.
• FAQ schema. Google deprecated FAQ rich results in May 2026.
• llms.txt. Google's optimization guide says Google Search ignores these files.
• AI-friendly writing or chunking. Google says you don't need to write in a specific way for generative AI search, and that there's no ideal page length.
• E-E-A-T scores. Google says E-E-A-T "isn't a specific ranking factor." There is no score to raise.

Hidden text or instructions aimed at AI systems are a different category. They are manipulation, they carry real risk under Google's spam policies, and they have no place in a legitimate plan.

1. Confirm your key pages are indexed in Search Console's URL Inspection.
2. Search the rendered HTML of those pages for noindex, nosnippet, max-snippet and data-nosnippet. Remove any you didn't mean to set.
3. Read robots.txt for Googlebot rules. Ignore Google-Extended for this purpose.
4. Open the Search Console AI features control on the parent property and every child.
5. Put your most important facts (pricing, what you do, who it's for) in plain sentences on pages Google can index.

Then look at outcomes for real buyer questions. The free checker on this site shows whether AI engines name you for up to three of them, as a snapshot. It won't tell you why Google picked someone else, because nobody outside Google can.