1 user-triggered fetch is blocked while the same operator may still collect content
ChatGPT-User is blocked while OAI-SearchBot may crawl.
ChatGPT-UserOpenAIL61
A ChatGPT user opening this page
"Disallow: /" blocks ChatGPT-User.
If that is the intention. If your intention is to block AI entirely, this configuration does not achieve it: the content is still being collected.
Consequence. This is the opposite of what either intent would produce. Blocking bulk collection while allowing people through is a common position; allowing bulk collection while turning away someone who asked for the page is not one anyone sets out to take. It usually means a rule aimed at AI crawlers named the wrong user agent.
If that is not intended. Decide which way round it should be. To keep people out but content in, no change is needed — but that is rarely the intent. To block collection instead, disallow the collecting agents named here and allow the user-triggered ones.
Info
1 of 6 search engines are blocked
Blocked: YandexBot.
YandexBotYandexL54
Yandex
"Disallow: /" blocks YandexBot.
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.
Info
1 of 3 user-triggered AI fetches are blocked
Blocked: ChatGPT-User.
ChatGPT-UserOpenAIL61
A ChatGPT user opening this page
"Disallow: /" blocks ChatGPT-User.
If that is the intention. If your intention is to prevent assistants from fetching pages when a person asks for them, the current configuration achieves that for these crawlers — the rest of the group is still allowed.
Consequence. When someone asks an assistant to open a page on this site, it cannot be retrieved. These requests are made because a person asked for that specific page, not to collect content in bulk.
If that is not intended. Allow these agents globally, or only on the sections you want retrievable.
Info
2 of 6 AI training crawlers are blocked
Blocked: GPTBot, CCBot.
GPTBotOpenAIL64
OpenAI model training
"Disallow: /" blocks GPTBot.
CCBotCommon CrawlL70
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.
Pass
AI answer engines can reach the site
All 4 checked AI answer engines are allowed at the site root.
Pass
Social link previews can reach the site
All 5 checked social link previews are allowed at the site root.
Pass
No indexing directives on the requested page
The page sends no robots meta tag and no X-Robots-Tag header.
Pass
1 sitemap declared
Every declared sitemap is an absolute URL and is crawlable.
https://qgis.org/sitemap.xmlL35
Pass
No syntax problems
Every line parses as a directive crawlers understand.
Pass
File size is 1.4 KB
Comfortably within the 500 KB that crawlers will read.
