1. Source
Live robots.txt fetch. The result identifies where its evidence came from.
Check and test any website's robots.txt for free. See its HTTP status, crawl rules grouped by user-agent, allow and disallow counts, any declared sitemaps, and whether it accidentally blocks the whole site.
Submit a public URL, domain, or keyword. Novaverb will show only the evidence this tool can actually retrieve or measure.
Each free check separates measured evidence from interpretation, and interpretation from the deeper work available in a connected workspace.
Live robots.txt fetch. The result identifies where its evidence came from.
The checker fetches /robots.txt and reads its directives. robots.txt is a crawl directive, not access control or index removal; this tool does not simulate a specific crawler's policy.
Use the finding to verify a problem, then connect a workspace when you need history, monitoring, or site-wide analysis.
robots.txt tells compliant crawlers which paths they may request. It is the first file most crawlers fetch, so a single wrong line can quietly keep a whole site out of search — or let private paths be crawled.
A clear robots.txt reduces ambiguity for search and AI crawlers. Novaverb can use this signal as part of a broader crawl and technical evidence model, alongside indexability, canonicals and internal links.
Yes. You can run the public check without creating an account. A connected workspace is required only for saved evidence, monitoring, and deeper product workflows.
Live robots.txt fetch. The checker fetches /robots.txt and reads its directives. robots.txt is a crawl directive, not access control or index removal; this tool does not simulate a specific crawler's policy.
No. If the required evidence is unavailable, the tool returns an unavailable or incomplete state instead of inventing a metric.
Connect the target to a Novaverb workspace to keep evidence, run site-wide analysis, monitor changes, and move findings into an accountable workflow.