Fix Snippet-Blocking Robots Directives
One or more of your pages is telling Google not to show a text or image preview of its content. Directives like nosnippet, max-snippet:0, max-image-preview:none, and the data-nosnippet attribute suppress the snippet under your search listing, remove your thumbnail and image rich-result eligibility, and block the page from featured snippets and from Google AI Overviews and AI Mode. Google's docs are explicit: these same directives control what AI Overviews may quote from your page. Unless you deliberately want a page kept out of previews, remove or relax them so Google can display and cite your content.
What this means
This warning means a page carries a robots directive that limits how much of its text or imagery Google may show in a preview. It appears in four forms:
- nosnippet — a value in a
robots/googlebotmeta tag orX-Robots-Tagheader that tells Google to show no text snippet at all for the page. - max-snippet:0 — the same outcome expressed as a length limit of zero characters. A positive number caps snippet length;
-1lets Google choose the length (no limit). - max-image-preview:none — no image thumbnail may be shown, which also removes the page from image-based previews and rich results. The permissive values are
standardandlarge. - data-nosnippet — a boolean HTML attribute you place on a
span,div, orsectionso Google excludes just that block from the snippet while the rest of the page stays snippettable.
These are all valid, documented directives. The audit flags them because they are usually left in by accident, such as a stray SEO-plugin toggle, a copied header block, or a leftover staging config, on pages you actually want visible and quotable. The page can still be crawled, indexed, and ranked. It just cannot present a useful preview.
Why it matters
The snippet is the part of your search listing that earns the click. Suppress it and Google falls back to a bare title and URL or guessed text, which gives searchers little reason to choose your result and drags down your click-through rate. max-image-preview:none costs you the thumbnail, the large preview, and eligibility for the image-driven results that carousels and Discover rely on.
The bigger cost now is answer engines. Google's own documentation states that nosnippet, max-snippet, and data-nosnippet govern whether your content can be used as a direct input for AI Overviews and AI Mode, and that they also control featured snippets. A page with nosnippet or max-snippet:0 is crawled and indexed but cannot be quoted in an AI Overview or shown as a featured snippet. data-nosnippet fences off a specific passage, often your clearest answer paragraph, so it never becomes the sentence Google surfaces and attributes to you. If your goal is to be cited by Google's AI features, these directives work directly against it.
One caveat worth knowing: these are Google-specific preview controls, not a universal AI opt-out. ChatGPT, Perplexity, and other assistants are governed by their own crawler user-agents in robots.txt, not by nosnippet. So removing these directives is about winning back Google Search previews, featured snippets, and AI Overviews. There is no ranking penalty here, which is why it is a warning rather than an error, but it quietly caps your visibility and CTR on every affected page.
How to fix it
- 1
Find where the directive is set
There are three places to check: the page's
<head>for a<meta name="robots">or<meta name="googlebot">tag, the HTTP response for anX-Robots-Tagheader, and the page body fordata-nosnippetattributes. View source and search fornosnippet,max-snippet, andmax-image-preview. For the header, runcurl -sI https://example.com/page | grep -i x-robots-tagor read the response headers in your browser's Network tab. A directive in the HTTP header applies alongside the meta tag, so if both exist, the most restrictive rule wins. Check both before assuming you found the source. - 2
Remove or relax the meta robots directive
If you want normal previews, the cleanest fix is to drop the restrictive values and let Google use its defaults. If you keep a robots meta tag for other reasons such as
index, follow, set the snippet controls to permissive values: removenosnippet, usemax-snippet:-1for no length limit, and usemax-image-preview:largefor a full-size thumbnail. A page you want fully visible should read<meta name="robots" content="index, follow, max-image-preview:large">or carry no robots meta tag at all, since the defaults already allow previews. - 3
Fix the X-Robots-Tag header at the server or CDN
If the directive lives in an HTTP header, editing the HTML will not help. You have to change where the header is emitted. In Apache, look in
.htaccessor the vhost for aHeader set X-Robots-Tagline. In Nginx, checkadd_header X-Robots-Tagdirectives. On Cloudflare, check Transform Rules and any Workers that set response headers. Remove the header for pages that should be previewable, or scope it so it only applies to paths you genuinely want suppressed such as PDFs, thank-you pages, or internal search results. - 4
Strip stray data-nosnippet attributes
Search your templates and content for
data-nosnippet. It is often applied to a wrapper element such as a main content div, an article body, or a pricing table, which silently removes your best answer text from previews, featured snippets, and AI Overviews. Remove it from anything you want quoted. Keep it only on fragments you deliberately want excluded, like a boilerplate legal disclaimer, a 'last updated' stamp, or a live price you do not want frozen in a stale snippet. Note that Google supports it only onspan,div, andsectionelements. - 5
Decide intentionally per page type
This directive is not always wrong. Paywalled content, gated resources, staging URLs, and utility pages such as cart, account, and internal search are legitimate places to suppress snippets. Make the choice deliberate rather than global: apply restrictions only to those templates and confirm your money pages such as articles, product pages, landing pages, and docs carry no snippet limits. Map which templates emit the directive before you bulk-edit.
- 6
Re-crawl and validate
After the change, fetch the URL again and confirm the directive is gone from both the HTML and the response headers. Use Google Search Console's URL Inspection tool to see the version Google has indexed and request re-indexing. The snippet will not reappear until Google re-crawls, so check the live SERP for the affected query a few days later to confirm the text and image preview are back, then re-run your audit to clear the warning.
Example
<!-- FLAGGED: these suppress snippets and thumbnails -->
<meta name="robots" content="index, follow, nosnippet">
<meta name="robots" content="max-snippet:0, max-image-preview:none">
<!-- and as an HTTP header (applies on top of the meta tag): -->
<!-- X-Robots-Tag: nosnippet, max-image-preview:none -->
<!-- and inline, blocking a specific block from previews and AI Overviews: -->
<div data-nosnippet>
Your best answer paragraph is hidden from Google here.
</div>
<!-- FIX: allow full text snippet + large image preview -->
<meta name="robots" content="index, follow, max-image-preview:large">
<!-- or omit the robots meta tag entirely; defaults already allow previews -->
<!-- Keep data-nosnippet ONLY where suppression is intended
(valid on span, div, and section elements): -->
<span data-nosnippet>Last updated: 2026-07-07</span>Restrictive directives (what the audit flags) versus permissive equivalents. Remove the top set or replace it with the bottom set on pages you want previewed and cited.
Platform-specific steps
In Yoast, open the post's SEO settings, go to the Advanced section, and check the 'Allow search engines to show this content in search results' toggle and the snippet meta controls. A stray 'No Snippet' setting here is the usual cause. In Rank Math, edit the post, open the Advanced tab of the SEO panel, and review the Robots Meta checkboxes such as No Snippet and No Image Index. Both plugins also have site-wide defaults under Titles & Meta or Post Types, so check those if the directive appears across a whole content type rather than one post.
Search your <head> output and any shared layout or component for the robots meta tag and remove nosnippet, max-snippet:0, and max-image-preview:none. In the Next.js App Router, set it via the metadata export: robots: { index: true, follow: true, 'max-image-preview': 'large' }. Also grep your server or middleware for code that adds an X-Robots-Tag response header, since that applies on top of the page markup.
A snippet directive is often injected at the edge rather than in your HTML. Check Rules, then Transform Rules, then Modify Response Header, and any Workers, for a rule that sets X-Robots-Tag with nosnippet or max-image-preview:none. Remove it, or add a condition so it only fires for the paths you want suppressed. Purge the cache afterward so the corrected headers are served.
These platforms rarely set nosnippet by default, so a directive usually comes from a custom code injection or an SEO app. In Shopify, check theme.liquid and any installed SEO app's per-page settings. In Wix and Squarespace, look under the page's SEO panel for a 'hide from search results' or 'no snippet' style toggle, plus any custom header code you have injected. Remove the offending directive at the source rather than overriding it downstream.
Frequently asked
No. nosnippet, max-snippet:0, and max-image-preview:none only control the preview shown under your listing. The page is still crawled, indexed, and eligible to rank. What you lose is the text snippet and thumbnail that earn the click, plus eligibility for featured snippets and image rich results. Only noindex removes a page from Search.
nosnippet is a page-level directive, set in a robots meta tag or X-Robots-Tag header, that suppresses the snippet for the whole page. data-nosnippet is an HTML attribute you place on a single span, div, or section to exclude just that block while the rest of the page stays previewable. Use data-nosnippet for surgical control, and remove page-level nosnippet when you want the page shown normally.
Use max-snippet with a positive number instead of 0. For example, max-snippet:160 caps the text snippet at roughly 160 characters. To allow an unlimited-length snippet, use max-snippet:-1 or omit the directive. Google also notes that lowering max-snippet is the recommended way to reduce how often a page appears as a featured snippet while keeping a regular snippet. Here, -1 means 'no limit' and 0 means 'no snippet at all', which is what the audit flags.
Yes. Google's documentation states that nosnippet and max-snippet control whether your content can be used as a direct input for AI Overviews and AI Mode, and they also govern featured snippets. A page with nosnippet or max-snippet:0 can be crawled and indexed but will not be quoted in an AI Overview or shown as a featured snippet. data-nosnippet excludes specific passages. Remove these directives from pages and paragraphs you want surfaced.
Google treats the directive as a maximum, not a guarantee. It still decides whether a thumbnail helps the query. Confirm there is no conflicting X-Robots-Tag header still setting max-image-preview:none, that the image is crawlable and not blocked in robots.txt, and that the page has been re-crawled since your change. Use URL Inspection to check the version Google currently has.
Does your site have this issue?
Run a free, AI-powered audit and we’ll flag this and 150+ other checks in about a minute. No signup.