ssitepoint.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: 10L63

Blocked: Google-Extended.

• Google-ExtendedGoogleL121

  Google AI Overviews and Gemini grounding

  "Disallow: /" blocks Google-Extended.

If that is the intention. If your intention is to keep the site out of AI-generated answers, the current configuration achieves that for these crawlers — the rest of the group is still allowed.

Consequence. The site cannot be cited as a source in AI-generated answers. Unlike training crawlers these send referral traffic, so blocking them forfeits those visits.

If that is not intended. Remove the matching Disallow rule, or allow these agents on the sections you want cited.

Blocked: GPTBot, CCBot.

• GPTBotOpenAIL121

  OpenAI model training

  "Disallow: /" blocks GPTBot.

• CCBotCommon CrawlL121

  Common Crawl, widely redistributed as training data

  "Disallow: /" blocks CCBot.

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 3 checked user-triggered AI fetches are allowed at the site root.

All 5 checked social link previews 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.

Every declared sitemap is an absolute URL and is crawlable.

• https://www.sitepoint.com/sitemap-index.xmlL2
• https://www.sitepoint.com/community/sitemap.xmlL3
• https://www.sitepoint.com/premium/sitemap.xmlL4
• https://jobs.sitepoint.com/sitemap.xmlL5
• https://www.sitepoint.com/tutorials/sitemap.xmlL6

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.