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.
Company 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 and metric
Source: Intercom Help · Browse Intercom Help tactics
HTTP 301 redirects from the old help-center host to the new host
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 low 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.
Founder checklist
- Read Intercom Help and identify what is directly supported.
- Choose one channel context: SEO, Website, Support.
- Define the test around HTTP 301 redirects from the old help-center host to the new host.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.