Bing's data-nosnippet Support, Digested

On October 15, 2025, the Bing Webmaster Blog announced support for the data-nosnippet HTML attribute. It is a first-party product announcement from Microsoft about how Bing's own systems treat a piece of markup.

The attribute was not new. Google already documents data-nosnippet alongside noindex, nosnippet and max-snippet in its robots meta tag specification. Bing's support means one attribute now carries the same intent on both major search indexes.

Why it matters for AI search: Bing's index backs Microsoft Copilot and Bing's AI summaries. A display control in Bing is therefore a display control for those answers. For the basics of the attribute itself, see the data-nosnippet definition.

This is not an experiment. There is no sample, no control group and no effect size. Bing states a rule about its own behavior.

That makes it strong evidence for the mechanism and silent on magnitude. The operator is telling you what its system does with the attribute. It is not telling you how many answers change, or how quickly a newly tagged section drops out of summaries.

It also means you can only check it by observation. Nobody outside Microsoft sees the display decision directly. You can see whether tagged text shows up in Bing results and Copilot answers over time, and Bing Webmaster Tools reports citation activity for your pages (what that data covers).

Two sentences carry the whole announcement:

• "When Bing crawls your site, any content marked with data-nosnippet is still indexed normally, but it will be excluded from snippets and AI summaries."
• "The content tagged as data-nosnippet is available for ranking."

Read together, they split three things that people often blur:

1. Indexing: unchanged. Bing still stores the content.
2. Ranking: unchanged. The content can still help the page rank.
3. Display: removed. The text is kept out of snippets and AI summaries.

In markup, it looks like this:

<div data-nosnippet>Text you do not want quoted</div>

The page-level relatives work at a different scale. nosnippet and max-snippet:0 suppress display for the whole page, and noindex removes the page from the index entirely. Google documents all four as the on-page controls for limiting what appears in its AI features. The trade-offs between them are laid out in noindex vs nosnippet vs data-nosnippet for AI. If ranking is your worry, hiding text from AI summaries and rankings covers that question directly.

There is no additive counterpart

data-nosnippet only takes things away. No attribute, schema type or wrapper makes a section more likely to be quoted. Treat any advice that implies the reverse ("mark your best paragraph so AI uses it") as unsupported.

It does not speak for other engines

The announcement covers Bing. It says nothing about ChatGPT, Perplexity or Claude, which run their own crawlers and document their own controls. Training use is governed separately, mainly by per-bot robots.txt rules. For Copilot specifically, see whether data-nosnippet keeps content out of Copilot answers.

It does not hide facts that live elsewhere

The attribute controls display of your page. If the same fact appears on other sites, an engine can still state it by drawing on those pages.

It does not hide text from people

Tagged content stays visible to visitors. It is a display instruction for search, not an access control. Never use it, or any hidden-text trick, to show crawlers something different from what users see.

The attribute is rarely misused on purpose. It is misused by inheritance.

Say you run a software company and a developer adds data-nosnippet to a cookie banner component. Later, a redesign reuses that wrapper around the main content area. Every product page is now indexed, ranking and healthy in your search reports, and none of it can appear in Bing snippets or AI summaries.

That is what makes this failure quiet. Indexing and ranking signals look fine, because the attribute does not touch them. The only symptom is absence from answers, and absence is easy to blame on something else.

The same goes for page-level directives. A nosnippet or max-snippet:0 left in a shared head template, or sent in an X-Robots-Tag HTTP header, suppresses display across every page that uses it.

Run this on your key templates before you spend time on anything else in AI search:

1. Search the raw HTML of each template type (home, product, pricing, article) for data-nosnippet. Use the server response, not the rendered page, so you see what crawlers receive.
2. Check page-level directives: the meta name="robots" tag and the X-Robots-Tag response header, looking for nosnippet, max-snippet and noindex.
3. Map every hit to an intent. Keep it where you meant to hide something (legal boilerplate, internal notes). Remove it where it wraps content you want quoted, such as prices or product descriptions.
4. Fix it at the component level, not page by page, so the next build does not reintroduce it.
5. Watch the result in Bing Webmaster Tools' AI Performance report over the following weeks. Note that parts of that data are sampled.

One caveat before you start: this control only matters if Bing can fetch the page. If a firewall turns bingbot away, snippet settings are moot (check that first). For a full site-wide method, follow auditing nosnippet and data-nosnippet across a site.

Removing an accidental tag restores eligibility for display. It does not promise a citation. What appears in an answer is still the engine's decision, as of October 2026.

Does adding data-nosnippet hurt my Bing rankings? Bing says no. Its October 2025 announcement states that content tagged with data-nosnippet "is available for ranking" and is still indexed normally. The attribute only removes the text from snippets and AI summaries. So the trade-off is display, not ranking. If you need the content gone from the index entirely, that is what noindex does, and it does affect whether the page can appear at all.

Does Google support data-nosnippet as well? Yes. Google documents data-nosnippet in its robots meta tag specification, alongside nosnippet, max-snippet and noindex. Google also says a page must be indexed and eligible to be shown with a snippet to appear as a supporting link in AI Overviews or AI Mode. That means aggressive snippet suppression on Google can also keep a page out of its AI features.

Can I use markup to make a section more likely to appear in AI answers? No markup with credible evidence does that. data-nosnippet is suppression only, and neither Bing nor Google documents an opposite attribute. What you can do is state the specific fact you want quoted (a price, a number, a one-line definition) plainly in the server-rendered HTML, so a fetching engine has a sentence it could use. Whether it does is up to the engine.

Does data-nosnippet keep my content out of ChatGPT or Perplexity? The Bing announcement only covers Bing and the AI summaries built on it. OpenAI, Perplexity and Anthropic document their own crawlers and controls, mostly through per-bot robots.txt rules, and none of the evidence here shows them reading data-nosnippet. If you need content out of those engines, use the controls each one documents rather than assuming Bing's attribute carries over.

How often should I re-check for accidental data-nosnippet tags? Check after any redesign, template change or component library update, since that is when wrappers get reused in new places. A light quarterly scan of your main template types is a reasonable habit. The check is cheap: search the raw HTML for the attribute and review robots directives in the head and response headers. Catching one inherited tag can matter more than any content change.