Amazonbot
One token covering both Alexa answers and Amazon AI training. There is no way to split them.
| Operator | Amazon |
|---|---|
| What it does | Search & training |
| Obeys robots.txt | Yes, per its operator's docs |
| Governs | AI model training |
| Has a crawler | Yes |
| Last verified | 13 August 2026 |
What blocking it costs you
What to know
That is the finding here. If you want out of Amazon's training data, the same rule takes you out of Alexa's answers, and Amazon offers no second token to separate the two. It is a genuine trade-off rather than an oversight to work around.
Amazonbot caches robots.txt for up to 30 days, so a rule change here takes effect slowly. If you make a change and check the next day, you will not see it. It honours noarchive and noindex.
The robots.txt rules
To block Amazonbot:
User-agent: Amazonbot
Disallow: /To allow it explicitly — worth doing when your file also contains a blanket User-agent: * disallow, since the most specific matching group wins and a token with no group of its own falls back to the wildcard:
User-agent: Amazonbot
Allow: /If neither rule is present, Amazonbot is allowed. That is the default, and it is why an accidental block is nearly always something that was added rather than something that was forgotten — usually a snippet copied from a blog post that listed more tokens than the author intended to block.
Is it blocked on your site?
Your robots.txt is only the half you can read. A CDN or bot-management rule can turn Amazonbot away while your file still says it is welcome, and that mismatch is invisible from the front of the site. We check both layers separately and tell you which one is doing what.
We request two things: your robots.txt and your homepage. No other pages, ever.
Official sources
- Amazon’s crawler documentation
- Published IP ranges — the only way to verify a request claiming this user agent really came from Amazon