# Cross-domain help-center 301s before docs move

> Before moving a help center to a new host, ship domain-level 301 redirects from the old support domain so rankings and bookmarked answers survive.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/cross-domain-help-center-301s-before-docs-move/
- 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-25
- Rarity: rare
- Budget: low
- Channels: SEO, Website, Support
- Stages: migration, docs, seo, support
- Key metric: HTTP 301 redirects from the old help-center host to the new host

## Why this can grow

Docs migrations often break trust in the dullest possible way: old answers vanish. Cross-domain 301s preserve discovery, backlinks, and customer habits. They make the new help center feel like a continuation instead of a reset.

## 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 HTTP 301 redirects from the old help-center host to the new host before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where cross-domain help-center 301s before docs move can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the SEO and Website 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: HTTP 301 redirects from the old help-center host to the new host.
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 help-center guidance says a custom-domain move needs HTTP 301 redirects at the DNS, CDN, or edge layer because Intercom will not create those cross-domain redirects for you.

## Adjacent tactics in the same lane

- [Legacy docs redirect map during help-center migration](/growth-ideas/legacy-docs-redirect-map-during-help-center-migration/) - same source, 3 shared channels, 3 shared stages
- [Help-center collection link cleanup after domain switch](/growth-ideas/help-center-collection-link-cleanup-after-domain-switch/) - same source, 3 shared channels, 2 shared stages
- [Same-workspace 301 map after help-center migration](/growth-ideas/same-workspace-301-map-after-help-center-migration/) - same source, 3 shared channels, 1 shared stage
- [Unlisted public article preview before search release](/growth-ideas/unlisted-public-article-preview-before-search-release/) - same source, 3 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The switcher usually buys the safer exit](/blog/the-switcher-usually-buys-the-safer-exit/) - switcher intent, seo, product marketing

## Advisory

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