TLDR;
Bing added support for data-nosnippet, letting brands exclude selected page sections from search snippets and AI answers while keeping the page discoverable. It's a more precise control than excluding a whole page. Brands should test it carefully so essential offer conditions are not left out.
What happened
Bing introduced support for the data-nosnippet HTML attribute, allowing specific page sections to be withheld from search snippets and AI-generated answers. The page can remain discoverable while selected text is excluded, giving site owners more precision than page-wide preview controls.
Why it matters
Enterprise pages often mix public product evidence with material that should not become a standalone answer. A narrow exclusion can preserve the useful part of a page. It also creates a maintenance obligation: teams must know which passages are deliberately unavailable, otherwise an incomplete assistant answer can be mistaken for poor optimisation.
Selective exclusion is useful because a page can contain material with different purposes. A product explanation may be suitable for public discovery while an adjacent internal reference, repetitive legal passage or unrelated promotional panel is not helpful in a concise answer. Treating the whole page as one unit can force an unnecessary choice between exposure and control. However, removing a passage can also remove context that prevents a misleading interpretation. A benefit without its eligibility condition is a weaker answer, even if the excluded condition was difficult to summarise. The enterprise judgement is therefore editorial as well as technical. Decide which information belongs together before implementing the markup. Bing's documented control should be assessed within its stated scope; it is not a universal instruction that every assistant will necessarily honour.
How your brand can benefit / be affected
Apply data-nosnippet to clearly bounded sections after deciding which information customers still need to make a sound decision. Do not hide essential pricing conditions, eligibility restrictions or safety qualifications while leaving the surrounding offer available.
Test the rendered HTML and resulting Bing outputs. Keep an inventory of excluded sections and review it when templates change. This is a Bing-supported control, so verify each other provider separately before assuming the same behaviour.
Review the proposed exclusions on representative templates, not just individual pages. Identify why each passage should be excluded and what the remaining text would imply without it. For example, hiding a lengthy supplementary note may be reasonable, but hiding the restriction that defines who can receive an offer could distort the offer itself. Ask the content owner to approve the resulting meaning. Apply the smallest sensible exclusion and keep essential qualifications alongside the relevant claim. This avoids a template-level change accidentally suppressing useful information across thousands of pages that happen to share the same component.
Verify that the markup reaches the rendered page correctly and does not interfere with ordinary reading. Then test relevant queries and inspect available evidence of how Bing presents the content, allowing for the fact that a single answer is not a complete coverage report. Keep a record of the implementation date and affected templates so unintended changes can be investigated. If the objective is protecting confidential information, remove it from public access rather than relying on snippet controls. Use selective exclusion to manage supported presentation behaviour, while maintaining separate access controls for material that should never be available to an unauthenticated visitor or crawler.
News date: 15 October 2025. Editorial review: 16 September 2026. Analysis includes subsequent developments where stated.