3 warning · 2 notice · 3 info · 1 not checked · 3 pass
100 crawlers named · 15 unrecognised
What this file says about crawlers
Not checked
Who this file lets in
AI Data Scraper all 25 blocked
AI Search Crawler all 14 blocked
Unrecognised all 14 blocked
AI Assistant all 14 blocked
Undocumented AI Agent all 10 blocked
Uncategorized all 8 blocked
Intelligence Gatherer all 6 blocked
AI Agent all 3 blocked
Path Access Checker
Detailed Analysis
Warning
No sitemap is declared
The file contains no "Sitemap:" line.
Consequence. Crawlers have to discover every URL by following links. Pages that are deep, newly published, or poorly linked internally take longer to be found, and some may never be. A sitemap is the most direct way to hand a crawler the full list.
If that is not intended. Publish an XML sitemap and declare it with an absolute URL, e.g. "Sitemap: https://example.com/sitemap.xml". The line is global — it belongs outside any User-agent group and applies to every crawler.
Warning
1 line will be ignored by crawlers
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 '*/gcrnsts' should start with '/'L65invalid_path
Warning
1 rule names a location nobody would have guessed
Rules name a sensitive location made specific by a qualifier or by where it sits, or a spreadsheet by its full path.
Consequence. A bare "/backup" is in every scanner wordlist; "/backup-2023/" is in none. Listing it advertises the location to the readers least likely to honour the rule.
If that is not intended. Put these locations behind authentication or remove them; once they are protected, the line can stay or go. Responses behind authentication are not indexed, so they need no "noindex". Content that is public by design and only has to stay out of search wants a "noindex" without the Disallow: a crawler only sees a noindex on a page it may fetch.
Disallow: /gp/legacy-handle-buy-box.htmlL20"legacy" with a qualifier
Notice
5 rules can never take effect
A broader rule of the same type already covers these paths.
Consequence. These lines change nothing. They are harmless, but they add length to a file that has a size limit, and they make the real policy harder to read.
If that is not intended. Remove the redundant rules, or narrow the broader rule if it is catching more than intended.
disallow: /gp/dmusic/orderL19Already covered by "disallow: /gp/dmusic/" on line 80
disallow: /gp/dmusic/order/handle-buy-box.htmlL38Already covered by "disallow: /gp/dmusic/order" on line 19
disallow: /gp/registry/wishlist/*/reserveL47Already covered by "disallow: /gp/registry/wishlist/" on line 51
disallow: /gp/dmusic/mp3/playerL67Already covered by "disallow: /gp/dmusic/" on line 80
disallow: /creatorhub/*L103Already covered by "disallow: /creatorhub" on line 102
Notice
1 rule is declared more than once
The same directive and path appear repeatedly within one group.
Consequence. Duplicates have no effect on crawling, but they inflate the file toward the 500 KB limit and usually signal that the file is generated without dedup.
If that is not intended. Remove the repeats.
disallow: /gp/associations/wizard.htmlL33Already declared on line 18 for *
If that is the intention. If your intention is to keep the site out of AI-generated answers, the current configuration achieves that.
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.
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.
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.
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
Search engines can reach the site
All 6 checked search 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.
Not checked
Page directives were not checked
The page answered HTTP , 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
File size is 7.8 KB
Comfortably within the 500 KB that crawlers will read.
