Preview docs noindex before cutover
Put staging or migration docs behind a site-wide `noindex, nofollow` rule until the real cutover is ready.
Why this can grow a startup
Preview docs are useful for launches and migrations, but they become a search problem if crawlers discover them before the real help center is ready. A staging host can start competing with the production docs, leaking authority across duplicate pages and sending users to a half-finished surface. Docusaurus exposes a site-wide `noIndex` switch for exactly this reason. The move is simple, but it keeps temporary environments temporary. That matters during docs moves, pricing rewrites, API version rollouts, and any release where the team needs outside review without inviting search engines to treat the preview as canonical.
Company example
Docusaurus says `noIndex: true` adds a `meta name="robots" content="noindex, nofollow"` tag to every page so search engines avoid indexing the site.
Source and metric
Source: Docusaurus Docs: docusaurus.config.js
One `noIndex: true` setting applies `noindex, nofollow` to every page on the site.
Source discovered: May 29, 2026
When to use it
Use this when Documentation, SEO, Operations is relevant to technical seo, staging hygiene, migration and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Docusaurus Docs: docusaurus.config.js and identify what is directly supported.
- Choose one channel context: Documentation, SEO, Operations.
- Define the test around One `noIndex: true` setting applies `noindex, nofollow` to every page on the site..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.