Wildcard docs redirects that keep path intent
Use wildcard redirects that pass the matched slug through when a docs section moves, instead of dumping every old page onto one generic landing page.
Why this can grow a startup
A flat redirect to the new docs homepage technically removes the 404, but it still forces the user to start over and makes old external links feel broken. GitBook supports wildcard redirects with matched-text replacement, so a whole section can move from /docs/* to /help/* while preserving the rest of the path. That keeps the old search result, bookmarked article, or partner link much closer to the answer the visitor expected.
Company example
GitBook shows that a source redirect like /docs/* can send /docs/install to /help/install when Replace wildcard with matched text is enabled.
Source and metric
Source: GitBook Docs: Site redirects
With Replace wildcard with matched text on, /docs/* can redirect /docs/install to /help/install instead of sending every request to one fixed destination.
Source discovered: May 29, 2026
When to use it
Use this when SEO, Docs, Support is relevant to redirects, information architecture, search retention 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 GitBook Docs: Site redirects and identify what is directly supported.
- Choose one channel context: SEO, Docs, Support.
- Define the test around With Replace wildcard with matched text on, /docs/* can redirect /docs/install to /help/install instead of sending every request to one fixed destination..
- 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.