Growth idea action plan
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.
Why this can grow a startup
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.
Key metric to watch
HTTP 301 redirects from the old help-center host to the new host
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
- Define one narrow startup segment where cross-domain help-center 301s before docs move can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the SEO and Website channel.
- Use the evidence from intercom.com to set the first version of the message, format, and audience.
- 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.
- 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.
Source: Intercom Help (intercom.com)
GrowthDex source hub: Intercom Help
Last checked: 2026-05-25
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Legacy docs redirect map during help-center migration same source · 3 shared channels · 3 shared stages
- Help-center collection link cleanup after domain switch same source · 3 shared channels · 2 shared stages
- Same-workspace 301 map after help-center migration same source · 3 shared channels · 1 shared stage
- Unlisted public article preview before search release same source · 3 shared channels
Related GrowthDex essays
- The switcher usually buys the safer exit switcher intent, seo, product marketing
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory