Dark green Relative Marketing Group cover graphic reading Snippet Controls, Explained, with a diagram of a search result snippet and nosnippet and max-snippet tag labels.

Most marketing teams have never looked at the robots meta tag on their own pages. It sits in the page source, a plugin usually writes it, and nobody touches it until something goes wrong. Yet a single word in that tag decides whether Google may quote a page in a search snippet, in an AI Overview, or in AI Mode. When an enquiry page stops appearing in AI answers while still ranking in the classic results, a snippet control is one of the first things we check.

This post covers what Google’s snippet controls actually do, the ways they break on websites that handle sensitive enquiries, and a check you can run on your own site in about five minutes.

What snippet controls are, in Google’s own terms

Google supports two levels of control over how much of a page it may show. Page-level rules go in a <meta name="robots"> tag or in an X-Robots-Tag HTTP header. Text-level rules use the data-nosnippet attribute on specific parts of a page. Both are defined in Google’s robots meta tag, data-nosnippet, and X-Robots-Tag specification, which is the document we work from rather than anyone’s summary of it.

The snippet-related rules are:

  • nosnippet: show no text snippet or video preview for the page.
  • max-snippet:[number]: use at most that many characters as a text snippet. A value of 0 is equivalent to nosnippet; a value of -1 lets Google choose the length.
  • max-image-preview:[setting]: none, standard, or large.
  • max-video-preview:[number]: the maximum length, in seconds, of a video preview.
  • data-nosnippet: an HTML attribute that keeps a specific span, div, or section out of snippets while the rest of the page stays eligible.

The same controls govern AI Overviews and AI Mode

This is the part most site owners do not expect, so it is worth stating plainly.

Google’s nosnippet rule does two things at once: it removes the text snippet from a page’s search listing, and it stops the page’s content from being used as a direct input for AI Overviews and AI Mode. Under Google’s robots meta tag specification, max-snippet:0 is equivalent to nosnippet, and when a page carries both max-snippet:50 and nosnippet, the more restrictive nosnippet wins. A business cannot keep a page in AI answers while hiding its snippet from classic results, because one control governs both.

Google’s guidance on AI features and your website says the same thing from the other direction. To be eligible as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet. There are no additional technical requirements, no special schema, and no new machine-readable file to create. The controls Google names for limiting what appears are nosnippet, data-nosnippet, max-snippet, and noindex.

Two consequences follow. First, there is no separate “AI opt-out” that leaves your organic snippet intact. Second, Google-Extended is not a Search control. Google points site owners to Google-Extended for AI training and grounding in some of its other systems, while robots.txt rules for Googlebot remain the control for Search. Blocking Google-Extended does not remove a page from AI Overviews, and allowing it does not put a page in.

Where snippet controls go wrong on business sites

websites that handle sensitive enquiries have a particular reason to reach for these tags: privacy. Someone on the team, often with good intentions, wants to make sure sensitive language never appears in a search result. The trouble is that a page-level rule meant for one paragraph ends up applying to the whole page, or the whole site. These are the patterns we see when auditing:

  • A sitewide nosnippet added for “privacy”: a theme or plugin setting applies nosnippet to every URL, which removes the entire site from AI Overviews and AI Mode as a quoted source, not just the sensitive text.
  • Conflicting tags from a theme and an SEO plugin: when two robots tags disagree, Google applies the more restrictive rule, so a stray max-snippet:0 in a theme header overrides the plugin’s max-snippet:-1.
  • data-nosnippet on the wrong element: Google only honors the attribute on span, div, and section, so placing it on a p, an li, or a page builder’s custom element does nothing.
  • An unclosed div: Google’s specification warns that an unclosed div carrying data-nosnippet includes all content after it, which can quietly exclude the rest of an enquiry page.
  • data-nosnippet added by JavaScript after load: Google may extract the attribute before or after rendering, so a script that toggles it on existing elements, such as a review widget or consent tool configured to hide text, produces unpredictable results.
  • A rule hidden behind robots.txt: robots meta tags and X-Robots-Tag headers are only read when a URL is crawled, so a page disallowed in robots.txt never has its snippet rules seen at all.

The first pattern is the expensive one. A privacy instinct is right for a business, but a page-level snippet control is the wrong tool for it. If a phrase should never appear in a search result, the more reliable answer is usually that it should not be on a public, indexable page in the first place. Protected health information does not belong on marketing pages, and no meta tag changes that.

What a WordPress site usually outputs by default

On most WordPress sites we work on, the robots meta tag is written by an SEO plugin, not by hand. Common plugins output a permissive set of rules by default, such as max-snippet:-1, max-image-preview:large, max-video-preview:-1. That combination tells Google it may choose the snippet length, show a large image preview, and play a video preview of any length. For most service pages, it is the setting you want.

The operational truth is that the plugin setting is rarely the problem. The problem is the second source: a theme that also prints a robots tag, a staging configuration copied to production, a header added at the server or CDN level, or a page builder template that set a restrictive value years ago. Because Google applies the most restrictive rule it finds, the stricter value wins even when the plugin screen looks correct. Checking the plugin settings is not the same as checking what Google receives.

A five-minute check you can run today

Open any important page on your site, such as your main enquiries or services page, in Chrome. Open the developer console (F12, then the Console tab) and paste this line:

[...document.querySelectorAll('meta[name="robots" i],meta[name="googlebot" i]')].map(m=>m.name+': '+m.content).concat([...document.querySelectorAll('[data-nosnippet]')].map(e=>'data-nosnippet on <'+e.tagName.toLowerCase()+'>'))

Read the result like this:

  • More than one robots or googlebot line means two systems are writing rules. Find the second one.
  • Any nosnippet or max-snippet:0 on a page you want cited in AI answers is a problem to fix first.
  • Any data-nosnippet on an element other than span, div, or section is being ignored.

The console only shows the HTML the browser received. Snippet rules can also arrive in an HTTP header, which never appears in the page source. To see the header, run curl -sI https://yourdomain.com/your-page/ | grep -i x-robots from a terminal, or ask your developer to. Then confirm what Google itself received by running the page through the URL Inspection tool in Search Console and viewing the crawled HTML. Google’s AI features guidance recommends exactly this step when preview controls do not behave as expected.

How long a fix takes to show up

Removing an accidental nosnippet does not restore anything on the spot. Google has to recrawl the page and process the change. Its AI features documentation says crawling can take anywhere from several days to several months, depending on how often Google decides a page needs refreshing. Requesting indexing through URL Inspection can help for a handful of key pages, but it is a request, not a guarantee.

That timeline is why we treat snippet controls as part of launch and migration checklists rather than as something to look at after traffic drops. On a redesign, the robots tag on the staging site is frequently restrictive by design, and it is one of the easiest settings to carry into production by accident.

What we do not recommend

Because AI search is new, there is a steady supply of advice to add special files or markup “for AI.” Google’s documentation is direct on this point: there are no additional requirements to appear in AI Overviews or AI Mode, no special schema.org structured data to add, and no need for AI text files. The snippet controls covered here are the levers that actually exist, and on most sites the right setting is the permissive default, applied once and consistently.

If you want help auditing how your pages present in classic results and AI answers, our answer engine optimization work starts with exactly these checks, and our SEO services include robots and indexing reviews on every engagement. If the conflict lives in your theme or page builder, our web design team can remove the duplicate tag at the source so it does not come back with the next update.

×
✦ Meet MIA – Your AI Marketing Assistant

Get Instant Marketing
Answers + Book Strategy Call

Talk to MIA and get real answers, custom insights, and expert help to grow your business.
💬
Answer your marketing questions

Get instant expert answers to help you grow.

📈
Analyze your website or ads

MIA can audit and analyze performance in seconds.

💡
Get growth strategies

Receive tailored recommendations.

📅
Schedule a call with our team

Book a strategy consult instantly.

Start Voice Chat with MIA Click to talk
📅 Book a Strategy Call Schedule a consult
⚡ Get Quick Answers Fast responses
🔍 Request Free Audit Analyze my site
MIA Bot

MIA

● Online
Listening...
🎙️

Click the mic to start speaking. We only use your voice to understand your questions.

Skip to content