Amazonbot vs GPTBot: Which AI Crawler Should You Allow or Block?

Mistakes when writing rules for Amazonbot and GPTBot together

Amazonbot is named in 10.6% of the top-site robots.txt files in our study and blocked in 12.2%; GPTBot is named in 18.1% of the top-site robots.txt files in our study and blocked in 15.4%. Large sites block GPTBot more often, which usually reflects a decision about training rather than about Amazonbot.

1. Both are a training crawlers, so the usual error is treating a rule for one as a rule for both. A group for Amazonbot says nothing about GPTBot; if you want the same treatment, list both lines above one set of rules.
2. They come from different operators (Amazon and OpenAI), with different documentation and different update cycles. Do not assume a change one of them announces applies to the other.
3. Putting User-agent: Amazonbot and User-agent: GPTBot in separate groups and then editing only one. Two groups drift apart over time; keep a comment above each that says why it differs from the other.

Each crawler's own profile lists the mistakes that apply to it alone; this list is only about combining the two.

Spotting Amazonbot and GPTBot in your logs

robots.txt says what Amazonbot and GPTBot may do; your access logs show what they actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "Amazonbot|GPTBot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "Amazonbot|GPTBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send these user-agents, so confirm the source before acting on a match:

• Amazonbot: we hold no published IP list, so use reverse DNS where Amazonbot and GPTBot documents a hostname and treat an unverifiable Amazonbot request with caution. Check it separately from GPTBot.
• GPTBot: compare each address with the ranges at openai.com/gptbot.json. A request claiming to be GPTBot from outside them is not genuine. Check it separately from Amazonbot.

How Amazonbot and GPTBot moved in our latest scans

Between our scans of October 17, 2026 and October 20, 2026, files naming Amazonbot went from 543 to 593 (+50) and files blocking it from 624 to 680 (+56), so more sites wrote a rule for Amazonbot and more of those rules block it. For comparison, 2026 and October 20, 2026, files naming GPTBot went from 941 to 1,008 (+67) and files blocking it from 789 to 859 (+70), so more sites wrote a rule for GPTBot and more of those rules block it.

Over the 3 days between those scans, blocking of Amazonbot moved +56 files and blocking of GPTBot moved +70. Owners are acting faster on GPTBot, which is the one to recheck first if you have not touched your file this month.

We first recorded Amazonbot on March 17, 2026. Amazon documents it on developer.amazon.com, and we recheck that page before each release. We first recorded GPTBot on March 17, 2026. OpenAI documents it on developers.openai.com, and we recheck that page before each release.

Among the 3 cloud services in our database, Amazonbot sits first by priority (Tier 2), alone in its tier. 3 of the 3 share its safe rating. On the GPTBot side: Among the 104 AI and LLM crawlers in our database, GPTBot sits ninth by priority (Tier 1), level with ChatGPT Agent, ChatGPT Operator, ChatGPT-User, ChatGPT-User/2.0. 81 of the 104 share its safe rating.

How top sites treat Amazonbot and GPTBot

From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):

• GPTBot, the most blocked of the Amazonbot and GPTBot tokens: blocked in 15.4% of files (663 with its own group, 196 through User-agent: *), more often by the top 1,000 (20.4%) than the long tail (14.5%).
• Amazonbot, second of the Amazonbot and GPTBot tokens: blocked in 12.2% of files (464 with its own group, 216 through User-agent: *), more often by the top 1,000 (15.6%) than the long tail (11.9%).

For scale, 20.1% of all files block at least one AI training crawler. GPTBot is one of the tokens driving that figure.

More questions about Amazonbot and GPTBot

Can I allow one and block the other?

Yes. Give each its own User-agent group with its own rules. Each crawler reads only the group that names it.

Which of the two visits more often?

It depends on your site, your audience and how often your content changes. Your access logs are the reliable answer; the commands above count both.

How long until a change applies?

Crawlers commonly cache robots.txt for up to a day, so allow about 24 hours and confirm in your logs.

Do I need to update my rules when either operator launches a new crawler?

Often, yes. A new token is not covered by rules written for the old ones. Check this comparison and both profiles periodically, or rerun the AI bot crawlability test after any announcement.