ccopyleaks.com

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: 10L13
• Crawl-delay: 0L29

All 6 checked search engines are allowed at the site root.

All 4 checked AI answer engines are allowed at the site root.

All 3 checked user-triggered AI fetches are allowed at the site root.

All 5 checked social link previews are allowed at the site root.

All 6 checked AI training crawlers are allowed at the site root.

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.

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://copyleaks.com/sitemap_index.xmlL33Not fetched: only the first few sitemaps are fetched, within a time limit and the site's Crawl-delay

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.