ffreshbooks.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: 10L21

Blocked: Bytespider.

• BytespiderByteDanceL10

  ByteDance model training

  "Disallow: /" blocks Bytespider.

If that is the intention. If your intention is to prevent this content being used as model training data, the current configuration achieves that for these crawlers — the rest of the group is still allowed.

Consequence. These crawlers cannot retrieve content from the site, so it will not be collected as training data. They send no traffic back, and blocking them does not affect search rankings.

If that is not intended. Remove the site-wide block, or replace it with narrower path restrictions.

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.

1 meta tag and 0 X-Robots-Tag headers, with no contradictions.

• <meta name="robots" content="index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1">Page HTML

Every declared sitemap is an absolute URL and is crawlable.

• https://www.freshbooks.com/sitemap_index.xmlL41

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.