The nosnippet Meta Tag: Controlling What Google Shows

Google decides, on its own, how much of your page to show under the blue link in a search result: a passage of body text, sometimes an image thumbnail, occasionally a video frame, stitched into a preview the searcher reads before they click. Most of the time that default is exactly what you want. Sometimes it isn't. A subscription article where a two-sentence excerpt gives away the paid paragraph. A pricing table that goes stale within a month. A disclaimer block nobody should quote out of context. Or a query where handing the full answer to the searcher directly in the results, or inside an AI-generated overview, removes any reason to click through at all.

Four controls let you adjust what Google is allowed to show, ranging from all-or-nothing to surgical: nosnippet, max-snippet, max-image-preview, and the HTML attribute data-nosnippet. Each targets something slightly different — the whole text snippet, a character budget, image size, or a single block inside the page — and each carries a real cost in what your result looks like next to competitors. This covers what each one actually controls, how they combine, and when giving something up is worth it. (Delivering a robots directive via an HTTP header instead of a meta tag is a separate mechanism, not covered here.)

What Google Shows Without Any Directive

Before restricting anything, it's worth knowing the default you're restricting away from. With no robots meta tag at all, or none of these specific values inside one, Google treats a page as fully open: no character limit on the text snippet, the largest image preview it offers, and no cap on video preview length. The text itself isn't necessarily the meta description you wrote — Google's systems select whichever passage best answers the specific query, and that choice can shift between searches for the same page. None of the four directives below change that selection logic. They only cap what the selected passage or image is allowed to look like once chosen, or forbid the selection outright.

nosnippet: No Text, No Video Preview, at All

Setting content="nosnippet" in the page's robots meta tag tells Google not to build any text snippet or video preview for that result. What remains is the title and the URL, with nothing describing what's on the page underneath. A static image thumbnail may still appear in some result types even with the directive active; nosnippet is specifically about text and video preview, not every visual element a result can carry.

nosnippet is not noindex, and the difference matters more than the similar names suggest. A nosnippet page is still crawled, indexed, and fully eligible to rank; it simply shows up bare, title and link only. The two often get set together out of habit rather than intent, and the mix-up tends to surface later as a findable page that mysteriously stopped earning clicks.

Situations where losing the description entirely earns its keep:

• Pages behind a metered or hard paywall, where even a short excerpt discloses the paragraph you're charging for.
• Boilerplate legal or compliance pages, where an out-of-context fragment shown in a result could misstate the page's actual position.
• Pages that exist to be linked to rather than searched for their own text — a redirect landing page, a printable coupon, an internal reference document that ranks by accident.

max-snippet: A Length Dial Instead of a Switch

max-snippet:[number] replaces the all-or-nothing choice with a character budget: the number is the maximum number of characters Google may use for the textual snippet. Two values act as shortcuts worth memorizing. max-snippet:0 removes the text snippet entirely, functionally the same as nosnippet for text alone. max-snippet:-1 is unlimited, and also what applies by default when the directive is absent.

Two limits are worth knowing. First, the cap governs only the plain-text snippet; image and video preview length are set independently through the two directives below it. Second, per Google's own documentation, the character cap doesn't apply where you have separately granted permission to use the content, for example through structured data markup.

• A short budget, on the order of fifty to a hundred characters, gives a searcher just enough to confirm relevance — a headline-length teaser — without reproducing the paragraph that actually answers the question.
• Setting a different number per template is normal practice. Product pages, blog posts, and legal pages have no reason to share one value.

max-image-preview and max-video-preview: The Same Idea for Other Media

The image and video equivalents work on the same principle with their own value sets. max-image-preview:[none|standard|large] controls the largest image size Google may use in the result: none suppresses the image preview altogether, standard keeps it at a smaller default size, large allows the biggest preview Google offers for that result type. max-video-preview:[number] caps a video preview to that many seconds, with 0 producing a static frame instead of a moving preview and -1 leaving it unlimited.

All of these directives can sit inside the same content attribute, comma-separated: content="max-snippet:150, max-image-preview:large, max-video-preview:0" is one valid meta tag that trims the text, keeps large images, and reduces any video preview to a still frame. Setting one does not quietly constrain the others.

• max-image-preview:none matters most for pages carrying images whose licensing you don't control tightly enough to want reproduced at large size on someone else's results page.
• Large-image participation in Google Discover's feed generally requires max-image-preview set to large; setting it to none or standard keeps a page out of large visual cards there, and none also removes the image preview in ordinary web search.

data-nosnippet: Excluding One Block, Not the Whole Page

The three directives above sit in the robots meta tag and apply to the entire document. data-nosnippet is different in kind: it's an HTML attribute placed directly on a span, div, or section element, telling Google not to draw snippet text from inside that specific block while leaving the rest of the page fully eligible. Written out, it looks like a span element carrying the attribute with no value required — data-nosnippet on its own is enough — and it only has an effect on those three element types.

This solves a problem nosnippet can't touch: a page that's fine to excerpt almost everywhere, except for one paragraph. A price that changes weekly. A disclaimer. A quoted passage you're not the rights-holder for. A boilerplate author bio repeated on every article. Wrap only that block, and Google remains free to build a snippet from everything else on the page.

• If data-nosnippet ends up covering every block of extractable text on a page, the practical outcome matches nosnippet: nothing is left for Google to build a snippet from.
• It doesn't need to align to a sentence boundary. Apply it to a div or section wrapping a whole table, widget, or sidebar just as easily as a single span around one line of text.

What Blocking a Snippet Costs, and When It's Worth Paying

Removing or shrinking a snippet has a genuine downside. For an ordinary informational or competitive query, the preview text is frequently what convinces someone to click your result instead of the one sitting above or below it. A bare title-and-URL listing next to five competitors carrying full descriptions is not likely to hold its share of clicks. That cost is exactly why these directives belong at the URL level, not as a sitewide default — reaching for nosnippet across an entire blog because one legal page needed it will quietly cost traffic everywhere else on the site.

The other side of that trade shows up precisely where a snippet, a featured snippet box, or an AI-generated overview would fully satisfy the search without a visit. Since Google stopped giving a featured snippet a second, separate listing further down page one — a change made in January 2020 — occupying that answer box is the same listing as your ordinary result, not an additional one. Removing a page's snippet eligibility also removes its eligibility to occupy that box with its own text, for better or worse depending on whether the box was sending clicks your way or absorbing them before a visit happened.

Google's own documentation on its AI-generated overviews states that pages eligible to be used as sources follow the same snippet controls that apply to ordinary search results, nosnippet and data-nosnippet included. Marking a page, or a specific block, off-limits to snippets keeps that content out of a generated overview's text too, not only out of the classic snippet. It's the closest available lever for "the full answer appears above my link and nobody clicks," paid for by losing the ordinary preview text on every other query where an overview was never going to appear anyway.

• Good candidates for the trade: pages whose real value sits behind the click — a tool, a calculator, an interactive form — rather than in the paragraph itself. The snippet was never going to be the deciding factor for these.
• Weak candidates: general informational posts competing on a crowded results page, where the descriptive line is doing genuine persuasive work against near-identical competitors.

Mistakes That Undo the Directive

A handful of implementation slips account for most cases where someone sets one of these values and later finds the result unchanged, or changed somewhere they didn't intend.

• Confusing nosnippet with noindex, then being surprised the page still ranks. It's supposed to — only the description text is gone, not the listing.
• Assuming max-snippet also limits the image preview. It doesn't. Set max-image-preview separately if the thumbnail needs constraining too.
• Applying the directive only to a duplicate or parameterized variant of a URL, and expecting it to affect the canonical version Google actually chooses to display. The directive has to sit on the URL Google is showing, not a near-copy of it.
• Wrapping a data-nosnippet attribute around a container far larger than intended — an entire page-body div, say — which quietly reproduces the effect of a full nosnippet without anyone deciding to remove the whole snippet.
• Expecting the change to show up immediately. The directive changes what Google is allowed to build the next time it processes the page; the snippet already cached in a result updates on Google's own recrawl schedule, not on the moment you publish the change.

Confirming It Took Effect

Because the effect is only visible inside the search result itself, and depends on a recrawl to appear, verify the mechanism before waiting on the outcome. View the page's rendered source, or run a live test through Search Console's URL Inspection tool, and confirm the exact directive string shows up in the meta tag's content attribute, or on the intended element — a templating bug that silently outputs an empty content value, or drops the attribute on certain page types, is the single most common reason a directive appears not to be working at all. Once the markup itself is confirmed correct, a direct site search for that URL will eventually show the updated, or removed, snippet once Google has recrawled and reprocessed the page; there's no way to force that refresh on demand, so budget days, not minutes, before concluding it didn't take.