Amazonbot
Amazonbot is blocked by 719 sites in the October 2026 survey, or 11.7% of readable files. The community reference lists its operator as Amazon.
Who runs Amazonbot?
| Fact | Amazonbot reference entry |
|---|---|
| Operator | “Amazon” |
| Purpose | “Service improvement and enabling answers for Alexa users.” |
| Does Amazonbot obey robots.txt? | “Yes” |
| Frequency | “No information provided.” |
| Cloudflare managed list for Amazonbot | Yes |
These facts quote the stored community ai.robots.txt reference.
“Includes references to crawled website when surfacing answers via Alexa; does not clearly outline other uses.”
This entry’s stated use is quoted above. A site can welcome a page fetch prompted by a person while declining the collection of that text to build future models.
How many sites block it?
Our readable sample has 719 whole-site blocks, 11.7% of 6,171 files, with Disallow: / as the instruction. Of that full sample, 666 name this crawler, or 10.8%. The count without a whole-site block is 5,452.
For the top 1,000 ranks, its name appears in 77 files out of 552, or 13.9%. Whole-site blocks total 84. Blocking is more common among the leading sites, at 15.2%. Lower in the ranking, blocking reaches 635 files out of 5,619, a 11.3% share.
| Readable files | Named by | Named share | Blocked by | Blocked share |
|---|---|---|---|---|
| Amazonbot, all ranks | 666 | 10.8% | 719 | 11.7% |
| Amazonbot, top 1,000 | 77 | 13.9% | 84 | 15.2% |
| Amazonbot, remaining ranks | 589 | 10.5% | 635 | 11.3% |
A general User-agent: * ban contributes to this total whenever it applies to this crawler. Of 719 blocks, 199 come only from that general rule, without naming this crawler. The naming total includes 520 files with a ban on every path and 146 files without that ban. Elsewhere, 5,505 files do not name it. We ignore capitalization and repeated names.
Has that changed since August?
Between August and October, 169 sites that had blocked it stopped and 57 started, so 112 fewer of the same 5,889 sites block it. A further 617 blocked it in both months, and 5,046 did so in neither. Keeping the sites the same lets us count changes in their rules.
August’s full sample had 897 blocks among 6,236 readable files. October’s was 719 among 6,171. Those monthly totals also reflect which files we could read on each visit.
| August to October | Files |
|---|---|
| Started blocking | 57 |
| Stopped blocking | 169 |
| Blocked in both | 617 |
| Blocked in neither | 5,046 |
| Net change | -112 |
How to block or allow it
Place the group in your root robots.txt file. Per the robots.txt standard, a named group for Amazonbot overrides User-agent: *.
Block the whole site
User-agent: Amazonbot
Disallow: /Allow access
User-agent: Amazonbot
Allow: /It's the 9th most-named crawler of the 171 we counted in the crawler index.
Which other crawlers does this operator run?
How we counted
For Amazonbot, we surveyed Tranco’s top 10,000 sites on 19 October 2026. Files had an 8-second timeout and a 262,144-byte limit. Missing, unreachable and oversized files do not contribute to these shares. The file readings, including repeats, use scripts/robots_2026_08_06.py (robots.py at app commit 07104ff). See the full survey method.
Common questions
What does naming this crawler tell me?
A name identifies the crawler addressed by a group. The survey found 146 files with that name and no recorded whole-site ban, out of 666.
Are leading sites different?
Leading files record 13.9% with the name and 15.2% blocking it. Across all readable files, the corresponding shares are 10.8% and 11.7%.
How does the nearby crawler compare?
For comparison, Applebot-Extended has 658 files naming it and 694 blocks, or 11.2%. Our counts for this entry are 666 files with the name and 719 blocking the whole site, or 11.7%.