Claim and evidence
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.
No dated example yet. Treat this tactic as a hypothesis.
Primary
The company or founder describes the tactic and its result themselves: own blog, talk, filing.
Working · 2025-05 Google documentation and Search Central post (May 2025)
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
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
- Audit robots meta and data-nosnippet usage on key pages
- Decide per page type whether exposure or click protection matters more
- Remember nosnippet is the only guaranteed block for featured snippets
- Compare impressions and clicks after changes
Ways to run it
Design options to test, not promised results.
- Option AOpen by default
Leave snippet controls off on most pages so they can appear in AI features and featured snippets.
- Option BProtect selected blocks
Use data-nosnippet only on sections you do not want quoted, keeping the rest of the page eligible.
- 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?
Google documentation and Search Central post (May 2025) source
Risks
- Blocking snippets reduces visibility
- Google-specific; other engines have their own controls
Sources
- developers.google.com
“More restrictive permissions will limit how your content is featured in our AI experiences.”
✓ quote checked word-for-word on the page - developers.google.com
“You can't.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (acq-search)