Can a page blocked by robots.txt appear in AI Overviews?

A page that robots.txt blocks for Googlebot can't be used as a supporting link in AI Overviews. The reason is Google's own eligibility rule.

Google's AI features documentation says that to be shown 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." It adds: "There are no additional technical requirements."

That rule chains three things together:

1. Crawling. Googlebot has to fetch the page. A robots.txt disallow tells it not to.
2. Indexing with content. Google can only use text it has crawled.
3. Snippet eligibility. Without crawled text, there is no snippet to show, and no content for an AI Overview to draw on.

Break the first link and the other two fail. That's why Google treats Googlebot as the control for its AI features. As Google puts it, AI is built into Search, so robots.txt directives for Googlebot are the control. For the detail on how this works, see AI Overviews and Googlebot: no separate crawler.

Many site owners look for a robots.txt line that blocks AI Overviews and leaves classic Search alone. As of October 2026, none exists.

The token people usually reach for is Google-Extended. Google's common crawlers documentation says it cuts 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." AI Overviews and AI Mode are part of Search, so Google-Extended does not touch them. The Google common crawlers doc and Google-Extended covers the split in more detail.

So your robots.txt choices for Google come down to this:

Blocking other AI bots, such as OAI-SearchBot or PerplexityBot, changes nothing in Google either. Those tokens govern other engines. See whether blocking all AI bots hides you from AI search.

Blocked URLs can still show up as bare links

Google's robots.txt guide notes that robots.txt is not a way to keep a page out of Google. A blocked URL can still be listed if other pages link to it, usually without a description. That bare listing has no crawled content, so it doesn't meet the snippet condition for a supporting link.

A block you didn't write

A disallow on a parent directory or a wildcard pattern can catch pages you meant to keep. A firewall or CDN rule can also turn Googlebot away while robots.txt allows it. The robots.txt vs firewall comparison explains why both gates matter.

noindex behind a disallow

If you disallow a page and also add noindex, Googlebot can't crawl the page to see the tag. Pick one mechanism per page.

The Search Console control

Google also has a Search Console control for generative AI features (AI Overviews, AI Mode and Discover's generative features). Inclusion is the default. Google describes the control as rolling out to a subset of site owners, and child properties inherit the parent's setting. It is not crawlable from outside, so check it in Search Console. See whether you need to opt in to AI Overviews.

If you want a page in classic results but not quoted in AI answers, robots.txt is the wrong tool. Google documents on-page snippet controls instead, and they only work if Googlebot can crawl the page and read them.

• nosnippet on the page removes snippets, including use in AI features.
• max-snippet:0 has the same practical effect.
• data-nosnippet on an element hides just that section.
• noindex removes the page from Search entirely.

A page-level tag looks like this:

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

Know the trade-off. nosnippet also strips the text snippet under your classic blue link. There's no control that hides content from AI Overviews while keeping a full classic snippet.

These tags also cause accidental losses. Templates sometimes carry nosnippet or noindex onto pages that should be visible. The accidental noindex audit walks through finding them.

Start with what you control, then accept what you don't.

1. Read your robots.txt for Googlebot rules. Look for disallows on pages you want in AI Overviews, including wildcards and parent paths. The robots.txt checker for AI crawlers shows how each crawler resolves.
2. Confirm Googlebot isn't blocked at the network layer. A firewall 403 has the same result as a disallow.
3. Scan for snippet and index tags. Check noindex, nosnippet, max-snippet and data-nosnippet on the pages that matter.
4. Check the Search Console generative AI control, if your property has it, including inherited settings.
5. Leave Google-Extended to its own decision. Block or allow it based on Gemini Apps and training, not AI Overviews.

Passing all of this makes a page eligible. It doesn't make it cited. Google states that indexing and serving aren't guaranteed, and that no special optimization is needed for AI Overviews. For the parts Google decides, read getting cited in AI Overviews: your control and Google's.

Can I block AI Overviews but stay in Google Search? Not with robots.txt. No token targets AI Overviews alone. The documented options are snippet controls such as nosnippet, max-snippet:0 and data-nosnippet, which also limit your classic snippet. The Search Console generative AI control is another route where Google has rolled it out to your property. Googlebot must still be allowed to crawl the page for snippet tags to be read.

Does blocking Google-Extended remove me from AI Overviews? No. Google's common crawlers documentation says Google-Extended does not affect a site's inclusion in Google Search and is not a ranking signal. It governs training and grounding for Gemini Apps and Vertex AI. AI Overviews and AI Mode are Search features, so Googlebot rules and snippet controls are what apply to them.

Do I need special markup or an llms.txt file to appear in AI Overviews? No. Google's AI features documentation says there are no additional requirements or special optimizations needed to appear in AI Overviews or AI Mode. Its optimization guide adds that Google Search doesn't use AI text files or special markup for these features. The requirement is the standard one: indexed and eligible for a snippet.

If I unblock Googlebot, will my page appear in AI Overviews? It becomes eligible, which is different from appearing. Google says indexing and serving aren't guaranteed. AI Overviews also don't trigger for every query. Unblocking removes a barrier you control. Whether a specific page gets used as a supporting link for a specific query is Google's decision, and no setting or tool can promise it.

Does JavaScript rendering affect AI Overviews the way it affects ChatGPT? Much less. Googlebot renders JavaScript, so client-side content can still reach Google's index. Many other AI crawlers, including OpenAI's and Anthropic's, fetch JavaScript files but don't execute them, according to Vercel's crawler study. For Google, crawl permission and snippet eligibility are the main gates to check.