Does Google’s nosnippet Make a Page Ineligible for AI Overviews?

Yes, in an important but specific sense. Secondary explanations of Google’s guidance report that a page must be indexed and eligible to appear in Search with a snippet to appear in AI Overviews or AI Mode. They also quote Google’s narrower statement: nosnippet prevents the page’s content from being used as a direct input for those features. That is a restriction on content eligibility, not simply a request for a shorter AI answer. It is not a promise that the URL can never be linked or mentioned in an AI response. (Eligibility explanation; direct-input wording)

For a publisher, the first question is therefore not just Do I want this text in an AI Overview? It is Am I willing to remove this page’s text snippet from ordinary Google Search results too?

The whole-page choice

nosnippet is a page-level control. A page using it can remain indexed and can rank, but its text snippet is suppressed in ordinary Search results as well as restricted in the AI features described above. max-snippet:0 is reported as equivalent to nosnippet; it is not a way to keep a conventional snippet while opting out of direct AI Overview input. (Page-level behavior; equivalence)

Here is an illustrative example, not tested code, for a page whose publisher intends to apply the control to the entire page:

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="robots" content="nosnippet">
  <title>Sample shipping policy</title>
</head>
<body>
  <main>
    <h1>Sample shipping policy</h1>
    <p>Example policy text for this hypothetical page.</p>
  </main>
</body>
</html>

The tag belongs in this example page’s head; it does not mark only the policy paragraph. If the ordinary Search listing benefits from a description of the policy, losing that description is part of the decision, not a separate technical problem to fix afterward. A reported nosnippet case also observed descriptions disappearing from normal search listings when content was removed from AI-driven features. That report does not establish what will happen to every page or how quickly Google will process a change.

If only one passage needs the boundary

data-nosnippet is the more precise option when the publisher wants to mark a particular passage rather than suppress snippets for the entire page. It is a boolean attribute supported on span, div and section elements; the marked subtree is the relevant scope. It is not a whole-page opt-out. (Passage-level details)

For example, if the rest of a hypothetical policy page should remain available for snippets, the publisher could mark just this sample passage:

<section data-nosnippet>
  <h2>Sample passage excluded from snippets</h2>
  <p>This is illustrative policy text, not an actual shipping commitment.</p>
</section>

Keep the HTML valid: an unclosed element can change how much content falls inside the marked section. The reported implementation guidance also cautions against adding or removing data-nosnippet later with JavaScript. Have the attribute present when the element is first created. This passage-level example is an alternative to the page-wide example above, not something to add beneath a whole-page nosnippet tag in the hope of narrowing it.

What a check can establish

Inspect the HTML of the example page you actually publish. If you chose the whole-page option, confirm that <meta name="robots" content="nosnippet"> is present in its head. That checks the implementation shown here; it does not show that Google has processed the change. If you chose the passage-level option, check that data-nosnippet is on the intended element, that its HTML boundaries are valid, and that the attribute is there when the element is first created. Those checks establish configuration scope, not observed inclusion or exclusion in an AI Overview.

Then reconsider the ordinary Search listing you are willing to have. A page remaining indexed does not prove its content was used as direct AI input; a missing AI Overview citation does not prove the control caused that absence. Neither observation substitutes for checking the markup and the intended boundary.

Because this is a consequential Search setting, check current Google Search Central documentation for the snippet-eligibility requirement, the exact direct-input wording, and the implementation details before changing an important page. The linked explanations above report Google’s guidance; they are not an independent verification of its current wording.