Microsoft runs it as a classic search crawler, which means it does ordinary search indexing, of the kind that has existed for decades. That matters more than it used to rather than less: several assistants answer by searching a conventional index first and reading the top results.
What blocking it costs you: You are invisible to Bing and to Copilot answers grounded on it. Ordinary search indexing stops, and increasingly that index is the substrate AI answers are built from as well.
The user agent, and the token a rule matches on
These are two different strings and confusing them is why a rule that looks right does nothing. A robots.txt rule matches on the product token, case-insensitively, and ignores the rest of the user-agent header entirely.
An empty Disallow: and Allow: / mean the same thing to a crawler. What does not mean the same thing is having no rule at all: absence is permission by default, but it is permission nobody wrote down, and it survives only until somebody adds a blanket User-agent: * block without thinking about this crawler.
Blocking Bingbot
User-agent: Bingbot
Disallow: /
Before you paste that: you are invisible to Bing and to Copilot answers grounded on it. That is the cost, and it is paid silently — no error appears in your logs, no report tells you, and the traffic you lose was traffic you never saw arrive.
Deciding one crawler at a time is how a robots.txt ends up refusing things nobody meant to refuse. The free robots.txt generator asks the question once per category instead — train on me, cite me, fetch on demand, shop on my behalf — and writes the whole file for all 54 crawlers, naming what each refusal costs before you copy it.
How the web actually treats Bingbot
Measured on 2026-09-06, by reading the robots.txt of 292 public websites and resolving each one against this crawler specifically.
Verdict
Sites
Share
Blocked
1
0%
Explicitly allowed
237
81%
No rule either way
54
18%
No site is named, here or anywhere else on this domain. The count is the useful part; a league table of businesses that never asked to be measured is not.
The row worth reading twice is the last one. 54 of 292 sites have written no rule about Bingbot at all, which means their position on it is an accident rather than a decision — whatever their User-agent: * block happens to say.
Checking what your site does right now
Reading your own robots.txt is not the same as knowing what a crawler concludes from it. Precedence between a User-agent: * group and a named one, the longest-match rule between overlapping paths, and a token you spelled slightly wrong all produce a file that looks correct and behaves otherwise.
npx axray-cli your-site.com
The scan resolves your file against all 54 crawlers on this list individually and reports which ones are allowed, blocked, or covered by nothing. It is free, needs no account, and installs nothing.
Questions people ask about Bingbot
What is Bingbot?
Bingbot is a classic search crawler operated by Microsoft: it does ordinary search indexing, of the kind that has existed for decades. That matters more than it used to rather than less: several assistants answer by searching a conventional index first and reading the top results.
Should I block Bingbot in robots.txt?
Only if you are willing to pay what it costs. You are invisible to Bing and to Copilot answers grounded on it. Ordinary search indexing stops, and increasingly that index is the substrate AI answers are built from as well.
What is the Bingbot user agent string?
Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) — and the robots.txt product token, which is what a rule actually matches on, is Bingbot.
How do I check whether my site is blocking Bingbot right now?
Scan your site with AXRAY. It resolves your robots.txt against 54 named AI crawlers individually rather than reporting one verdict for all of them, so it will tell you whether this specific crawler is allowed, blocked, or covered by no rule at all. It is free and needs no account.