Crawl-delay is declared 2 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: 0L106
Crawl-delay: 1L110
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
Page indexing directives are consistent
1 meta tag and 2 X-Robots-Tag headers, with no contradictions.
<meta name="robots" content="index, follow">Page HTML
X-Robots-Tag: allRobots.txt response
X-Robots-Tag: allPage response
Not checked
1 declared sitemap was not checked
These sitemaps were not seen: each was blocked for our bot, left out by a limit, or did not answer in time. Each line says which.
Consequence. Nothing is known about whether they work. They are not counted against the file.
https://slashdev.io/api/link-archive-sitemap.xmlL3Not fetched: robots.txt does not let our bot fetch it
Pass
No syntax problems
Every line parses as a directive crawlers understand.
Pass
File size is 2.5 KB
Comfortably within the 500 KB that crawlers will read.
