Crawl-delay is declared 4 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: 3L28
Crawl-delay: 3L31
Crawl-delay: 3L34
Crawl-delay: 3L37
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
AI training crawlers can reach the site
All 6 checked AI training crawlers 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://www.hackerrank.com/sitemap.xmlL39
Pass
No syntax problems
Every line parses as a directive crawlers understand.
Pass
File size is 680 bytes
Comfortably within the 500 KB that crawlers will read.
