A small Disallow rule can block valuable pages or rendering assets. Review robots.txt as a public crawl-control file, not a security layer.
Symptoms
- Important pages stop being crawled.
- Search Console reports blocked by robots.txt.
- Rendered pages miss CSS, JavaScript or images.
Likely causes
- A broad Disallow rule catches more paths than intended.
- Asset directories are blocked even though pages need them to render.
- The sitemap URL points to the wrong host or protocol.
Fix steps
- Generate a minimal robots.txt and add one rule at a time.
- Remove blocks for public assets required by key pages.
- Use noindex or authentication when you need privacy or deindexing.
Verify the fix
- Open /robots.txt directly.
- Use Search Console URL Inspection on important URLs.
- Check the sitemap URL listed in robots.txt.
FAQ
Does robots.txt hide private pages?
No. It is public and only gives crawl instructions.
Can blocked pages still be indexed?
Yes, URLs can appear in search if discovered elsewhere, often without a useful snippet.
Related tools and guides
Last updated: May 18, 2026