AI crawler list · Amazon · User-triggered fetcher
Amzn-User
Fetches live web information to answer Alexa users. Amazon says it may not follow all robots.txt directives because it is user-initiated, and it does not crawl for generative AI training.
Facts checked against Amazon docs on Oct 20, 2026.
Is Amzn-User allowed on your site?
Reads your robots.txt and requests your page as each AI bot. Free, no signup.
Should you allow it?
Leave it allowed.
If you block it: A robots.txt rule may not fully apply; Amazon says it may not follow all directives.
robots.txt rules
User-agent: Amzn-User Allow: /
User-agent: Amzn-User Disallow: /
User-agent: Amzn-User Disallow: /private/ Allow: /
Put each User-agent group in the robots.txt at your domain root. A bot follows the most specific group that names it and ignores the generic User-agent: * group, so repeat any shared Disallow lines inside it. Build a full file with the AI robots.txt generator.
This fetcher does not reliably follow robots.txt, so a Disallow rule may have little effect.
Same company, different bots: Amazon
Amazon uses separate user agents for separate jobs. Blocking one does not block the others.
| Bot | Purpose | Obeys robots.txt | If you block it |
|---|---|---|---|
AmazonbotAI training crawler | Amazon products and AI | Yes | Stops the Amazon crawler whose data may be used to train Amazon AI models. Alexa search uses Amzn-SearchBot instead. |
Amzn-SearchBotAI search index | Alexa and Amazon search | Yes | Your content is no longer eligible to appear in Amazon search experiences such as Alexa. |
Amzn-UserUser-triggered fetcher | Alexa (user requests) | Not reliably | A robots.txt rule may not fully apply; Amazon says it may not follow all directives. |
User-agent: Amzn-SearchBot User-agent: Amzn-User Allow: / User-agent: Amazonbot Disallow: /
User agent string
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amzn-User/0.1) Chrome/W.X.Y.Z Safari/537.36
Versions in the string can change. Match on the token Amzn-User, and verify real traffic as shown below rather than trusting the header.
How to verify it's really Amzn-User
Find its requests in your server logs (the path to your access log depends on your host):
grep -i "Amzn-User" access.log
Amazon publishes a separate IP address list for each of its crawlers.
Published IP list: developer.amazon.com/amazonbot/live-ip-addresses/
Common mistakes
- Writing a User-agent: Amzn-User group and expecting your User-agent: * rules to still apply. A crawler follows only the most specific group that matches it and ignores the others, so repeat any shared Disallow lines inside the Amzn-User group.
- Leaving a CDN or host "block AI bots" setting on and only checking robots.txt. Those settings block requests at the network edge. Cloudflare, for example, changed its defaults on September 15, 2026 for customers who did not opt out: bots it classifies as Training or Agent are blocked on pages that display ads, and multi-purpose crawlers that combine Search and Training are affected by the Training block.
- Trusting the user agent header alone. Anyone can send "Amzn-User" in a request; verify the source IP as shown above before allowlisting or blocking.
FAQ
Fetches live web information to answer Alexa users. Amazon says it may not follow all robots.txt directives because it is user-initiated, and it does not crawl for generative AI training.
Not reliably. Amazon says user-requested fetches may not follow robots.txt.
A robots.txt rule may not fully apply; Amazon says it may not follow all directives.
Leave it allowed.
Sources
- Official documentation from Amazon
- Published IP addresses for Amzn-User
- Cloudflare bots changelog (AI bot policy defaults)
Related AI crawlers
ChatGPT-User · OAI-AdsBot · Claude-User · Perplexity-User · Google-CloudVertexBot · meta-externalfetcher · Amazonbot · Amzn-SearchBot
Facts checked against Amazon docs on Oct 20, 2026. Spot an error? rankroot.support@proton.me