CrawlPactFree tools
Free validators for the public signals CrawlPact's full audit evaluates together. Each one runs a full scan of the domain you enter and takes you straight to the relevant section of the report.
A tool, or the full audit?
Use an individual tool when you already know which signal you care about — for example, confirming a single crawler is blocked, or checking whether an llms.txt file validates. Use the full audit when you want every signal evaluated together, a Policy Health Score, and conflict detection across signals (for example, robots.txt allowing a crawler that RSL prohibits).
AI crawler checker
Check whether a specific documented AI crawler appears allowed or blocked for a domain.
Robots.txt AI validator
Validate robots.txt syntax and AI-crawler-specific groups against RFC 9309 behaviour.
RSL validator
Validate supported RSL syntax and view declared permissions and prohibitions.
llms.txt validator
Validate llms.txt and llms-full.txt structure and linked resources.
Content Signals checker
Detect recognised Content Signals and identify contradictions with crawler-specific rules.
How these work
Enter a domain or full URL. CrawlPact retrieves the relevant public resource directly — no account, no installation, and no server-log access required. Only the specific, bounded resources relevant to AI crawler policy are retrieved and stored; see scanner informationfor exactly what is and isn't fetched, and privacy for retention.
Every tool here uses the same parser and rules as the full audit — there is no separate, simplified logic that could disagree with it. See methodology for how each signal is evaluated, and limitations for what a result does and doesn't prove.