Working · 2025-05PrimaryAcquisitionAEO / AI search

Snippet controls and AI feature exposure

Be aware that restrictive snippet and preview settings (nosnippet, data-nosnippet, max-snippet) limit how content appears in Google's AI features and featured snippets.

Claim and evidence

The claimBe aware that restrictive snippet and preview settings (nosnippet, data-nosnippet, max-snippet) limit how content appears in Google's AI features and featured snippets.

No dated example yet. Treat this tactic as a hypothesis.

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
Choose previewsettings per pageOpen snippets: moreAI exposureRestrict snippets:protect clicksCompare impressionsand clicks
Choose preview settings per pageOpen snippets:more AIexposureRestrictsnippets:protect clicksCompare impressions and clicks

Google uses the same preview controls for classic snippets and AI experiences, so blocking them to protect clicks also reduces visibility.

How to run it

  1. Audit robots meta and data-nosnippet usage on key pages
  2. Decide per page type whether exposure or click protection matters more
  3. Remember nosnippet is the only guaranteed block for featured snippets
  4. Compare impressions and clicks after changes

Ways to run it

Design options to test, not promised results.

  1. Option AOpen by default

    Leave snippet controls off on most pages so they can appear in AI features and featured snippets.

  2. Option BProtect selected blocks

    Use data-nosnippet only on sections you do not want quoted, keeping the rest of the page eligible.

  3. Option CPer page-type policy

    Decide by page type whether exposure or click protection matters more, then review impressions and clicks.

Dated examples

No dated example yet. Treat this tactic as a hypothesis.

Does it still work?

Workingas of 2025-05

Google documentation and Search Central post (May 2025) source

Risks

  • Blocking snippets reduces visibility
  • Google-specific; other engines have their own controls

Sources

  1. developers.google.com · Google Search Central · John Mueller · 2025-05-21
    “More restrictive permissions will limit how your content is featured in our AI experiences.”
    ✓ quote checked word-for-word on the page
  2. developers.google.com · Google Search Central · undated
    “You can't.”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (acq-search)