# The docs route should feel boring even when the product is moving > Why broken-link build failures, preview noindex rules, hidden unreleased docs, file-based links, and custom 404 recovery pages make documentation easier to trust. - Canonical HTML: https://growth.iangoh.com/blog/the-docs-route-should-feel-boring-even-when-the-product-is-moving/ - Published: 2026-05-29 - Updated: 2026-05-29T14:55:00Z - Categories: docs strategy, technical seo, support-led growth - Niches: SaaS, developer tools, AI products, API platforms, B2B software ## On this page - Broken links should fail in CI, not in front of users - Preview docs should stay previews - The internal link graph should survive ordinary editing - The 404 page is still part of the product ## Start with these related tactics - [Fail docs build on broken links before release](/growth-ideas/fail-docs-build-on-broken-links-before-release/): Treat broken documentation links as a release blocker so product, support, and search never inherit avoidable dead ends. - [Preview docs noindex before cutover](/growth-ideas/preview-docs-noindex-before-cutover/): Put staging or migration docs behind a site-wide `noindex, nofollow` rule until the real cutover is ready. - [Hide unreleased docs until the version is real](/growth-ideas/hide-unreleased-docs-until-the-version-is-real/): Keep the work-in-progress docs version out of the public site when the release is not ready for customer traffic yet. A docs move often fails long before anyone calls it a failure. Nobody announces that the help center now feels half-moved. The feeling shows up in smaller ways. A support reply lands on the wrong host. A search result opens a preview copy. A changelog link finds a page that still exists, but not where the reader expected. The buyer does not file a bug about that. They just trust the product a little less. The useful goal is not a dramatic docs redesign. It is something quieter. The route to the answer should feel boring even while the product, release train, and information architecture are moving underneath it. ## Broken links should fail in CI, not in front of users [Fail docs build on broken links before release](/growth-ideas/fail-docs-build-on-broken-links-before-release/) is the kind of rule teams postpone because it feels strict right up until the week they need it. The point is simple. If onboarding, changelog, and support links are part of the product, a broken route is a product regression. Docusaurus treating broken links as a production-build failure is useful because it makes the repair happen while the editor still remembers what changed. It pairs naturally with [draft redirect review before GitBook cutover](/growth-ideas/draft-redirect-review-before-gitbook-cutover/). One catches the route that vanished. The other catches the route map that was never properly finished. ## Preview docs should stay previews [Preview docs noindex before cutover](/growth-ideas/preview-docs-noindex-before-cutover/) exists because staging hosts have a bad habit of becoming semi-public by accident. Someone shares the preview with partners, search finds it, and now the company has two docs surfaces competing to explain the same product. A site-wide noindex rule is boring, but that is exactly why it works. It keeps the rehearsal from becoming the performance. The same restraint shows up in [hide unreleased docs until the version is real](/growth-ideas/hide-unreleased-docs-until-the-version-is-real/). A work-in-progress page should not outrun the feature it describes. Otherwise the docs start making promises the product team has not actually signed yet. ## The internal link graph should survive ordinary editing A lot of docs debt comes from basic maintenance, not from big migrations. A file gets moved. A slug gets cleaned up. Somebody changes a trailing-slash setting and a few older links quietly rot. [Markdown file links for version-safe docs navigation](/growth-ideas/markdown-file-links-for-version-safe-docs-navigation/) is worth stealing because it makes the safer choice the default one. Editors can reorganize the library without treating every rename like a search-and-replace fire drill. This also belongs beside [main-version redirect to clean docs URLs](/growth-ideas/main-version-redirect-to-clean-docs-urls/). One tactic protects the links inside the library. The other keeps the public route simpler for everyone arriving from outside it. ## The 404 page is still part of the product Teams act like a 404 page sits outside the main experience. It does not. It usually appears when the user is already in a hurry. [Custom docs 404 page with task-led redirects](/growth-ideas/custom-docs-404-page-with-task-led-redirects/) matters because the broken link moment is still a support and trust moment. A branded rescue page plus real redirect rules can recover old campaign links, stale bookmarks, and copied support macros before the reader decides the help center is unreliable. If the team has already done [customer-facing docs on a brand subdomain](/growth-ideas/customer-facing-docs-on-brand-subdomain/), this is the next standard to hold. The owned surface should still feel owned when something goes slightly wrong. For SaaS, developer tools, AI products, API platforms, and B2B software, the lesson is plain. Docs trust is built in route decisions as much as in prose quality. The reader should not need to know how much changed behind the scenes. If you want help making docs, search, and support surfaces feel tighter under real growth pressure, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Fail docs build on broken links before release](/growth-ideas/fail-docs-build-on-broken-links-before-release/) - Documentation, SEO, Product - [Preview docs noindex before cutover](/growth-ideas/preview-docs-noindex-before-cutover/) - Documentation, SEO, Operations - [Hide unreleased docs until the version is real](/growth-ideas/hide-unreleased-docs-until-the-version-is-real/) - Documentation, Product, Support - [Markdown file links for version-safe docs navigation](/growth-ideas/markdown-file-links-for-version-safe-docs-navigation/) - Documentation, SEO, Developer Experience - [Custom docs 404 page with task-led redirects](/growth-ideas/custom-docs-404-page-with-task-led-redirects/) - Documentation, SEO, Brand ## Essay chronology - [Newer essay: The launch thread should look alive before it looks popular](/blog/the-launch-thread-should-look-alive-before-it-looks-popular/) - launches, community-led growth, brand trust - [Older essay: The help article should know what comes next](/blog/the-help-article-should-know-what-comes-next/) - SEO, support-led growth, brand trust ## Keep reading - [The docs site should answer like one product](/blog/the-docs-site-should-answer-like-one-product/) - technical seo, docs strategy, brand trust - [The changelog should prove the product keeps moving](/blog/the-changelog-should-prove-the-product-keeps-moving/) - release communication, brand trust, technical seo - [The customer-facing answer should keep the context attached](/blog/the-customer-facing-answer-should-keep-the-context-attached/) - support-led growth, brand trust, customer success ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Docusaurus Docs: docusaurus.config.js](https://docusaurus.io/docs/api/docusaurus-config) · [GrowthDex source hub](/sources/docusaurus-docs-docusaurus-config-js-docusaurus-io/) - [Docusaurus Docs: Versioning](https://docusaurus.io/docs/next/versioning) · [GrowthDex source hub](/sources/docusaurus-docs-versioning-docusaurus-io/) - [Docusaurus Docs: Markdown links](https://docusaurus.io/docs/markdown-features/links) · [GrowthDex source hub](/sources/docusaurus-docs-markdown-links-docusaurus-io/) - [ReadMe Docs: Error Pages and Redirects](https://docs.readme.com/main/docs/error-pages) · [GrowthDex source hub](/sources/readme-docs-error-pages-and-redirects-docs-readme-com/) - [ReadMe Docs: Redirect Scenarios](https://docs.readme.com/main/docs/redirect-scenarios) · [GrowthDex source hub](/sources/readme-docs-redirect-scenarios-docs-readme-com/) ## Editing notes - Kept the essay on one plain claim: route hygiene, not a fresh redesign, is what makes docs feel trustworthy during change. - Used ordinary scenes like a support macro, a shared preview host, and a stale changelog link instead of abstract documentation strategy language. - Let the source mechanics carry the proof and linked them to moments operators actually recognize during launches and migrations. - Ended with the operating lesson and advisory CTA instead of a generic docs-quality conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.