resulthack

All AI crawlers /

Bingbot

Microsoft · AI search · robots.txt: Yes

Bing's standard crawler: it fetches pages for the Bing index, which Microsoft says also supplies Copilot answers and grounding API results.

Block Bingbot

User-agent: Bingbot
Disallow: /

Blocking Bingbot stops Bing crawling your pages; Microsoft asks site owners not to do it. Because robots.txt controls crawling, not indexing, Microsoft says to use NOINDEX to keep a URL out of Bing search, Copilot and grounding results, NOARCHIVE to keep content out of Copilot responses and grounding results, and notes that NOCACHE limits Copilot to the URL, title and snippet.

This token also decides Bing search. The robots.txt generator leaves it to the rest of your file unless you choose Allow or Block for it by name.

Allow Bingbot

User-agent: Bingbot
Allow: /

An allow group only changes anything if a broader rule would block Bingbot. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.

Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.

Block or allow it at the server

robots.txt asks; a server rule refuses. Every rule here matches bingbot, spelled as in the User-Agent Microsoft documents (“bingbot/2.0”), and matches it case-sensitively. The server answers 403.

What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user. (Apache HTTP Server 2.4 documentation). A fake Bingbot is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Microsoft's published addresses.

Your server

To block it: refuse every request that says Bingbot

In the server block (or a location)

if ($http_user_agent ~ bingbot) {
    return 403;
}

Bingbot also decides Bing search, so this refuses that crawl too.

To allow only the real one: refuse Bingbot claims from outside Microsoft's list

In the http block

geo $bingbot_unlisted {
    default 1;
    157.55.39.0/24 0;
    207.46.13.0/24 0;
    40.77.167.0/24 0;
    13.66.139.0/24 0;
    13.66.144.0/24 0;
    52.167.144.0/24 0;
    13.67.10.16/28 0;
    13.69.66.240/28 0;
    13.71.172.224/28 0;
    139.217.52.0/28 0;
    191.233.204.224/28 0;
    20.36.108.32/28 0;
    20.43.120.16/28 0;
    40.79.131.208/28 0;
    40.79.186.176/28 0;
    52.231.148.0/28 0;
    20.79.107.240/28 0;
    51.105.67.0/28 0;
    20.125.163.80/28 0;
    40.77.188.0/22 0;
    65.55.210.0/24 0;
    199.30.24.0/23 0;
    40.77.202.0/24 0;
    40.77.139.0/25 0;
    20.74.197.0/28 0;
    20.15.133.160/27 0;
    40.77.177.0/24 0;
    40.77.178.0/23 0;
}
map $http_user_agent $bingbot_fake {
    default 0;
    "~bingbot" $bingbot_unlisted;
}

In the server block (or a location)

if ($bingbot_fake) {
    return 403;
}

The geo and map blocks go at http level; nginx's docs give Context: http for both, and for if Context: server, location. By default, the address is taken from the $remote_addr variable (nginx documentation).

To block it: refuse every request that says Bingbot

In the virtual host, a <Directory> block or .htaccess

<If "%{HTTP_USER_AGENT} =~ /bingbot/">
    Require all denied
</If>

Bingbot also decides Bing search, so this refuses that crawl too.

To allow only the real one: refuse Bingbot claims from outside Microsoft's list

In the virtual host, a <Directory> block or .htaccess

<If "%{HTTP_USER_AGENT} =~ /bingbot/">
    Require ip 157.55.39.0/24 207.46.13.0/24 40.77.167.0/24 13.66.139.0/24 13.66.144.0/24 52.167.144.0/24
    Require ip 13.67.10.16/28 13.69.66.240/28 13.71.172.224/28 139.217.52.0/28 191.233.204.224/28 20.36.108.32/28
    Require ip 20.43.120.16/28 40.79.131.208/28 40.79.186.176/28 52.231.148.0/28 20.79.107.240/28 51.105.67.0/28
    Require ip 20.125.163.80/28 40.77.188.0/22 65.55.210.0/24 199.30.24.0/23 40.77.202.0/24 40.77.139.0/25
    Require ip 20.74.197.0/28 20.15.133.160/27 40.77.177.0/24 40.77.178.0/23
</If>

Apache httpd 2.4. Syntax: <If expression> ... </If> Context: server config, virtual host, directory, .htaccess (Apache HTTP Server 2.4 documentation). Several Require ip lines in one block: When multiple Require directives are used in a single configuration section and are not contained in another authorization directive like <RequireAll>, they are implicitly contained within a <RequireAny> directive. (Apache HTTP Server 2.4 documentation)

To block it: refuse every request that says Bingbot

Inside the site block

@bingbot header User-Agent *bingbot*
respond @bingbot 403

Bingbot also decides Bing search, so this refuses that crawl too.

To allow only the real one: refuse Bingbot claims from outside Microsoft's list

Inside the site block

@fake-bingbot {
    header User-Agent *bingbot*
    not {
        client_ip 157.55.39.0/24 207.46.13.0/24 40.77.167.0/24 13.66.139.0/24 13.66.144.0/24 52.167.144.0/24
        client_ip 13.67.10.16/28 13.69.66.240/28 13.71.172.224/28 139.217.52.0/28 191.233.204.224/28 20.36.108.32/28
        client_ip 20.43.120.16/28 40.79.131.208/28 40.79.186.176/28 52.231.148.0/28 20.79.107.240/28 51.105.67.0/28
        client_ip 20.125.163.80/28 40.77.188.0/22 65.55.210.0/24 199.30.24.0/23 40.77.202.0/24 40.77.139.0/25
        client_ip 20.74.197.0/28 20.15.133.160/27 40.77.177.0/24 40.77.178.0/23
    }
}
respond @fake-bingbot 403

Like directives, named matcher definitions must go inside the site blocks that use them. (Caddy documentation) On client_ip: This matcher is best used when the trusted_proxies global option is configured, otherwise it acts identically to the remote_ip matcher. (Caddy documentation)

To block it: refuse every request that says Bingbot

Expression of a custom rule; action Block

(http.user_agent contains "bingbot")

Bingbot also decides Bing search, so this refuses that crawl too.

To allow only the real one: refuse Bingbot claims from outside Microsoft's list

Expression of a custom rule; action Block

(http.user_agent contains "bingbot" and not ip.src in {157.55.39.0/24 207.46.13.0/24 40.77.167.0/24 13.66.139.0/24 13.66.144.0/24 52.167.144.0/24 13.67.10.16/28 13.69.66.240/28 13.71.172.224/28 139.217.52.0/28 191.233.204.224/28 20.36.108.32/28 20.43.120.16/28 40.79.131.208/28 40.79.186.176/28 52.231.148.0/28 20.79.107.240/28 51.105.67.0/28 20.125.163.80/28 40.77.188.0/22 65.55.210.0/24 199.30.24.0/23 40.77.202.0/24 40.77.139.0/25 20.74.197.0/28 20.15.133.160/27 40.77.177.0/24 40.77.178.0/23})

Each expression is one custom rule with the action Block (Cloudflare's own example: Expression: (cf.bot_management.score lt 2 and http.user_agent contains "App_Name 2.0") Action: Block).

Addresses in the “only the real one” rules: Microsoft's list www.bing.com/toolbox/bingbot.json, 28 ranges, fetched 8 Oct 2026, list dated 3 Jan 2024. Operators change their lists; compare the date with the live list before you rely on it.

The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.

Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.

Who blocks it

Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 3 block Bingbot from the whole site by name, 12 block it through their User-agent: * group, and 53 name it with partial rules (some paths closed, the home page open). 9 more name it only to let it in.

3

block it by name 0.6%

12

block it through * 2.4%

53

name it, partial rules 10.4%

Percentages are of the 508 files we could read, not of all 1,000 sites.

Highest-ranked sites that block Bingbot by name

  1. fbcdn.net rank 12
  2. goodreads.com rank 475
  3. sharethrough.com rank 653

Each links to the site's live robots.txt, which may have changed since 2026-10-09.

robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.

Facts

Operator
Microsoft
Purpose
AI search index

Microsoft says Bing search, Copilot and grounding API results rely on the same crawling and indexing foundation, so the pages Bingbot crawls are what Copilot can ground and cite.

Obeys robots.txt
Yes. Microsoft says robots.txt tells Bing’s crawlers how to interact with your site, and lists blocking Bingbot in robots.txt among the things to avoid. It also says robots.txt controls crawl access, not indexing.
In your server logs
The user-agent string contains "bingbot/2.0" (lower case), in desktop and mobile variants whose Chrome version follows Microsoft Edge. BingPreview page snapshots use the same bingbot string.
How to verify it
Match the IP against Microsoft’s published Bingbot list, or check a single address with Bing’s Verify Bingbot tool.

Published list: www.bing.com/toolbox/bingbot.json — 28 IPv4 ranges when we fetched it, list dated 3 Jan 2024. Always match against the live list; operators update them. To count real and fake Bingbot requests in your own server log against this list, drop the log into the log reader.

What Microsoft says

Quoted word for word from the operator's documentation.

“Bingbot is our standard crawler and handles most of our crawling needs each day.”

“Bing and Copilot search experiences rely on the same core crawling, indexing, and ranking foundation as traditional search.”

“These guidelines describe how Bing discovers, crawls, indexes, evaluates, and surfaces content across Bing search experiences, Copilot, and grounding API results.”

“Robots.txt files can be configured to tell Bing crawlers how to interact with your website.”

“Allow Bingbot to crawl and render content efficiently.”

“Blocking Bingbot in your robots.txt file”

“robots.txt controls crawl access, not indexing.”

“Use NOINDEX when a URL should NOT appear in Bing search, Copilot experiences, or grounding API results.”

“NOARCHIVE prevents content from being used in Copilot responses and grounding results.”

“NOCACHE limits Copilot to using only the URL, title, and snippet, reducing citation depth and answer quality.”

“Mozilla/5.0 (compatible; bingbot/2.0;”

“BingPreview generates page snapshots for Bing.”

“Other solutions: You can also identify Bingbot using IP address, by matching the crawler's IP address to the list of Bingbot IP addresses.”

“Verify Bingbot allows you to check if an IP address belongs to Bingbot.”

Sources

Same purpose, other operators

← All 49 AI crawlers

Made with AI tools. · Privacy