DiagramPreview
Analyse basiqueNo AILocal previewDebuggingExport

Testeur robots.txt

Collez du contenu pour Testeur robots.txt et générez un aperçu local vérifiable pour déboguer configurations, réponses API, fichiers SEO et snippets générés par AI.

Exemples
Robots decisionPrêt
Your preview will appear here.

Continuer avec un outil lié

Envoyez cette prévisualisation vers un workflow proche pour convertir, déboguer ou exporter.

Comment utiliser

  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.

Cas d’usage

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 revue pour Testeur robots.txt

Utilisez Testeur robots.txt pour inspecter visuellement une source avant documentation, note de PR, post-mortem ou transfert. Testeur robots.txt: Prévisualisez et déboguez cette source localement.

Avant export, vérifiez la lisibilité, les relations, les données sensibles et la cohérence après modification.

Limites et dépannage

Si l'aperçu échoue, réduisez l'entrée au plus petit exemple complet, validez la syntaxe puis réajoutez les sections.

Considérez l'aperçu comme une surface de revue, pas comme une source de vérité. Les résultats critiques doivent être validés.

Exemples à tester

  • 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

Maturité de l'outil

Analyse basique

Analyse basique

Cet outil vise l'inspection rapide de structure. Utilisez-le pour relire et déboguer, puis validez les résultats critiques.

Le libellé indique si l'outil convient surtout à l'export stable, au débogage, à l'analyse rapide ou à la génération AI.