Crawl-delay is declared 3 times and Google ignores it
Crawl-delay was never part of the standard. Google has never supported it; Bing and Yandex do.
Consequence. Any rate limit intended for Googlebot is not being applied. If the goal was to reduce load from Google specifically, it is not working.
If that is not intended. Set the crawl rate for Google in Search Console instead. Keep the directive if the limit is meant for Bing or Yandex, which do honour it.
Crawl-delay: 10L49
Crawl-delay: 10L58
Crawl-delay: 10L67
Info
1 of 6 AI training crawlers are blocked
Blocked: Amazonbot.
AmazonbotAmazonL6
Amazon model training and Alexa
"Disallow: /" blocks Amazonbot.
If that is the intention. If your intention is to prevent this content being used as model training data, the current configuration achieves that for these crawlers — the rest of the group is still allowed.
Consequence. These crawlers cannot retrieve content from the site, so it will not be collected as training data. They send no traffic back, and blocking them does not affect search rankings.
If that is not intended. Remove the site-wide block, or replace it with narrower path restrictions.
Pass
Search engines can reach the site
All 6 checked search engines are allowed at the site root.
Pass
AI answer engines can reach the site
All 4 checked AI answer engines are allowed at the site root.
Pass
User-triggered AI fetches can reach the site
All 3 checked user-triggered AI fetches are allowed at the site root.
Pass
Social link previews can reach the site
All 5 checked social link previews are allowed at the site root.
Pass
No indexing directives on the requested page
The page sends no robots meta tag and no X-Robots-Tag header.
Pass
1 sitemap declared
Every declared sitemap is an absolute URL and is crawlable.
https://fakemayo.com/sitemap.xmlL25
Pass
No syntax problems
Every line parses as a directive crawlers understand.
Pass
File size is 1.6 KB
Comfortably within the 500 KB that crawlers will read.
