ggit-tower.com

The robots.txt points crawlers at a sitemap URL its own rules forbid them to fetch.

Consequence. The sitemap cannot be read, so none of the URLs it lists are submitted. The declaration gives a false impression that discovery is handled.

If that is not intended. Add an Allow rule for the sitemap path, or narrow the Disallow rule that covers it.

• https://www.git-tower.com/docs/ai/sitemap-ai.xmlL46Blocked by "Disallow: /docs/ai/" on line 10

Blocked: CCBot.

• CCBotCommon CrawlL13

  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 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.

The page sends no robots meta tag and no X-Robots-Tag header.

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://www.git-tower.com/docs/ai/sitemap-ai.xmlL46Not fetched: the robots.txt of its own origin does not let our bot fetch it

Every line parses as a directive crawlers understand.

Comfortably within the 500 KB that crawlers will read.