A page can appear in ordinary Google results and still be ineligible as a supporting link in AI Overviews or AI Mode. Google requires both indexing and snippet eligibility. A directive in the HTML or an HTTP response header can block the second condition without removing the page from ordinary results. Google’s AI features documentation

A directive delivered only in an HTTP header will not appear in the page’s HTML. You can inspect it in your browser’s developer tools, under the document request’s response headers. Chrome’s instructions

What Google Actually Requires Before a Page Can Appear in AI Overviews

Google requires a page to be indexed and eligible for a Search snippet before it can qualify as a supporting link in AI Overviews or AI Mode. No special schema or AI text file unlocks that eligibility. Meeting the requirements does not guarantee that Google will select the page. Google’s requirements

Read that as two separate checks. Being indexed answers one question. Permission to show a snippet answers another.

A third check concerns the Search generative AI control in Search Console. Google says the Search generative AI control was rolled out to all websites worldwide as of August 31, 2026. The control governs inclusion in AI Overviews, AI Mode, and generative AI features in Discover.

Inclusion is the default, but a property can inherit an exclusion from a parent. Check the effective setting for the URLs you are auditing. Google states that this control is not used as a ranking or inclusion signal elsewhere in Search. Changing it generally takes a few days to take effect. Control documentation

Which Controls Restrict Snippets and AI Visibility

These controls affect different parts of the process.

noindex instructs Google to exclude the page from Search. Google must crawl and process the instruction before it takes effect. That prevents the page from satisfying the indexing requirement. Google's noindex guidance

nosnippet blocks text snippets and video previews. Google also says it prevents direct content input into AI Overviews and AI Mode. Robots specification

max-snippet:0 is equivalent to nosnippet. Positive values limit text usage rather than automatically excluding the page. Google documents exceptions for separately permitted uses, including structured data and licensing arrangements. Snippet limits

data-nosnippet excludes selected text from snippets. It works on span, div, and section elements; it does not itself exclude the rest of the page. Google's explanation of snippet controls

noarchive is no longer used by Google Search. It is not an AI visibility control. Historical directives

X-Robots-Tag is the HTTP header that carries directives. For example:

X-Robots-Tag: nosnippet

When applicable rules conflict, the more restrictive rule takes effect. A max-snippet:-1 meta tag does not cancel a nosnippet header. The same principle applies if their locations are reversed: the restriction matters, not whether it arrived in HTML or a header. Header reference

What Search Console Can Tell You

The Page indexing report can identify exclusion caused by noindex. Do not assume its reason identifies whether the directive came from HTML or a header; inspect the response to establish that. Page indexing documentation

An indexed status does not establish snippet eligibility. It answers the indexing question, which is only part of this audit.

The generative AI performance report shows impressions and lets you examine pages, countries, dates, and devices. Google says the report may not appear when a site has insufficient impressions. Missing data does not identify the cause of missing visibility. AI performance report documentation

Check the permissions directly before interpreting a lack of impressions as a content problem.

Where to Look for These Directives

Check the hosting platform, the site’s templates, and any server or delivery rules that modify responses. These are places to investigate, not evidence that a restriction was added accidentally.

Vercel documents automatic X-Robots-Tag: noindex headers on preview deployments and outdated production deployments. A custom domain assigned to a non-production branch is an exception: Vercel omits that automatic header. A staging environment using such a domain can therefore be indexed unless another control prevents it. Vercel's documentation

Kajabi’s documented landing-page option to hide a page from search adds noindex, nofollow. This is an indexing control, not evidence of an unexpected nosnippet directive. Kajabi's documentation

On a server you manage, inspect response-header configuration as well as HTML templates. Rules can target individual files or URL patterns, so checking the homepage alone is insufficient. Google’s server configuration examples

How to Check a Published Page

Start with a real published URL. Use a GET request and follow redirects:

curl -sS -L -D - -o /dev/null 'https://example.com/your-page'

The command prints response headers while discarding the body. Redirects produce additional header blocks. Inspect the final response’s status and any X-Robots-Tag headers. Unlike this command, curl -I sends a HEAD request. curl documentation

A header can name a crawler:

X-Robots-Tag: googlebot: nosnippet

The prefix identifies who should obey the rule. It does not make the header disappear from ordinary requests. Conditional delivery based on the incoming User-Agent is a separate server configuration. Changing your request’s User-Agent can help compare responses, but it does not reproduce a request from Google’s infrastructure. Crawler-specific header syntax

Then scan the HTML:

curl -sS -L 'https://example.com/your-page' \
  | grep -inE 'robots|googlebot|nosnippet|max-snippet'

Every match needs reading. The pattern also catches words in body text, comments, and scripts. Check the actual robots and googlebot meta tags and any elements carrying data-nosnippet. This is an initial text scan, not a complete HTML audit.

Repeat the header check for representative URLs from different templates and paths. For PDFs, inspect the HTTP headers; the HTML scan does not apply.

In Search Console’s URL Inspection tool, open “View crawled page” to examine stored HTML and HTTP headers where available. A live test checks the current page and may differ from the indexed version. This matters for pages whose rendered HTML differs from the initial response: curl does not execute JavaScript. URL Inspection documentation

Google must be allowed to crawl a page to discover its directives. A robots.txt block can prevent it from seeing a new or changed rule; blocking crawling is not a substitute for noindex. Google's crawl-access guidance

After a fix, Google must recrawl and process the change. You can request a recrawl, but that does not guarantee immediate processing or inclusion. Recrawl guidance

Why a Passing Schema Test Is Not Enough

Google documents structured-data exceptions to preview restrictions, including data within data-nosnippet elements. Those exceptions do not make a schema check an AI eligibility test. Structured-data preview rules

Valid markup does not override noindex, and a passing Rich Results Test does not guarantee a rich result. Check the page's indexing status and visibility controls separately from its structured data. Google's structured-data requirements

FAQ

Q: Does nosnippet block AI Overviews?

A: Google says it prevents direct content input into AI Overviews and AI Mode. Snippet eligibility is also required for supporting links. Google’s specification

Q: Does max-snippet stop my page appearing?

A: Zero is equivalent to nosnippet. Positive values restrict text usage, subject to Google's documented exceptions; they are not automatic page exclusions. Snippet limits

Q: What is the difference between noindex and nosnippet?

A: noindex prevents inclusion in Search once processed. nosnippet restricts previews without itself preventing an ordinary listing. Neither setting guarantees rankings or traffic. Indexing controls, snippet controls

Q: How do I check for an X-Robots-Tag header?

A: Run curl -sS -L -D - -o /dev/null 'https://example.com/your-page' and inspect the final response block. Then compare with the response available in URL Inspection.

Q: Does blocking Google-Extended remove my site from AI Overviews?

A: No. Google-Extended is not the control for inclusion in Google Search. Check Search indexing and preview controls, along with the Search Console AI setting. Google’s crawler documentation

Q: Can I stay in normal search results but opt out of AI Overviews?

A: Yes. The Search generative AI control manages participation in the covered AI features without using that choice as a ranking or inclusion signal elsewhere in Search. Unlike nosnippet, it does not require suppressing ordinary text snippets. Control documentation

Q: Will an indexed status tell me whether a page is eligible for a snippet?

A: No. Inspect the relevant HTML and response headers, and check the effective Search Console AI setting. An indexing result alone does not establish AI eligibility.

Q: If my schema validates, is the page eligible?

A: Validation alone cannot establish that. Check indexing, snippet permissions, and the Search Console AI control as separate conditions.

Before rewriting a page that is missing from AI answers, check its snippet permissions and Search Console AI setting. Rewriting cannot override a blocking directive or an exclusion setting.

AI Visibility Studio helps websites become easier for AI systems to find, read, and cite. aivisibilitystudio.com