Bing's web crawler. Microsoft says Copilot and Copilot Chat may fetch information from the Bing search service to ground a response.
Source: learn.microsoft.comOperator
Microsoft
Job
Search index
Builds the index an AI answer searches. Block it and you drop out of that product's results.
robots.txt
Follows robots.txt
Bing says it respects the preferences content owners express through robots.txt and its other supported controls.
Source: blogs.bing.comMozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Chrome/W.X.Y.Z Safari/537.36
Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)
Add one of these groups to the robots.txt at the root of your domain.
A crawler obeys only the most specific group that names it (RFC 9309), so a named group does not inherit the rules under User-agent: *. Repeat any paths you keep private, as the example does with /admin/.
User-agent: bingbot Allow: / Disallow: /admin/
User-agent: bingbot Disallow: /
Read from the robots.txt we serve. We want AI engines to read and cite this site, so every AI crawler is allowed everywhere except the app, the API and the sign-in pages (/dashboard/, /api/, /login, /signup, /sign-in, /sign-up). The file also declares Content-Signal: ai-train=yes, search=yes, ai-input=yes.
User-agent: bingbot Allow: / Allow: /api/markdown/ Disallow: /dashboard/ Disallow: /api/ Disallow: /login Disallow: /signup Disallow: /sign-in Disallow: /sign-up
See the whole file. The same rules repeat in every group, because a crawler that matches a named group ignores the wildcard one.