Amzn-User
Fetches behind user actions, such as an Alexa question needing current information
What Amzn-User does
Amzn-User is Amazon's user-triggered fetch. Amazon's example is the one that makes it concrete: an Alexa question that needs up-to-date information, where a person has asked something and the answer requires reading a page now rather than recalling one.
Like every user-triggered agent in this directory, the traffic is one request serving one person, not a crawl. And like the others, blocking it produces a failure the person sees rather than a policy they never notice.
How to block Amzn-User
Add this to the robots.txt at the root of your domain, alongside what is already there rather than replacing it.
robots.txt
User-agent: Amzn-User
Disallow: /What that costs you: Someone asking Alexa a question your page answers gets an answer from somewhere else.
To allow it instead, write nothing. A crawler with no group of its own follows your User-agent: * rules, and giving it a named group with Allow: / detaches it from those rules entirely — including any path you disallow there.
Find it in your logs
Amazon names the token but does not publish a full user-agent string for it, so match on the token itself.
To find every visit it has made, and the addresses it came from:
Terminal
grep -F 'Amzn-User' /var/log/nginx/access.log | awk '{print $1}' | sort | uniq -c | sort -rnCheck that it is really Amzn-User
Harder than it should be. Amazon documents the token and states that its crawlers honour robots.txt, but publishes no list of the addresses they crawl from — unlike OpenAI, Perplexity, Google and Bing. Reverse DNS and request patterns are what is left. Treat an unverifiable user agent as unverified, because anyone can send any string.
Should you block Amzn-User?
Usually leave it. Someone asking Alexa a question your page answers is about as qualified as an audience gets.
The reason to block is the same narrow one as elsewhere: cost, on a site where serving a request is genuinely expensive.
Questions
- What does Amzn-User actually fetch?
- A page a person's request needs. Amazon gives the example of responding to an Alexa query that requires current information, which is a live fetch rather than something served from an index.
The user agent and IP figures on this page were read from Amazon’s own URLs on 14 September 2026. Blocking figures come from our survey of 170 well-known sites across 10 categories on 14 September 2026, 148 of which returned a readable robots.txt.
Is Amzn-User allowed on your site right now?
The checker reads your live robots.txt and reports every token in this directory, with the exact directive that decided each one.