If I block Bingbot, can Copilot still cite me?

Blocking Bingbot removes the one documented route your own pages have into Microsoft Copilot. Copilot grounds its answers in Bing's index. So do Bing's AI-generated summaries and Azure's Grounding with Bing Search, which Microsoft lists as a generally available option for agents. Bingbot is the crawler that fetches pages into that index.

The chain is short:

1. Bingbot fetches your page (access).
2. Bing stores it in its index.
3. Copilot runs grounding queries against that index at answer time (retrieval).
4. The model decides which retrieved pages to use and cite (generation).

A Disallow for Bingbot breaks step 1. Every later step depends on it. As of October 2026, the evidence we work from documents no separate Copilot crawler token that would let you block Bing search but stay in Copilot, or the reverse. If you want a page out of Bing, you are out of the documented Copilot path too. If you want a page in Bing but kept out of AI answers, robots.txt is the wrong tool. Snippet controls are the right one.

Two kinds of evidence point the same way.

First, Microsoft's own documentation. Its Azure agent docs describe Web Search and Grounding with Bing Search as Bing-index-backed. Bing Webmaster Tools' AI Performance report, in public preview since February 2026, covers Microsoft Copilot, AI summaries in Bing and select partner integrations. It reports citations and the grounding queries Copilot actually ran.

Second, an outside test. In OtterlyAI's 2026 experiment with two AI-generated sites, Google deindexed both, and Google's AI surfaces almost stopped citing them. Bing kept both sites indexed. Of the 3,934 citations Otterly tracked for one site, 2,718 came from Microsoft Copilot. The index an engine holds shaped what it cited.

That test is one pair of sites on a low-stakes topic, run by a vendor that sells tracking. It shows the mechanism in action, not a reliable effect size. The practical reading: an engine can't cite what its index doesn't hold. For the related case of a site that never made it into Bing, see whether Copilot can cite a site missing from Bing's index.

Other sites can still mention you

Blocking Bingbot keeps your own pages out. It doesn't stop Copilot citing a review site, a directory or a news article that names you. Being named on pages engines already cite is associated with appearing in answers, though nothing guarantees it.

ChatGPT is a separate question

OpenAI says ChatGPT search sometimes partners with other search providers, but that link is hedged and unquantified. In Otterly's test, ranking in Bing produced effectively zero ChatGPT citations even with ChatGPT's crawlers visiting. ChatGPT search eligibility runs through OAI-SearchBot. Read how GPTBot and ChatGPT search differ before changing those rules.

Your firewall can block Bingbot for you

robots.txt is one gate. Your CDN or web application firewall is a second one. A bot-management rule that returns 403 to Bingbot has the same effect as a Disallow, and nothing in your robots.txt reveals it. The Bingbot, Copilot and firewall page covers how this happens.

Bing announced support for the data-nosnippet attribute in October 2025. Its wording is precise: content marked this way "is still indexed normally, but it will be excluded from snippets and AI summaries." Bing adds that the tagged content "is available for ranking." You keep index eligibility and lose display.

You have three levels of control:

• One section: wrap it in an element with data-nosnippet.
• A whole page: a robots meta tag with nosnippet.
• A length cap: max-snippet with a character limit, or max-snippet:0 for none.

<meta name="robots" content="nosnippet">
<div data-nosnippet>Internal pricing notes</div>

These are suppression tools only. No markup makes a section more likely to be cited. They also fail quietly when a template applies them by accident, for example to hide a cookie banner, and they end up covering real content. Audit where they appear before you add more.

Decide what you actually want, then check that your setup matches it.

1. Read your robots.txt group for Bingbot. Look for a blanket AI block or a User-agent: * disallow that catches it. The per-bot robots.txt guide shows how groups resolve.
2. Test the second gate. Request a page as Bingbot and confirm you get a 200, not a 403 or a challenge page. The robots.txt vs firewall comparison explains why both gates matter.
3. Check index status in Bing Webmaster Tools. Google Search Console tells you nothing about Bing.
4. Search your HTML for snippet controls. Find every data-nosnippet, nosnippet and max-snippet and confirm each one is intentional.
5. Watch the AI Performance report. It is the only place you'll see the grounding queries Copilot used for your pages.

For step 1, the robots.txt Checker for AI Crawlers resolves your rules per bot. None of this guarantees a citation. It removes the blocks that make one impossible.