# Preview docs noindex before cutover

> Put staging or migration docs behind a site-wide `noindex, nofollow` rule until the real cutover is ready.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/preview-docs-noindex-before-cutover/
- Source: [docusaurus.io](https://docusaurus.io/docs/api/docusaurus-config)
- GrowthDex source hub: [Docusaurus Docs: docusaurus.config.js](/sources/docusaurus-docs-docusaurus-config-js-docusaurus-io/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: free
- Channels: Documentation, SEO, Operations
- Stages: technical seo, staging hygiene, migration, canonical control


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where preview docs noindex before cutover can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Documentation and SEO channel.
3. Use the evidence from docusaurus.io to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Docusaurus says `noIndex: true` adds a `meta name="robots" content="noindex, nofollow"` tag to every page so search engines avoid indexing the site.

## Adjacent tactics in the same lane

- [Fail docs build on broken links before release](/growth-ideas/fail-docs-build-on-broken-links-before-release/) - same source, 2 shared channels, 1 shared stage
- [Regex redirect families before docs group migration](/growth-ideas/regex-redirect-families-before-docs-group-migration/) - 3 shared channels, 2 shared stages
- [ReadMe subdomain redirect after custom-domain cutover](/growth-ideas/readme-subdomain-redirect-after-custom-domain-cutover/) - 2 shared channels, 2 shared stages
- [Docs linter runs before save, not after publish](/growth-ideas/docs-linter-runs-before-save-not-after-publish/) - 3 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The docs route should feel boring even when the product is moving](/blog/the-docs-route-should-feel-boring-even-when-the-product-is-moving/) - docs strategy, technical seo, support-led growth

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.