Does data-nosnippet keep content out of Copilot answers?

data-nosnippet keeps the text it wraps out of Bing's snippets and AI summaries. Bing announced support on October 15, 2025, and stated that tagged content "is still indexed normally, but it will be excluded from snippets and AI summaries." The same post says the tagged content "is available for ranking."

That split matters. Bing still reads the text and can still use it to decide whether the page is relevant. It just won't display that text as a snippet or in an AI summary. Microsoft Copilot grounds its answers on the Bing index, so the same exclusion is the control you have over what Copilot shows from your page, as of October 2026.

The markup is a single boolean attribute on an element:

<div data-nosnippet>Internal pricing notes</div>

For the full background on the announcement, see our digest of Bing's data-nosnippet support. If you're worried about the ranking side, whether hiding text from AI summaries hurts rankings covers it in detail.

data-nosnippet is narrow on purpose. Know its limits before you rely on it.

• It does not remove the page. The rest of the page stays eligible for snippets and AI summaries. Only the wrapped element is held back.
• It does not stop the fact appearing elsewhere. If the same detail sits on another page you own, or on a third-party site, Copilot can draw on those. The attribute controls your element, not the fact.
• It is not cross-engine. Bing's post is a statement about Bing. Google also documents data-nosnippet for its own surfaces. Treat ChatGPT, Perplexity and Claude as separate questions and check each vendor's own documentation.
• It has no additive twin. No attribute or markup makes a section more likely to be quoted. Snippet controls only subtract.
• It only matters if Bingbot gets in. If your firewall or CDN turns Bingbot away, Bing never sees the page at all. Check that first with our guide to Bingbot, Copilot and your firewall.

If you need broader exclusion, page-level tools do more. noindex drops the page from the index. nosnippet and max-snippet:0 suppress snippet text for the whole page. The trade-offs are laid out in noindex vs nosnippet vs data-nosnippet for AI.

This is one of the few AI visibility claims with first-party documentation behind it. Google and Bing both list noindex, nosnippet, max-snippet and data-nosnippet as the on-page controls for limiting how content appears in their AI features. data-nosnippet is the only control in that set that works below the page level.

Two honest limits apply. First, Bing's statement is a vendor description of its own system, not an outside measurement. Second, nobody outside Microsoft can watch Copilot's retrieval directly. What you can observe is the output: whether a tagged sentence ever turns up in a Copilot answer.

Bing Webmaster Tools gives you one window here. Its AI Performance report shows citation activity for your pages across Copilot and Bing AI summaries. It's covered in free Copilot citation data in Bing Webmaster Tools. Use it to confirm a page is still cited after you tag part of it.

The common failure is not a site that wants to hide something. It is a site that hides the wrong thing without knowing.

The usual pattern: a developer adds data-nosnippet to a component to keep boilerplate out of search snippets. A cookie banner, a legal footer or a promo bar are typical targets. Then the attribute lands on a wrapper that also holds real content, or a shared component gets reused on product and pricing pages. From that point, your prices, plan names or one-line product definition are indexed but never shown in Bing's AI summaries.

This matters because a specific, fetchable fact (a price, a number, a clear definition) gives an engine a sentence it can quote. Suppress that sentence and you remove it from the answer, while everything still looks fine in your rankings report. Consent tools cause related problems, which whether a cookie banner can hide your site from AI explains.

Run this check on templates, not just single pages. One template can cover thousands of URLs.

1. List your templates. Home, product, pricing, article, category, about and any shared components.
2. Fetch raw HTML for one URL per template. Search the source for data-nosnippet. Note which element carries it and what text sits inside.
3. Check page-level directives. Look for <meta name="robots"> with nosnippet, max-snippet:0 or noindex, and check the X-Robots-Tag HTTP header too.
4. Compare against intent. For each hit, ask whether someone chose to hide that text. Anything holding pricing, product names or definitions is a red flag.
5. Fix at the component. Narrow the attribute to the element that should be hidden, then redeploy and refetch.
6. Recheck after redesigns. Template changes reintroduce the problem quietly.

The step-by-step version, with what to log, is in auditing nosnippet and data-nosnippet across a site. Once your controls are clean, the free checker on this site shows how AI engines describe you for up to three buyer questions, which tells you whether the facts you care about are actually showing up.