Primary related guide or tool
Continue the workflow with this related LLMs.txt Kit resource.
/templates/ai-crawler-robots-txt-examples.htmlAI crawler policy for private docs and staging sites
How to protect private documentation and staging sites without relying on robots.txt as security.
Fast answer
If your goal is to protect private areas properly, start with this framing: robots.txt is public and voluntary, so it is not access control. The useful deliverable is a private-docs protection checklist.
This page is intentionally conservative. It treats crawler files, URL inspection, feeds, and server logs as discovery and measurement aids, not as guaranteed ranking levers.
When to use this playbook
Use it when technical teams with private docs, staging, or preview environments need a concrete next step and a page that can be linked from a hub, a community answer, a README, or a launch checklist. The page should help someone make a decision even if they never buy anything or contact the site owner.
The strongest pages in this topic cluster have three traits: they answer one narrow question, they include a copyable artifact, and they link to the relevant tool or proof page so the reader can act immediately.
Recommended workflow
- Use authentication for private docs.
- Avoid listing private paths in llms.txt.
- Use noindex where crawled pages should not appear.
- Keep staging off public discovery surfaces.
Pre-publish checklist
- authentication enabled.
- staging not linked.
- private URLs excluded.
- robots.txt not treated as security.
Copyable working note
Use this as a starting point in a ticket, README, client note, or launch log. Edit it to match the real site before publishing.
Private docs: auth required
Staging: no public links
Public docs: curated and indexedWhat not to count as proof
Do not count this setup as traffic by itself. A submitted sitemap, an IndexNow receipt, a crawler log hit, or an indexing request can show discovery work, but none of them proves rankings, impressions, clicks, conversions, or AI citations. Organic proof should come from Search Console, analytics, qualified referral evidence, or server logs interpreted for the right purpose.
The main pitfall for this topic is: Publishing sensitive path names in a public robots.txt file.
Related resources
Next supporting resource
Continue the workflow with this related LLMs.txt Kit resource.
/guides/ai-crawler-audit-checklist.htmlAll free tools
Continue the workflow with this related LLMs.txt Kit resource.
/tools/Proof dashboard
Continue the workflow with this related LLMs.txt Kit resource.
/proof.html