AI Overviews: What Google Says You Can Influence

Google’s own documentation says there is nothing special to do for AI Overviews: no new file, no dedicated markup, no separate submission process. The eligibility bar is the same one Search has always used – get indexed, be snippet-eligible, meet the normal technical requirements. What you can actually influence is the same thing you could always influence: whether your content is worth citing in the first place, and whether Google can technically reach and understand it. What independent research adds is a harder number on the cost of not being cited: when an AI Overview appears, several studies converge on organic click-through rates dropping by roughly a third to over half for the page that used to sit in position one.

What Google’s documentation actually says you can influence

I read Google’s two most relevant developer pages directly rather than working from secondhand summaries, because this is exactly the kind of topic where confident-sounding advice outruns the source material. The first, AI features and your website, states plainly that there are no additional requirements to appear in AI Overviews or AI Mode, and no other special optimizations are necessary. Sites do not need to create new machine-readable files, AI-specific text files, or new markup to show up in these features – and there is no special schema.org structured data you need to add either.

The technical bar is unchanged from ordinary Search: to be shown as a supporting link in AI Overviews, a page must be indexed and eligible to appear in Google Search with a snippet, meeting the same requirements as regular Search results. If you want to limit or opt out of appearing in these AI features specifically, the same controls that have always governed snippets still apply – nosnippet, data-nosnippet for individual sections of a page, max-snippet, and noindex. There is no separate AI-specific opt-out mechanism; it’s the same levers, reused.

What the optimization guide mythbusts, and what it says actually helps

Google’s companion page, the guide to optimizing for generative AI features, is more useful precisely because it spends as much time debunking tactics as it does recommending them. It states the core requirement is “unique, valuable, good content,” and warns specifically against commodity content – content “often based on common knowledge, which could originate from anyone.” The instruction is direct: don’t “just recycle what others on the internet have already said, or could easily be produced by a generative AI model.”

On the tactics that get repeated in AEO and GEO discussions, the guide is unambiguous. Google Search itself doesn’t use llms.txt files, so adding one to your site neither helps nor hurts your visibility in these features – it’s inert as far as Google’s systems are concerned. There’s no requirement to chop your content into small chunks for an AI system to parse it. And you don’t need to write in some special declarative style purely to be more quotable by a generative AI feature; normal, well-structured writing is the ask, not a new dialect.

Structured data gets the same treatment I’ve covered in more detail on whether schema markup actually helps AI citations: it isn’t required for generative AI search, and there’s no special schema.org markup specific to AI Overviews. Google still recommends using structured data for its ordinary purpose – qualifying for rich results in standard Search – but that’s a normal SEO practice, not an AI Overviews shortcut. Sibling surface AI Mode gets the identical framing, which I went through separately in what changes for publishers under AI Mode; the two features share the same eligibility logic and the same absence of special tricks.

What the guide does say helps: clear technical crawlability so nothing blocks indexing, accurate local and shopping data surfaced through Business Profiles and Merchant Center where relevant, and genuinely useful, non-commodity content that demonstrates direct expertise rather than restating what’s already indexed a thousand times over. None of that is new advice. That’s the point the documentation itself is making – the same fundamentals that were always good Search practice are still the whole answer.

What independent evidence adds about the cost of not being cited

Documentation tells you the eligibility rules. It doesn’t tell you what happens to your traffic once an AI Overview actually appears above your result, so I looked for independently-run measurement rather than stopping at Google’s page. Ahrefs analyzed 300,000 keywords – 150,000 that triggered an AI Overview and 150,000 comparable informational keywords that didn’t – comparing March 2024 against March 2025. The study, run by Ryan Law and Xibeijia Guan and published April 17, 2025, found that the presence of an AI Overview correlated with a 34.5% lower average click-through rate for the top-ranking organic result, relative to similar keywords without one.

Pew Research Center published a separate short-read on July 22, 2025, built from real browsing-panel data rather than keyword-tool estimates, concluding plainly that “Google users who encountered an AI summary were less likely to click on links to other websites than users who did not see one.” The specific figures reported consistently across several independent write-ups of that same study put it at 8% of visits including a click on a traditional search result when an AI summary appeared, versus 15% when it didn’t – and only 1% of visits included a click on a source actually cited inside the AI summary itself.

I want to label the strength of this evidence honestly. These are two independently-run studies using different methodologies – keyword-panel CTR modeling in Ahrefs’ case, real browsing-panel data in Pew’s – and they land on different magnitudes (34.5% versus a roughly 47% relative decline implied by 15% dropping to 8%). They agree on direction and rough scale, not on an exact number, and neither is a Google-published figure. Google has publicly disputed conclusions drawn from studies like these, with reported statements calling the methodology “flawed” and “not representative of Search traffic,” and saying the company has “not observed significant drops in aggregate web traffic.” I’m reporting both the independent findings and Google’s on-record pushback rather than picking a side neither of us can fully verify from outside either company’s raw logs.

A practical checklist

Given what’s actually confirmed above, here’s what I’d prioritize, in order:

• Confirm the page is indexed and returns a normal snippet in regular Google Search first. AI Overview eligibility rides on ordinary Search eligibility – there’s no separate technical bar to clear.
• Don’t build an llms.txt file or chop content into artificial chunks expecting an AI Overviews advantage. The documentation states directly that neither does anything for Google Search specifically; that effort is better spent elsewhere.
• Treat structured data as a normal rich-results investment, not an AI Overviews lever. If you’re deciding how much time to spend on schema, decide it based on the rich-results case I’ve covered separately, not on an AI-citation promise Google’s own guide doesn’t make.
• Spend the time you were going to spend on AI-specific tricks on the thing Google’s guide actually asks for: content that states something the rest of the internet hasn’t already said, grounded in direct experience or verified fact rather than a restatement of common knowledge.
• If a particular page’s value depends on drawing a click rather than just being read inside a summary, expect that value to compress once an AI Overview starts appearing for its target query – the independent CTR studies above both point the same direction, even if they disagree on magnitude.
• Use nosnippet, data-nosnippet, or noindex deliberately if a specific page’s business model depends on the click itself and you’d rather opt out than be summarized for free – understanding that this also removes it from ordinary Search snippets, since the controls aren’t AI-feature-specific.

What this site hasn’t measured yet

I want to be direct about a gap rather than paper over it. This site has no citation- or appearance-tracking pipeline connected for Google AI Overviews specifically, and no measurement was taken as part of writing this piece. I’m not going to state an appearance count or a citation count, verified or otherwise, because neither was actually checked. I’ve written separately about how to measure AI citations in general, and the same discipline applies here: the independent CTR studies above describe industry-wide samples, not this domain, and the honest starting point for a small, early-stage site like this one is that the AI Overviews question is currently a documentation-and-industry-data question, not yet a measured-on-this-site question. That will change once there’s enough underlying Search volume here to measure against, and I’ll report it plainly, including if the answer turns out to be zero.