If one visible passage should stay out of Google search snippets, ask your developer to put data-nosnippet around that passage—not the whole article. The rest of the page can still supply useful preview text. If no text from the page should appear in a preview, use a page-level nosnippet directive instead. Google’s snippet guidance distinguishes these controls from max-snippet, which limits preview length rather than selecting the words Google may use.
Choose the smallest preview restriction that fits
Use the scope of the concern to make the decision. Google documents passage-level data-nosnippet alongside the page-level nosnippet and max-snippet controls. A length limit is not a substitute for excluding a particular sentence: the unwanted words could still fit within that limit.
| Your goal | Control | What you give up |
|---|---|---|
| Exclude one identifiable passage | data-nosnippet on that passage | That passage cannot supply snippet text; other eligible text remains available. |
| Cap text-preview length across the page | Page-level max-snippet:[number] | You cannot choose which passage supplies the limited text. |
| Allow no text snippet from the page | Page-level nosnippet | Readers lose the text preview; a static image thumbnail may still appear. |
Give your developer exact text boundaries
Consider a fictional article at https://example.com/blog/support-handoff-guide. Its opening summary explains how teams route support requests. A later paragraph quotes a customer’s internal support message. The owner wants visitors to read the quote on the page but does not want that paragraph used as snippet text. The resulting action is to keep the summary outside the excluded element and wrap only the quoted paragraph.
Send the developer the page URL, the exact beginning and end of the quote, and this requested markup shape: <div data-nosnippet><p>Fictional customer message: Our internal escalation route is being revised.</p></div>. The example message and URL are fictional; substitute the real passage without copying it into a public ticket. Google supports data-nosnippet on span, div, and section elements, and requires valid HTML with properly closed tags. Check that a wrapper does not accidentally include the summary or later paragraphs.
Ask for the attribute to be present when the element enters the page, rather than added or removed later on an existing element with JavaScript. Google warns that snippet extraction can happen before or after rendering. Also check whether the unwanted words appear elsewhere, including the page’s meta description: Google primarily builds snippets from page content but sometimes uses the meta description.
For a Ranks article, this is a website change to coordinate with whoever controls the published page. Ranks says you can review and edit each article before publishing when autopilot is off, and that articles live on your own blog. In that review-first workflow, flag a passage before release and arrange the markup with your developer; for an already published article, update the live page.
Check the deployed page before judging the search result
After release, open the public URL—not an editor preview. Confirm that the quoted paragraph remains visible to visitors, the useful summary remains outside the data-nosnippet element, and the deployed markup has the attribute on the intended wrapper with closing tags in the right place. Check for a conflicting page-level snippet directive and for other copies of the quoted words. Google can read and follow these preview settings only when its crawler is allowed to access the page.
Then inspect the public URL in Search Console and run Test live URL to check the current page. Do not treat that result as confirmation that Google has refreshed the search snippet: the indexed view describes Google’s most recently indexed version, while the live test examines the page now. Search for the page again after Google has had time to recrawl it, and keep the verified markup change separate from what any particular query happens to display.
If you manage the Search Console property and need to prompt a recrawl, Google offers an indexing request for individual URLs to property owners or full users. Crawling can take days to weeks, and a request does not guarantee immediate inclusion in results. Most importantly, data-nosnippet is a preview control, not a privacy measure: if the message must not be public, remove it from the published page rather than leaving it visible behind an attribute.
If the problem is an inaccurate description rather than text that must be excluded, use the misleading snippet guide. If the displayed title is wrong, use the separate title-link guide.
