Bingbot: Robots.txt & Crawl Policy Reference

AI Summary: Bingbot is Microsoft's standard web crawler. It collects documents from the web to build the searchable index for the Bing search engine and powers Microsoft Copilot's AI-generated answers.

Role and policy boundary

Bingbot is essential for search visibility on Bing, Yahoo, and DuckDuckGo (which utilizes Bing's index). It is a traditional search crawler that has evolved to also feed data into Microsoft's AI features, such as Copilot. Blocking Bingbot completely removes your site from Bing's search index.

A robots rule is a declaration of intent; it does not replace authentication, authorization, or rate limiting. Start with a dedicated group:

User-agent: bingbot
Allow: /
Disallow: /staging/
Disallow: /internal/

To stop access for the entire site, use:

User-agent: bingbot
Disallow: /

Avoid assuming that User-agent: * expresses the same business intent. A wildcard can affect assistant and training crawlers too, and it makes later audits harder because the source of the decision is less specific.

Layered verification

Verify the same URL through each control plane instead of assuming that one green signal represents the whole request path. Compare the bot-specific robots group, the page-level metadata, and the response headers captured at the public edge.

Bingbot strictly adheres to robots.txt and supports standard directives, including crawl-delay. You can verify legitimate Bingbot traffic using Reverse DNS lookups or the Bing Webmaster Tools API to prevent spoofing by malicious actors.

The Policy Engine evaluates the selected user-agent, path scope, and the other supplied layers independently. It can therefore explain why a bot is allowed while another is blocked, rather than returning one blended website score.

Page-level directives can still override the intended outcome for indexing:

<meta name="robots" content="noindex, nofollow">

X-Robots-Tag: noindex, nofollow

If a response uses these tags, the report marks the result as blocked or conflicting even if the crawler-specific robots group is permissive. This is especially important for canonical pages served through an edge cache where headers may differ from the origin response.

WAF and Nginx remediation examples

To ensure only verified Bingbot traffic reaches your origin server while blocking spoofed requests, you can use a WAF rule (example conceptually for Cloudflare):

{
  "description": "Block fake Bingbot",
  "expression": "lower(http.user_agent) contains \"bingbot\" and not cf.bot_management.verified_bot",
  "action": "block"
}

Use your platform's actual middleware response pattern rather than copying this simplified example without review. Never place a secret, verification token, or internal policy identifier in a public response header.

map $http_user_agent $block_bingbot_private {
    default 0;
    ~*bingbot 1;
}

server {
    location ~ ^/(admin|account|private|licensed|internal|api)/ {
        if ($block_bingbot_private) { return 403; }
        try_files $uri $uri/ =404;
    }
}

Review checklist

Use this checklist after every policy change and after a CDN or WAF migration. Record the request URL, User-Agent, HTTP status, final redirect, and the exact evidence used to reach the decision.

Verify that the dedicated group appears before relying on a wildcard, test a representative public and private path, and compare live response headers with robots.txt. Keep the policy close to the content owner's intent and record whether the site wants discovery, citation, or no access at all.

Need to optimize your entire site for AI search visibility? Run a comprehensive audit with Geolify.ai.