Microsoft
bingbot
Crawls pages for Bing Search.
Web searchTHE SIGNAL
Ad checks can appear on campaign URLs that receive little organic crawling.
Test the advertised URL and all redirects before broadening crawler access.
Look for the adidxbot identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.
Use Microsoft’s documented bot verification procedure and current IP information; do not trust the User-Agent alone.
Microsoft’s robots.txt tester supports AdIdxbot. Test the named-client rules against your advertising landing pages.
Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.
User-agent: adidxbot
Disallow: /403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.
Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.
Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.
See their requests. Find the pages that matter.
See your agent traffic