1. Fuente
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.
Envía una URL pública, dominio o palabra clave. Novaverb mostrará solo la evidencia que esta herramienta puede realmente recuperar o medir.
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.
Usa el hallazgo para verificar un problema, luego conecta un espacio de trabajo cuando necesites historial, monitoreo o análisis a nivel de sitio.
robots.txt indica a los rastreadores cumplidores qué rutas pueden solicitar. Es el primer archivo que la mayoría de los rastreadores obtienen, por lo que una línea incorrecta puede mantener silenciosamente todo un sitio fuera de la búsqueda - o permitir que se rastreen rutas privadas.
Un robots.txt claro reduce la ambigüedad para los rastreadores de búsqueda y de IA. Novaverb puede usar esta señal como parte de un modelo más amplio de evidencia de rastreo y técnica, junto con indexabilidad, canónicos y enlaces internos.
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.comCualquier forma de dirección funciona - obtenemos /robots.txt en la raíz del host por ti. http o https, con o sin www, un dominio desnudo o una ruta completa - lo normalizamos por ti.https://www.yourdomain.com/anythingIncluso una URL profunda está bien; resolvemos al host y leemos su robots.txt raíz.Expecting a subfolder robots.txt to countrobots.txt solo se respeta en la raíz del host; una copia dentro de una subcarpeta es ignorada por los rastreadores.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.
Analiza tus directivas Allow / Disallow / user-agent según el estándar formal de robots.txt.
Lee la especificaciónNotas dónde la interpretación de Googlebot extiende el estándar base.
Lee la especificaciónIt 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.