# 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.

Canonical page: https://getrankroot.com/ai-bots/amzn-user · Facts checked against Amazon docs on 2026-10-20

| Operator | Used for | Type | Obeys robots.txt |
| --- | --- | --- | --- |
| Amazon | Alexa (user requests) | User-triggered fetcher | Not reliably |

## 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

Allow Amzn-User:

```
User-agent: Amzn-User
Allow: /
```

Block Amzn-User:

```
User-agent: Amzn-User
Disallow: /
```

Disallow Amzn-User from one folder only:

```
User-agent: Amzn-User
Disallow: /private/
Allow: /
```

A bot follows the most specific User-agent group that names it and ignores the generic `User-agent: *` group, so repeat any shared Disallow lines inside it.

This fetcher does not reliably follow robots.txt, so a Disallow rule may have little effect.

## Same company, different bots: Amazon

| Bot | Type | Purpose | Obeys robots.txt | If you block it |
| --- | --- | --- | --- | --- |
| [Amazonbot](https://getrankroot.com/ai-bots/amazonbot.md) | AI 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-SearchBot](https://getrankroot.com/ai-bots/amzn-searchbot.md) | AI search index | Alexa and Amazon search | Yes | Your content is no longer eligible to appear in Amazon search experiences such as Alexa. |
| [Amzn-User](https://getrankroot.com/ai-bots/amzn-user.md) | User-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 string

```
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amzn-User/0.1) Chrome/W.X.Y.Z Safari/537.36
```

## How to verify it's really Amzn-User

Find its requests in your server logs:

```
grep -i "Amzn-User" access.log
```

Amazon publishes a separate IP address list for each of its crawlers.

Published IP list: https://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

### What is 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.

### Does Amzn-User respect robots.txt?

Not reliably. Amazon says user-requested fetches may not follow robots.txt.

### What happens if I block Amzn-User?

A robots.txt rule may not fully apply; Amazon says it may not follow all directives.

### Should I block Amzn-User?

Leave it allowed.

## Sources

- [Official documentation from Amazon](https://developer.amazon.com/amazonbot)
- [Published IP addresses for Amzn-User](https://developer.amazon.com/amazonbot/live-ip-addresses/)

Check whether Amzn-User can reach a site: https://getrankroot.com/tools/ai-crawler-checker or `GET https://getrankroot.com/api/bots?url=example.com`. Full list: https://getrankroot.com/ai-bots.md