Crawl-delay is declared 7 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: 10L56
Crawl-delay: 10L59
Crawl-delay: 10L62
Crawl-delay: 10L65
Crawl-delay: 10L68
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.
Not checked
Page directives were not checked
The page answered HTTP 403 with a bot challenge instead of its content, so its meta robots tags and X-Robots-Tag headers were not read.
Consequence. Nothing is known about whether this page asks to be kept out of search results. Its absence of directives here proves nothing either way.
If that is not intended. Analyse the page again once it answers normally to our bot.
Pass
1 sitemap declared
Every declared sitemap is an absolute URL and is crawlable.