ttremendous.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: 2L17

Blocked: YandexBot, Baiduspider.

• YandexBotYandexL30

  Yandex

  "Disallow: /" blocks YandexBot.

• BaiduspiderBaiduL30

  Baidu

  "Disallow: /" blocks Baiduspider.

If that is the intention. If your intention is to keep the site out of the major search indexes, the current configuration achieves that for these crawlers — the rest of the group is still allowed.

Consequence. These search engines cannot crawl the site, so its pages will not appear in their results. Note that robots.txt does not remove URLs that are already indexed — it stops them being re-crawled.

If that is not intended. Remove the matching Disallow rule, or give these crawlers their own group with an Allow rule. Path matching is longest-wins, so a specific Allow overrides a broader Disallow.

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 sends no robots meta tag and no X-Robots-Tag header.

Every declared sitemap is an absolute URL and is crawlable.

• https://www.tremendous.com/sitemap.xmlL32

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.