AEO Footnotes

Loading search…

Snippet controls for AI answers: what publishers trade away in search

Choose between page-wide, section-level and length-based controls, then check the effects on Google, Bing and Apple search experiences.

Footnotes DeskAEO, AI search5 min read

Drafted with AI assistance from the sources in its footnotes and checked against them before publishing.

Start with the trade-off

A snippet control can limit what an engine displays or uses in an answer, but it can also reduce the preview available in conventional search. Decide first whether the goal is to restrict an entire page, withhold a particular passage, or allow a shorter preview.

For Google, a page must be indexed and eligible to appear with a snippet to qualify as a supporting link in AI Overviews or AI Mode.1 That makes a page-wide snippet ban a consequential choice: it restricts more than the text visible in an answer. If the objective is to keep a page discoverable while withholding a passage, examine the section-level option first.

nosnippet: restrict the whole page

Place a robots meta tag in the HTML <head> to apply a page-wide instruction. For example:

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

Google says nosnippet prevents a text snippet or video preview in search results and prevents the content from being used as direct input for AI Overviews and AI Mode.2 A static image thumbnail may still appear when Google considers it helpful.2 The classic-search cost is the lost text preview and video preview, even if the page itself remains eligible to appear in results.

This is a blunt option. Use it when the whole page warrants the restriction, rather than as a default for pages where only a paragraph or section should be withheld. Review important landing pages separately, since the value of a conventional search preview may differ from one page to another.

Apple also supports nosnippet: it says Applebot will not generate a description or web answer for the page, and suggestions to visit the URL will include only the title.3 Apple says it will not use data tagged nosnippet as additional context and up-to-date content when AI models generate output for display in its products and services.3 For Apple, too, the decision affects the search presentation as well as answer generation.

data-nosnippet: withhold a passage

For a narrower restriction, mark the section rather than the whole page. This leaves the rest of the page available for a preview:

<div data-nosnippet>Text to exclude from snippets</div>

Google supports the attribute on span, div and section elements to designate text that should not be used as a snippet.2 Google lists data-nosnippet among the controls for limiting information shown from pages in Search.1 The trade-off is narrower than with nosnippet: the marked passage cannot supply the search snippet, so the remaining visible text needs to give searchers a useful reason to visit.

Bing says marked content is excluded from Bing Search snippets and AI summaries, while remaining indexed and available for ranking.4 Bing also says the attribute can be applied to any HTML element.4 For an implementation intended to work across both engines, use a span, div or section rather than relying on Bing’s broader element support.

Check the boundaries of the marked section carefully. Put the attribute around the material to withhold, not around an entire container by accident. Then review the unmarked copy as a potential search preview: it should still make sense without the excluded passage.

Google treats data-nosnippet as a boolean attribute, so a value such as false does not turn it off.2 Google also advises against adding or removing the attribute on existing nodes through JavaScript, because extraction may happen before or after rendering.2 When adding DOM elements through JavaScript, Google advises including the attribute as necessary when initially adding the element to the page’s DOM.2 Google also requires valid HTML with appropriate tags closed to ensure machine-readability.2

max-snippet: set a length limit

A character limit is an alternative when the objective is to allow some preview text, but not an unrestricted excerpt. For example, put this instruction in the page’s <head>:

<meta name="robots" content="max-snippet:20">

For Google, max-snippet sets a maximum number of characters for the textual snippet and limits how much content may be used as direct input for AI Overviews and AI Mode.2 It does not affect image or video previews.2 The cost in classic search is the same constraint on the text available to explain the result, so choose the limit with the result page in mind, not only the AI use case.

Google treats max-snippet:0 as equivalent to nosnippet, while max-snippet:-1 lets Google choose the snippet length it considers most effective.2 An unparseable number causes Google to ignore the rule.2 Check the rendered tag and its value after deployment rather than assuming a malformed instruction will fail closed.

A length limit is not a substitute for marking a specific passage. If a particular section should be excluded, use a section-level control; if the concern is the amount of text generally available for a preview, consider the length cap. Where both concerns matter, review the instructions together before publishing.

Check structured data and separate permissions

A snippet restriction is not the only decision that governs information supplied to Google. Google says robots meta tag limitations generally do not affect structured data, with an exception for article.description and description values for other creative works.2 It also says structured data remains usable for search results when declared within a data-nosnippet element.2

Audit the markup alongside the visible page. Remove or adjust structured data values that should not be made available, rather than assuming that wrapping them in a restricted section is enough. Google also says the max-snippet limit does not interrupt more specific permitted uses, such as content supplied through in-page structured data or a license agreement.2

Apple has a separate page-level signal for paywalled content: pages marked isAccessibleForFree: false remain eligible for search results, but Applebot will not use their content as additional context for AI-generated output in Apple products and services.3 Apple does not support section-level hasPart markup for this signal.3 Treat that as an Apple-specific choice, not as a replacement for checking snippet controls across engines.

Deploy, inspect and allow for recrawling

For Google, a rule that can be placed in a robots meta tag can also be sent in an X-Robots-Tag HTTP response header.2 The header is useful when managing non-HTML resources or applying instructions through server configuration. Applebot also supports indexing directives in that header.3

Google says robots meta tags and X-Robots-Tag headers are discovered when a URL is crawled, so rules on a page disallowed from crawling through robots.txt will not be found and will be ignored.2 Use URL Inspection to check the HTML Googlebot received, then allow time for a recrawl and processing.1 Google says that can take from several days to several months.1

For Bing, use URL inspection in Bing Webmaster Tools to check the last crawl time.4 After deployment, review both conventional search previews and the answer experiences relevant to the site. Keep a record of the intended restriction, the implementation location and any structured data or permissions that need a separate review.

Footnotes 4

  1. 1
  2. 2
  3. 3
  4. 4

Comments 0

No comments yet.

Sign in with GitHub or Google to comment. Reading needs no account.