# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/wildcard-docs-redirects-that-keep-path-intent/
- Source: [gitbook.com](https://gitbook.com/docs/publishing-documentation/site-redirects)
- GrowthDex source hub: [GitBook Docs: Site redirects](/sources/gitbook-docs-site-redirects-gitbook-com/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: free
- Channels: SEO, Docs, Support
- Stages: redirects, information architecture, search retention, docs migration


## Why this can grow

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.

## 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. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. 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 wildcard docs redirects that keep path intent can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the SEO and Docs channel.
3. Use the evidence from gitbook.com 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

GitBook shows that a source redirect like /docs/* can send /docs/install to /help/install when Replace wildcard with matched text is enabled.

## Adjacent tactics in the same lane

- [Draft redirect review before GitBook cutover](/growth-ideas/draft-redirect-review-before-gitbook-cutover/) - same source, 2 shared channels
- [GitBook custom domain before docs promotion](/growth-ideas/gitbook-custom-domain-before-docs-promotion/) - 3 shared channels, 1 shared stage
- [Explicit answer pages to improve GitBook AI search](/growth-ideas/explicit-answer-pages-to-improve-gitbook-ai-search/) - 3 shared channels
- [One help article per search job](/growth-ideas/one-help-article-per-search-job/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The docs site should answer like one product](/blog/the-docs-site-should-answer-like-one-product/) - technical seo, docs strategy, brand trust

## Advisory

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