What to do with your robots.txt result
A reachable file tells you what it contains. It does not prove that Google indexed your pages or that every crawler can reach the rest of your site.
User-agent: *
Disallow: /private/
Sitemap: https://example.com/sitemap.xmlThis illustrative file asks matching crawlers to avoid /private/ and declares a sitemap. It does not keep private content secure. Use authentication for that.
| Finding | Next check |
|---|---|
| Disallow: / | Check the user-agent group. If it applies to Googlebot, it blocks crawling across that hostname. |
| No sitemap directive | Your sitemap may still exist. Open the sitemap checker and submit the correct URL in Search Console. |
| 404 response | A missing robots.txt does not itself block crawling. Check page-level noindex and access separately. |
| Server error or access challenge | Review hosting or firewall rules and retest. A failed fetch cannot confirm which crawl rules apply. |
Rules belong to specific user-agent groups. A flat list of allow and disallow paths is not a complete decision for an individual Googlebot URL. Use Google's URL Inspection for that page.
Check the declared sitemap, or follow the missing search visibility diagnosis if the page still does not appear. The technical SEO checklist covers the remaining checks.
See Google's robots.txt guidance for crawl controls and indexing limitations.
