AI search

Amzn-SearchBot

Crawls for Amazon search experiences, including Alexa, rather than generative-model training.

See your agent traffic
PurposeAI search
HTTP identifierAmzn-SearchBot
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

Search retrieval may support discovery, but the request does not prove an Alexa answer featured your business.

Public-page coverage
Retrieval failures
Referrals separately

Your next move

Make the search policy explicit when you want different treatment from general collection. Inspect important public-page response codes.

The technical details

Markdown
How to identify it

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

How to check identity

Compare the request IP with the current operator-published ranges linked in the source. A matching name alone does not verify identity.

Access and robots.txt

Supports robots.txt; absent a specific group, Amazon describes fallback to other search-bot rules.

Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.

User-agent: Amzn-SearchBot
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 Amzn-SearchBot in context

See their requests. Find the pages that matter.

See your agent traffic