1. Source
Live robots.txt and /sitemap.xml fetch. The result identifies where its evidence came from.
Check robots.txt and the default sitemap.xml for free. Inspect HTTP status, sitemap directives, file size, and the URL count in the fetched sitemap.
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 and /sitemap.xml fetch. The result identifies where its evidence came from.
The checker fetches /robots.txt and /sitemap.xml and reads Sitemap directives. It does not recursively audit every child sitemap or prove Google indexing.
Use the finding to verify a problem, then connect a workspace when you need history, monitoring, or site-wide analysis.
Robots.txt and XML sitemaps work together to guide search engine crawlers. Robots.txt is a gatekeeper that tells bots which directories they are forbidden from crawling (like admin consoles or cart pages). Sitemaps act as a roadmap, declaring all indexable, high-quality URLs you want search engines to discover and index.
An incorrectly configured robots.txt file can accidentally block search engines from crawling your entire site, wiping out your organic traffic overnight. Always validate changes before uploading.
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 and /sitemap.xml fetch. The checker fetches /robots.txt and /sitemap.xml and reads Sitemap directives. It does not recursively audit every child sitemap or prove Google indexing.
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.