Amazon
Amzn-SearchBot
Crawls for Amazon search experiences, including Alexa, rather than generative-model training.
AI searchUser-requested fetch
Amzn-User
Retrieves current web information for user actions such as Alexa queries.
Operated by Amazon
See your agent traffic PurposeUser-requested fetch
HTTP identifierAmzn-User
IdentityVerify beyond the name
THE SIGNAL
What this visit tells you
A verified retrieval can follow a user request through an Amazon product. Additional requests alone do not identify the same user.
Requested public pages
Public-page 403 and 404 responses
Subsequent page requests
Your next move
Inspect the requested URL, response code and readable page content. Check whether redirects or authentication prevented retrieval.
The technical details
MarkdownHow to identify it
Look for the Amzn-User 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
User-initiated requests may not follow all robots.txt directives.
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 PulseSee Amzn-User in context
See their requests. Find the pages that matter.
See your agent trafficKEEP EXPLORING
Different bots, different intent
OpenAI
ChatGPT-User
Fetches pages for user actions in ChatGPT and custom GPTs.
User-requested fetch