DiagramPreview
Analizador básicoNo AILocal previewDebuggingExport

Probador robots.txt

Pega contenido para Probador robots.txt y genera una vista local revisable para depurar configuración, respuestas de API, archivos SEO y fragmentos generados con AI.

Ejemplos
Robots decisionListo
Your preview will appear here.

Continúa con una herramienta relacionada

Lleva esta vista previa a un flujo cercano para convertir, depurar o exportar.

Cómo usar

  1. 1Put the target URL on the first line, then add --- and the robots.txt content.
  2. 2Check whether the URL is allowed or disallowed for the relevant user-agent.
  3. 3Review broad Disallow rules such as /, /api, /en, or wildcard paths before publishing.
  4. 4Confirm production behavior with Search Console or the crawler tools you rely on.

Casos de uso

robots.txt QATechnical SEO reviewIndexing issue debuggingAI robots snippet validationLaunch checklist

FAQ

What robots.txt mistake is most dangerous?

A broad Disallow such as / or a locale prefix can block important pages from crawling even when the sitemap lists them.

Does robots.txt remove indexed pages?

Not directly. It controls crawling. Use noindex or removal tools when you need deindexing behavior.

Why test a single URL?

A specific URL test makes broad rules and wildcard behavior easier to reason about than reading the file abstractly.

robots.txt Tester checks Allow and Disallow rules for a target URL so technical SEO changes can be reviewed before deployment.

It is useful when AI, CMS settings, or manual edits produce robots rules that look simple but accidentally block tool pages, docs, assets, or localized routes.

Use it together with sitemap and Open Graph preview checks before submitting important pages for indexing.

Demo: make sure tool pages are crawlable

Before launching a tool site, test representative URLs from each section. A single broad rule can block pages even when sitemap.xml is correct.

  • Test home, tool, blog, and asset URLs separately.
  • Avoid blocking locale prefixes such as /en or /zh-CN by accident.
  • Disallow /api/ without blocking documentation paths such as /api-error-flow-diagram.
https://diagrampreview.com/en/mermaid-preview
---
User-agent: *
Allow: /
Disallow: /api/
Sitemap: https://diagrampreview.com/sitemap.xml

SEO release checklist: test robots rules with real URLs

robots.txt should be reviewed with concrete URLs, not only by reading the file. Locale prefixes, API-looking slugs, and static asset paths are easy to block accidentally on a tool site.

  • Test one page from each major directory before submitting a sitemap.
  • Keep /api/ blocked if needed, but verify similar public slugs are not matched by mistake.
  • Pair robots checks with canonical, hreflang, and sitemap checks for launch review.
User-agent: *
Allow: /
Disallow: /api/
Sitemap: https://diagrampreview.com/sitemap.xml

Checklist de revisión para Probador robots.txt

Usa Probador robots.txt para inspeccionar visualmente contenido fuente antes de publicar documentación, notas de PR, incidentes o handoffs. Probador robots.txt: Previsualiza y depura esta fuente localmente.

Antes de exportar, revisa legibilidad, relaciones, datos sensibles y si la vista sigue teniendo sentido tras editar la entrada.

Límites y solución de problemas

Si la vista falla, reduce la entrada al ejemplo completo más pequeño, valida la sintaxis y agrega secciones gradualmente.

Trata la vista como superficie de revisión, no como fuente de verdad. Los resultados críticos requieren validación humana.

Entradas de ejemplo

  • Blog allowed: URL: https://example.com/blog/har-guide --- User-agent: * Disallow: /admin/ Allow: /blog/ Sitemap: https://example.com/sitemap.xml
  • Private blocked: URL: https://example.com/private/report --- User-agent: * Disallow: /private/ Allow: /private/public/
  • Sitemap rule: URL: /tools/jsonpath-tester --- User-agent: * Disallow: /api/ Allow: /tools/ Sitemap: https://example.com/sitemap.xml

Madurez de la herramienta

Analizador básico

Analizador básico

Esta herramienta se centra en inspección rápida de estructura. Úsala para revisar y depurar, y valida lo crítico antes de producción.

La etiqueta indica si la herramienta sirve mejor para exportar, depurar, analizar rápido o generar con AI.