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

- Canonical HTML: https://growth.iangoh.com/growth-ideas/same-workspace-301-map-after-help-center-migration/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/8491098-manage-article-redirects-from-another-help-center)
- GrowthDex source hub: [Intercom Help](/sources/intercom-help-intercom-com/)
- Last checked: 2026-05-28
- Rarity: uncommon
- Budget: medium
- Channels: SEO, Support, Website
- Stages: redirects, migration, technical seo, support ops
- Key metric: Intercom uses 301 redirects, auto-creates them during Zendesk imports, and limits redirect targets to the same workspace

## Why this can grow

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.

## 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. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. 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 same-workspace 301 map after help-center migration can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the SEO and Support channel.
3. Use the evidence from intercom.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

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.

## Adjacent tactics in the same lane

- [Unlisted public article preview before search release](/growth-ideas/unlisted-public-article-preview-before-search-release/) - same source, 3 shared channels, 2 shared stages
- [Locale-picked help-center homepage articles](/growth-ideas/locale-picked-help-center-homepage-articles/) - same source, 3 shared channels, 1 shared stage
- [Legacy docs redirect map during help-center migration](/growth-ideas/legacy-docs-redirect-map-during-help-center-migration/) - same source, 3 shared channels, 1 shared stage
- [Cross-domain help-center 301s before docs move](/growth-ideas/cross-domain-help-center-301s-before-docs-move/) - same source, 3 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The help center stops feeling generic when the brand context stays intact](/blog/the-help-center-stops-feeling-generic-when-the-brand-context-stays-intact/) - support-led growth, technical SEO, brand trust

## Advisory

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