Forum Moderators: open

Message Too Old, No Replies

AmazonBot ignoring robots.txt

3.208.0.0/12

         

Bewenched

5:49 pm on Jun 4, 2025 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



we have it disallowed in our robots.txt, never even asked for it.
blocked entire range 3.208.0.0/12

3.222.190.107 (United States)6/4/2025 7:34:30 AM/example.html854287301 - Moved PermanentlyGETNo ReferrerMozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Amazonbot/0.1; https://developer.amazon.com/support/amazonbot) Chrome/119.0.6045.214 Safari/537.36

Bad bot go away

[edited by: not2easy at 2:03 am (utc) on Jun 5, 2025]
[edit reason] de-linked bot URL [/edit]

lucy24

10:59 pm on Jun 4, 2025 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Psst! If you put the UA in [ code ] markup, it prevents auto-linking:
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)

Now, here’s an oddity. Looking through recent logs, I find that since mid-December of 2024, Amazonbot has requested nothing but robots.txt, where it is ...

... Whoops! Thanks to that “Chrome” in the UA, it’s been getting a comprehensive Disallow. My bad; it’s been authorized (in htaccess) for a goodish while. But it does tell me that, from any IP, it appears to be fully robots.txt compliant.

I have now made a change, and will see how it behaves in future weeks. In particular, will it stay out of Disallowed directories?

I should note that the version of robots.txt that it has been getting is the minimalist
User-Agent: *
Disallow: /
It is possible that some robots respond better to this form than to a more complex robots.txt.