Same-workspace 301 map after help-center migration
Keep a same-workspace 301 map for imported or renamed help-center URLs so old article paths continue carrying traffic and trust after a migration.
Why this can grow a startup
Docs migrations often lose value in the handoff. Intercom's redirect system creates permanent redirects, auto-generates them during Zendesk imports, and lets teams keep several old paths pointed at one destination. Used well, that means a migration can preserve search demand and customer bookmarks instead of treating every URL change like a fresh start.
Source-backed example
Intercom's Manage redirects feature adds 301 redirects, auto-generates them during Zendesk imports, supports multiple old URLs pointing to one article, and blocks cross-workspace redirects.
Source-reported evidence
Source: Intercom Help · Browse Intercom Help tactics
Intercom uses 301 redirects, auto-creates them during Zendesk imports, and limits redirect targets to the same workspace
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 28, 2026
When to use it
Use this when SEO, Support, Website is relevant to redirects, migration, technical seo and you can run a bounded test with a medium 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 Support, using evidence from Intercom Help as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. 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