Lines that do not parse as a known directive: invalid_path.
Consequence. A crawler skips what it cannot parse, without reporting anything. A misspelled "Dissalow" leaves a path fully crawlable while the file appears to restrict it.
If that is not intended. Correct the spelling of each field name, and make sure every line follows "Field: value". Rules must also appear after a User-agent line to belong to a group.
Path '*/presented/' should start with '/'L41invalid_path
Path '*/integrated/' should start with '/'L42invalid_path
Info
1 of 6 search engines are blocked
Blocked: Baiduspider.
BaiduspiderBaiduL110
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.
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.
Info
2 of 3 user-triggered AI fetches are blocked
Blocked: Perplexity-User, Claude-User.
Perplexity-UserPerplexityL110
A Perplexity user opening this page
"Disallow: /" blocks Perplexity-User.
Claude-UserAnthropicL110
A Claude user opening this page
"Disallow: /" blocks Claude-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.
Common Crawl, widely redistributed as training data
"Disallow: /" blocks CCBot.
AmazonbotAmazonL110
Amazon model training and Alexa
"Disallow: /" blocks Amazonbot.
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
Social link previews can reach the site
All 5 checked social link previews are allowed at the site root.
Not checked
Page directives were not checked
The page answered HTTP 403, 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.
Pass
2 sitemaps declared
Every declared sitemap is an absolute URL and is crawlable.
