What it does
Amzn-User is Amazon's user action crawler. A live fetch made because a human asked the assistant about your page right now. Closest thing to a real visitor; several of these (Perplexity-User, meta-externalfetcher) ignore robots.txt by design because the request is user-initiated.
User-initiated fetches for Amazon AI experiences.
Full UA: not captured in our July 2026 roster review — match log hits on the token Amzn-User (case-insensitive substring) and verify by IP before acting.
How to verify a hit is really Amzn-User
Verification method (July 2026): Published IP list page: https://developer.amazon.com/amazonbot/live-ip-addresses/
The vendor publishes crawler IPs on a documentation page (not a machine-readable JSON endpoint), so verification is a manual cross-check: open the page, compare the hit's source IP against the listed ranges.
User-agent strings are freely spoofed, so a UA match alone proves nothing. Full step-by-step method: verify by IP.
Allow or block in robots.txt
Match the exact token Amzn-User in robots.txt:
# Block Amzn-User site-wide
User-agent: Amzn-User
Disallow: /
# Explicitly allow Amzn-User
User-agent: Amzn-User
Allow: /
For the allow-search-block-training combined pattern (and the Allow-directive gotcha that silently kills carve-outs), see the robots.txt guide. robots.txt governs whether Amzn-User may fetch; llms.txt is the separate, curated map AI assistants read once allowed in.
Vendor documentation: https://developer.amazon.com/amazonbot
The Amazon family
Amazon operates 3 distinct tokens in this roster, and they do not block each other: a robots.txt line for Amzn-User does nothing to its siblings — each needs its own User-agent: entry (the robots.txt guide has combined patterns).
| Token | Role | robots.txt |
|---|---|---|
| Amazonbot | Training | honors robots.txt |
| Amzn-SearchBot | AI search | honors robots.txt |
Frequently asked questions
What is Amzn-User?
Amzn-User is Amazon's user action crawler. A live fetch made because a human asked the assistant about your page right now. Closest thing to a real visitor; several of these (Perplexity-User, meta-externalfetcher) ignore robots.txt by design because the request is user-initiated.
Does Amzn-User respect robots.txt?
Amazon claims Amzn-User respects robots.txt, but compliance is not independently confirmed.
How do I block Amzn-User?
Add 'User-agent: Amzn-User' followed by 'Disallow: /' to your robots.txt. Use the exact token — substring variants of other tokens will not match.
How do I verify Amzn-User traffic by IP?
Amazon publishes Amzn-User's IP ranges on a documentation page (not machine-readable JSON); cross-check the hit's source IP against the listed ranges manually.
Related bots
Same vendor, then other user-action fetchers — the full directory profiles all 34.