Amazonbot: robots token, verification and how to allow or disallow it

All 21 documented crawlers

Identity

Vendor text fetched on 2026-09-17: 'Automated crawling from these listed user agents respects the Robots Exclusion Protocol, honoring the user-agent and the allow/disallow directives.' The reverse DNS suffix comes from app/botverify.py (existing fleet data), not from this page. The published IP address URL recorded here is the one the vendor page names for Amazonbot itself; it answered http 200 on 2026-09-17. It had pointed at the list the same page names for Amzn-User, which is now a registry entry of its own.

Allow or disallow it

User-agent: Amazonbot
Allow: /

User-agent: Amazonbot
Disallow: /

A robots.txt rule is a request that a well behaved crawler honours. It is not an access control, and this page does not tell anyone what to choose.

Build a robots.txt with Amazonbot and every other documented token

Questions

Does Amazonbot obey robots.txt?

The vendor documentation at https://developer.amazon.com/amazonbot states that Amazonbot respects robots.txt. We fetched that page and it answered our checker on 2026-09-17. This records what the vendor documents, not what any individual request did.

How do I allow Amazonbot in robots.txt?

Add this group to the robots.txt at the root of the host: User-agent: Amazonbot Allow: /. The token is matched case insensitively as a substring of the user agent by RFC 9309, and the longest matching rule wins.

How do I disallow Amazonbot in robots.txt?

Add this group to the robots.txt at the root of the host: User-agent: Amazonbot Disallow: /. A robots.txt rule is a request that a well behaved crawler honours; it is not an access control.

How do I verify a request really came from Amazonbot?

The vendor documents reverse DNS verification: look up the address of the request, check the name ends in .crawl.amazonbot.amazon, then look that name up again and confirm it resolves back to the same address.

What we measure

Of the 12976 seeded domains whose robots.txt we have read, 1462 disallow Amazonbot for / and 11514 allow it, which is 11.3% disallowed, week 2026-W43. Counts only: no domain is named.

The weekly AI crawler access index

Sources

Free data

• The AEO Watch dataset
• Tranco top 1,000 AI crawler policy (CSV, CC BY 4.0)
• The AEO Watch API
• The checker as a command line tool (one file, no install)

Check a domain against every token

Check your own site

The same checks, run on your domain now: what robots.txt tells each AI crawler, whether the edge answers them, and whether the text is readable without JavaScript. Free, no signup.

Limits: 8 checks and 5 different domains per address per hour; a repeat of the same domain inside 7 days is answered from what we already hold.

AEO Watch is an independent, factual monitor. It is not affiliated with, endorsed by or speaking for any crawler vendor. Every statement is an observation with the date it was made and the raw evidence behind it: a robots.txt line, an HTTP status code, a header. There are no scores, no grades and no verdicts here, and nothing on this page is advice. A site opts out at any time and the opt out is honoured automatically and permanently.