Legacy docs redirect map during help-center migration
When migrating a help center or docs corpus, ship permanent redirects from every legacy URL so search traffic, backlinks, and in-product links survive the move.
Why this can grow a startup
Docs migrations usually lose trust in quiet ways: old support links break, bookmarked answers die, and search equity resets just when buyers are comparing vendors. A redirect map keeps the old URLs useful, preserves link authority, and makes the migration feel stable instead of risky.
Source-backed example
Intercom's Zendesk article migration creates permanent redirects from previous Zendesk article and collection URLs to the new Intercom articles so existing links keep working and SEO value is preserved.
Source-reported evidence
Source: Intercom Help · Browse Intercom Help tactics
Permanent HTTP 301 redirects for migrated article and collection URLs
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 25, 2026
When to use it
Use this when SEO, Website, Support is relevant to migration, docs, seo 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to SEO and Website, using evidence from Intercom Help as context—not as a promised result.
- Record a baseline for: Share of the target cohort repeating the core action within the chosen period. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.
SOURCE HUB
More tactics from Intercom Help
Explore related GrowthDex examples and evidence connected to Intercom Help.
Open Intercom Help source hub