Can Google AI Overviews Use Pages That Are Not Indexed?

01Can Google AI Overviews use pages that are not indexed?

No. According to Google's own documentation on AI features and your website, AI Overviews and AI Mode apply the same SEO fundamentals as organic search. A page must be indexed and eligible for snippets before it can appear in an AI Overview. Google does not document any mechanism by which an unindexed page can supply content to AI Overviews.

That said, four distinct states matter here, and they are easy to conflate:

1. Crawl access — whether Googlebot can fetch the page at all. A `robots.txt` block prevents crawling but does not by itself exclude a URL from the index. A blocked URL can still appear in Google when discovered through links, without Google reading its content.
2. Index status — whether Google has processed and stored the page. This is the gate for AI Overview eligibility.
3. Snippet eligibility — whether an indexed page is eligible to appear with a snippet in Search. Google lists this as a separate requirement for supporting links in AI features. Indexing alone is not enough.
4. AI-feature inclusion — whether an indexed, snippet-eligible page is actually selected for a given AI Overview. Eligibility does not guarantee inclusion.

The practical takeaway: fixing crawl access is necessary but not sufficient. You need to confirm index status independently.

02A hypothetical example: a page excluded by noindex

Imagine that Search Console URL Inspection reports a public pricing page as excluded by a `noindex` directive. This is a hypothetical example, not an observed client result.

The team now has a specific diagnostic to investigate. It did not infer non-indexation from a missing search result. First, establish why the directive exists. If the page is intended for public search and the exclusion was accidental, remove the directive and make sure Googlebot can crawl the page to see the change. Google must be able to read noindex directives; a robots.txt block can prevent that.

Request indexing through URL Inspection and check the subsequent status. Removing a directive or submitting a request is an action, not proof that indexing has happened. Even after indexing and snippet eligibility are confirmed, inclusion in an AI Overview remains a separate outcome.

03What to check on your own website

Work through these checks in order before drawing conclusions about AI Overview eligibility:

1. Inspect the specific URL Use Google Search Console URL Inspection to check the specific page. Record the reported index status and reason, then investigate crawl restrictions rather than guessing from a search result.

Also check `robots.txt` directly. Fetch `yourdomain.com/robots.txt` and look for `Disallow` rules that match your page path. A blocked path can silently prevent the `noindex` tag from being processed, as Google's crawling documentation explains.

1. Check for noindex signals Inspect the page source for `<meta name="robots" content="noindex">` or an `X-Robots-Tag: noindex` HTTP header. If either is present and Googlebot can crawl the page, Google will eventually drop it from the index.
2. Verify the Google-selected canonical If your page has a `rel=canonical` pointing elsewhere, Google may treat the declared canonical as a hint rather than a rule and may index a different URL instead. URL Inspection shows which canonical Google has selected.
3. Distinguish index status from AI-feature inclusion Even after confirming a page is indexed and snippet-eligible, Google's documentation notes that eligibility does not guarantee inclusion in AI Overviews. Search Console reports AI-feature traffic under Web results; use that data rather than assumptions.

Note on other AI platforms: ChatGPT search and Perplexity use their own crawlers and operate independently of Google's index. OpenAI's OAI-SearchBot and PerplexityBot each have separate access controls. A page that is indexed by Google may still be blocked from those crawlers, or vice versa.

04Limits and common mistakes

Mistake 1: Treating a `site:` search as a complete index diagnostic An indexed URL is not guaranteed to appear in a `site:` query. A missing result therefore does not prove non-indexation. Google explains that these results are not exhaustive. Use URL Inspection to investigate the specific URL.

Mistake 2: Assuming `robots.txt` blocks prevent indexation Blocking Googlebot via `robots.txt` prevents crawling, not indexation. Google's robots.txt documentation confirms a blocked URL can still appear in results if discovered through links. The content just will not be processed.

Mistake 3: Removing legitimate exclusions to chase AI visibility Not every excluded page should be promoted in search. Before changing a directive, establish why it exists and whether the page is the intended public version. This is a practical review step, not an additional Google AI eligibility rule.

Mistake 4: Conflating crawl access with citation For ChatGPT search, OpenAI documents that crawler access does not guarantee citation. The same principle applies to Perplexity and to Google AI Overviews. Eligibility is a prerequisite, not a promise.

Mistake 5: Expecting immediate results after fixing noindex Removing a `noindex` tag and requesting a recrawl starts the process but does not instantly update index status or AI-feature inclusion. Verify the subsequent Search Console state after the next crawl cycle.

05Next step

Start with URL Inspection for the pages that matter most to prospective customers. Record index status, crawl restrictions and the Google-selected canonical before deciding what to fix.

AI Friendly offers a free AI readiness scan as a starting point for reviewing technical visibility issues. For Google index status, use Search Console directly; a readiness scan does not replace that record.

For broader context, read AI citation tracking and monitoring tools compared, or explore the website fixes and structured data articles.

Run a free AI readiness scan: https://aifriendly.agency/