Ad review

adidxbot

Checks landing pages for Microsoft advertising.

See your agent traffic
PurposeAd review
HTTP identifieradidxbot
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

Ad checks can appear on campaign URLs that receive little organic crawling.

Landing-page responses
Redirect chains
Failed checks

Your next move

Test the advertised URL and all redirects before broadening crawler access.

The technical details

Markdown
How to identify it

Look for the adidxbot identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Use Microsoft’s documented bot verification procedure and current IP information; do not trust the User-Agent alone.

Access and robots.txt

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: /
Seeing 403 or 404 responses?

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.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See adidxbot in context

See their requests. Find the pages that matter.

See your agent traffic