max-snippet & previews

How the three robots preview directives cap your text snippet, image-preview size, and video-preview length in Google and Bing — and the AI-Overview tradeoff.

First published: Jun 23, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #15 in Meta Tags#66 in On-Page#285 in Technical SEO#381 on the site
1 evidence signal on this page

max-snippet, max-image-preview, and max-video-preview are robots directives that control how much of a page Google and Bing may show in a result — they're display controls, not indexing controls, and none of them guarantees indexing, ranking, or traffic. max-snippet:[number] caps the text snippet (0 = no snippet, same as nosnippet; -1 = Google chooses; an unparseable value is ignored); max-image-preview:[none|standard|large] caps image size (large is needed for big Discover treatments, paired with images at least 1200px wide, over 300,000 total pixels, and a 16:9 ratio); max-video-preview:[seconds] caps inline video (0 = static image at most; -1 = no limit). Set them in the robots meta tag or the X-Robots-Tag header, and combine all three in one comma-separated tag — conflicting rules resolve to the most restrictive one. The catch: max-snippet:0/nosnippet strips featured-snippet eligibility and AI-Overview/AI-Mode input at the page level, a real CTR tradeoff — Google is separately testing a property-level Search Console control to exclude AI Overviews, AI Mode, and Discover's AI features without touching your snippet, but it's in limited rollout and distinct from these page directives.

TL;DR — max-snippet, max-image-preview, and max-video-preview are robots directives that cap display, not indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.. max-snippet:[number] limits the text snippet (0 = none, equal to nosnippet; -1 = Google chooses) and also limits how much content feeds AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index. and AI Mode. max-image-preview takes none / standard / large (large enables big Discover/preview images, pair with images at least 1200px wide and over 300,000 total pixels). max-video-preview:[seconds] caps inline video (0 = static image at most; -1 = no limit). Set via robots meta tagThe robots meta tag is an HTML element in a page's head — <meta name=\"robots\" content=\"noindex\"> — that tells search engines how to index and serve that page. It's crawl-then-obey: a page blocked in robots.txt is never fetched, so the tag is never seen. or X-Robots-TagThe X-Robots-Tag is an HTTP response header that carries the same indexing and serving directives as the robots meta tag (noindex, nofollow, nosnippet, and the rest). Because it lives in the header rather than the HTML, it's how you control indexing for non-HTML files like PDFs, images, and videos., combine in one comma-separated tag, most-restrictive rule wins, and the page must stay crawlable. The honest catch: at the page level, max-snippet:0/nosnippet strips featured snippets and AI-Overview/AI-Mode input together — a genuine CTR tradeoff. Google is separately testing a property-level Search generative AI control for excluding AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index./AI Mode/Discover AI without touching your snippet, but it’s in limited rollout and distinct from these directives.

Evidence for this claim Google supports max-snippet to set a text-snippet character limit and max-image-preview to set the maximum preview-image size. Scope: Google Search result presentation controls, not indexing or ranking controls. Confidence: high · Verified: Google Search Central: Robots directives Evidence for this claim Google documents that stricter snippet controls also limit eligible direct inputs and previews in certain AI search features. Scope: Current Google Search AI-feature controls; feature presentation can change. Confidence: high · Verified: Google Search Central: AI features and your website

Display controls, not indexing controls

The mental model to lock in first: these directives govern how much Google may show or use from a page, not whether the page is indexed or how it ranks. That’s what separates them from noindex (removes the page) and even from the crawl-blocking robots.txt disallow. They live in the same family as the robots meta tag and the X-Robots-TagThe X-Robots-Tag is an HTTP response header that carries the same indexing and serving directives as the robots meta tag (noindex, nofollow, nosnippet, and the rest). Because it lives in the header rather than the HTML, it's how you control indexing for non-HTML files like PDFs, images, and videos. header, and they’re the graduated version of the binary nosnippet / data-nosnippet — instead of “snippet on or off,” you set a ceiling. Google’s own wording is consistently “maximum” and “may”: these directives set a permission ceiling on what Google may display if it decides to show something at all. None of them guarantees indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., ranking, that a preview of any size will actually appear, or any particular amount of traffic or click-through — they only cap the upper bound.

The three directives cap different parts of the search preview; none of them removes the page from the index. Source: Patrick Stox

The page remains eligible for indexing and ranking. max-snippet:N caps the text snippet to N characters; 0 allows no text snippet and -1 lets Google choose. max-image-preview allows none, standard, or large image previews. max-video-preview:N caps inline video to N seconds; 0 allows a still frame at most and -1 sets no limit. The directives must be crawlable, and restrictive snippet settings can also reduce featured-snippet and AI-feature use.

© Patrick Stox LLC · CC BY 4.0 ·

max-snippet — the text snippet

max-snippet:[number] caps the textual snippet to N characters. The two special values are the ones to memorize:

  • max-snippet:0 — no text snippet. Google’s spec is explicit that this is equivalent to nosnippet.
  • max-snippet:-1 — Google chooses the snippet length it believes is most effective.

It does not touch image or video previews — those have their own directives. The load-bearing modern detail is that max-snippet also governs AI features. Per Google’s spec, it applies across web search, Images, Discover, Assistant, AI Overviews, and AI Mode, and “will also limit how much of the content may be used as a direct input for AI Overviews and AI Mode.” There’s a carve-out: this limit doesn’t apply where a publisher has separately granted permission for the content (for instance, in-page structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories., or a license agreement with Google).

The practical consequence — and the thing worth being honest about — is that these page-level directives don’t give you a clean “opt out of AI Overviews only” lever. max-snippet and nosnippet cut your AI-Overview/AI-Mode input and your normal text snippet at the same time; you can’t keep one and drop the other with these tags alone.

That’s changing at a different layer, though: Google is rolling out a Search generative AI control in Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. — a property-level setting, separate from these page directives, that lets you include, exclude, or inherit your site’s participation in AI Overviews, AI Mode, and generative AI features in Discover, without touching your normal snippet. As of this writing it’s in a subset rollout (available to some site owners, not all yet), and an exclusion can take one to two days or longer to propagate. It’s also distinct from Google-Extended, which controls model training, not what appears in these Search AI features. So there are now three separate levers: the page-level preview directives covered on this page (bundle snippet + AI-input control), the property-level Search generative AI control (AI-only, no snippet impact, but still rolling out), and Google-Extended (training only).

max-image-preview — the image preview

max-image-preview:[setting] caps the image preview size, with three values:

  • none — no image preview.
  • standard — a default-size preview may be shown.
  • large — a larger preview, up to the width of the viewport, may be shown.

If you don’t set it, Google may show a default-size preview. The reason most people reach for this is large: it’s the standard recommendation for Google DiscoverGoogle Discover is a personalized, mobile-first content feed built into the Google app, Chrome's mobile New Tab page, and google.com that surfaces articles and videos based on a user's interests and activity — not a response to a search query. There's nothing to 'rank' for in the traditional sense; eligibility is governed by Discover's content policies plus the same helpful-content, image, and page-experience signals Google Search already uses. and other large-image treatments. Google’s current Discover image guidance is specific — a relevant, high-quality image at least 1200px wide, with more than 300,000 total pixels, in a 16:9 aspect ratio — and it’s enabled by max-image-preview:large or AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.. Frame it honestly though: eligibility, the large permission, which image gets selected, and whether Discover actually shows it are four separate things, and Google is explicit that being eligible to appear in Discover isn’t a guarantee of appearing. large isn’t a ranking factor.

max-video-preview — the video preview

max-video-preview:[number] caps the inline video preview to N seconds:

  • 0 — at most a static image may be used (governed by your max-image-preview setting). Note this is “a still frame at most,” not “no video media whatsoever.”
  • -1 — no limit.

Unset, Google decides the preview length.

One edge case worth knowing for both max-snippet and max-video-preview: if the number you supply isn’t parseable — a non-numeric or malformed value where Google expects an integer — Google ignores that directive entirely and falls back to its default behavior for it. The 0 and -1 special values always keep their documented meaning; it’s everything else that has to parse cleanly to take effect.

Combining them in one tag

All three live in one comma-separated directive. Google’s own canonical example limits the snippet to 20 characters and allows a large image:

<meta name="robots" content="max-snippet:20, max-image-preview:large">

You can also split them across separate meta tagsMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored. — same effect. Two rules govern how they resolve:

  • Most-restrictive wins. If a page carries both max-snippet:50 and nosnippet, the nosnippet rule applies (no snippet at all). This is Google’s documented conflict-resolution rule specifically — Bing supports the same three directives (see below), but its combined-tag conflict handling and any AI-product effects aren’t documented the same way, so verify per engine rather than assuming identical behavior.
  • The page must be crawlable. These are read during crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., so they aren’t governed by a robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. disallow — but if you do block the page in robots.txt, Google never fetches it and never sees the tag. Don’t pair these with a disallow.

A couple of realistic recipes:

<!-- Publisher who wants maximum SERP + Discover surface -->
<meta name="robots" content="max-snippet:-1, max-image-preview:large, max-video-preview:-1">

<!-- News site wary of feeding long passages into AI features -->
<meta name="robots" content="max-snippet:[low number], max-image-preview:large">

Robots meta tag vs X-Robots-Tag

Same directives, two delivery mechanisms:

  • Robots meta tagThe robots meta tag is an HTML element in a page's head — <meta name=\"robots\" content=\"noindex\"> — that tells search engines how to index and serve that page. It's crawl-then-obey: a page blocked in robots.txt is never fetched, so the tag is never seen. — an HTML element in the page <head>. Best for individual pages.
  • X-Robots-Tag — an HTTP response header set at the server (Apache, Nginx, or a CDN). This is how you apply max-image-preview / max-video-preview caps to non-HTML files like images, PDFs, and video that have no <head>, and how you apply a rule in bulk or site-wide.

The rules are case-insensitive, and you can verify a live header with curl -I against the public URL. Watch for a CDN serving a different header than your origin.

How to test

  • URL Inspection (Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.) — check the HTML GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. actually received, so you can confirm the tag is present and not stripped by a plugin or CDN.
  • curl -I — confirm the X-Robots-Tag header is being sent for the header approach.
  • Don’t robots.txt-block the page — if Google can’t crawl it, none of these caps are read.

The tradeoff, and a bit of history

These shipped on September 24, 2019 (effective mid-to-late October 2019). Google’s own announcement doesn’t say why — but the widely reported industry driver was the EU Copyright Directive: France’s 2019 implementation pushed Google to give publishers granular control over how much preview content appeared, in lieu of paying for snippets. (That EU-origin framing is industry-sourced, not from Google’s post — so treat it as context, not a Google statement.)

The honest bottom line: capping snippets is not free. As Glenn Gabe documented when he tested the preview controls, applying nosnippet removed his content from an AI Overview — but it also left his normal search listing with no description, which he expected would hurt click-through rate. Barry Schwartz flagged the featured-snippet angle back in 2019: drop below the minimum text a featured snippet needs and you can fall out of that position. So max-snippet:0 / nosnippet is a real CTR decision at the page level, not a tidy AI-only opt-out — that separate lever now exists as the property-level Search generative AI control described above, still in limited rollout. For the all-or-nothing on/off control and the surgical, per-section variant, see the nosnippet / data-nosnippet article; the robots meta tag and X-Robots-Tag header pages cover the full directive set.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.