Amazonbot — Amazon's ai training crawler

Amazonbot crawls broadly and persistently; multiple publishers and infrastructure providers have flagged its aggregate volume as disproportionate to any visible traffic return.

The visibility payoff is opaque: Alexa answers rarely cite or link sources in a way that returns measurable traffic, which distinguishes Amazonbot from search indexers whose citations you can at least measure.

Amazonbot identifies itself with the following user-agent string:

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/600.2.5 (KHTML, like Gecko) Version/8.0.2 Safari/600.2.5 (Amazonbot/0.1; +https://developer.amazon.com/support/amazonbot)

Never trust the user-agent string alone. Scrapers routinely impersonate well-known crawlers to inherit their access. Amazon documents Amazonbot and supports reverse-DNS verification of its crawler hosts; validate suspect traffic before whitelisting the user-agent string.

Note that most AI crawlers and fetchers, Amazonbot included, do not execute JavaScript — so this traffic is invisible to GA4 and every script-based analytics tool. Server logs, CDN analytics, or a dedicated bot-analytics layer are the only places you will see it. For the full picture of measuring AI-driven visits, see our guide on how to track AI traffic.

To refuse Amazonbot access to your entire site, add this to your robots.txt:

User-agent: Amazonbot
Disallow: /

To restrict it from specific sections only (for example, premium content) while leaving the rest open:

User-agent: Amazonbot
Disallow: /premium/
Disallow: /members/

The case for blocking: High crawl cost, negligible referral return, and training use for a commercial assistant: the ledger reads like a training crawler's, and many publishers treat it as one and block it.

The case for allowing or monetizing: As with other training-type access, the coherent path is licensed access rather than free crawling — Amazon licenses plenty of data commercially and can license yours.