1. Source
Live robots.txt fetch. The result identifies where its evidence came from.
Test and validate robots.txt rules, User-Agent directives, blocked paths and AI bot access policies for search engines and AI crawlers.
Soumettez une URL publique, un domaine ou un mot-clé. Novaverb ne montrera que les preuves que cet outil peut réellement récupérer ou mesurer.
This check proves what a site's robots.txt actually says and which rules apply to which crawler, including conflicting or overly broad Disallow blocks and any declared Sitemap directives. It proves crawl permission, not indexing: a URL that is disallowed here can still appear in search results, and one that is allowed is not thereby crawled.
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.
Utilisez la découverte pour vérifier un problème, puis connectez un espace de travail lorsque vous avez besoin d'historique, de surveillance ou d'analyse à l'échelle du site.
robots.txt indique aux robots conformes quels chemins ils peuvent demander. C'est le premier fichier que la plupart des robots récupèrent, donc une seule ligne incorrecte peut silencieusement empêcher un site entier d'apparaître dans les résultats de recherche - ou laisser des chemins privés être explorés.
Un fichier robots.txt clair réduit l'ambiguïté pour les crawlers de recherche et d'IA. Novaverb peut utiliser ce signal dans le cadre d'un modèle de crawl et de preuves techniques plus large, aux côtés de l'indexabilité, des canonicals et des liens internes.
Submit the domain, or any URL on it; the host is resolved and robots.txt is fetched from the root, which is the only location the specification recognises. A file placed in a subdirectory is not a robots.txt and will be reported as missing, which is the same conclusion every real crawler reaches.
yourdomain.comToute forme d'adresse fonctionne - nous récupérons /robots.txt à la racine de l'hôte pour vous. http ou https, avec ou sans www, un domaine nu ou un chemin complet - nous le normalisons pour vous.https://www.yourdomain.com/anythingMême une URL profonde est correcte ; nous résolvons l'hôte et lisons son robots.txt racine.Expecting a subfolder robots.txt to countrobots.txt n'est respecté qu'à la racine de l'hôte ; une copie dans un sous-dossier est ignorée par les robots d'exploration.The host is resolved from the input and robots.txt is fetched from its root. User-agent, Allow and Disallow groups are parsed per RFC 9309, and the rules that apply to each major crawler are resolved the way that crawler resolves them. Conflicting or overly broad Disallow blocks are flagged, and Sitemap directives are noted.
RFC 9309 has defined the Robots Exclusion Protocol as a published standard since 2022, and this parse follows it rather than folklore, including its precedence rules for Allow against Disallow. Google's own robots.txt documentation is applied where it defines behaviour the RFC leaves to the implementation.
Analyse vos directives Allow / Disallow / user-agent selon la norme formelle robots.txt.
Lisez la spécificationNote où l'interprétation de Googlebot étend la norme de base.
Lisez la spécificationIt fetches your /robots.txt file, reports the HTTP status, and lists crawl rules grouped by user-agent, counting every Allow and Disallow directive plus any declared Sitemap lines so you see exactly what crawlers are told.
Robots.txt is a plain-text file at your domain root that follows the Robots Exclusion Protocol (RFC 9309). It tells cooperating crawlers like Googlebot which paths they may or may not request, grouped by user-agent.
Robots.txt controls crawler access to your paths. A mistaken Disallow can stop search engines from crawling important pages, so verifying the rules prevents accidentally hiding content you actually want discovered and ranked.
No. Robots.txt only requests that crawlers skip a path; it is a crawl directive, not index removal. A disallowed URL can still be indexed from external links. Use a noindex meta tag or removal request instead.
Look for a Disallow: / line under User-agent: *, which blocks every path. Remove or narrow it, then re-check. The tool flags this specific site-wide block so you can catch it fast.
A 200 OK means the file was served and its rules apply. A 404 means no file exists, so crawlers assume full access. Persistent 5xx errors can cause crawlers to pause crawling entirely.
Disallow lists paths crawlers should not request; Allow re-permits a sub-path inside a broader Disallow. The most specific matching rule wins, so Allow can carve exceptions out of a blocked directory.
Yes. A Sitemap: directive with the full URL helps crawlers discover your XML sitemap independently of any submission. The checker reports every Sitemap line it finds so you can confirm it is declared.
No. Robots.txt is a public, voluntary instruction for cooperating crawlers, not access control. Anyone can read it, and it cannot protect private content. Use authentication or server rules to actually restrict access.
It parses and reports your directives as written, but it does not replicate any single crawler's full internal matching policy. Treat the grouped rules and counts as an accurate readout, not a crawler-specific simulation.