Back to GrowthDex
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.

rare tactic
Best-fit channelSEO · Website · Support
Stage + contextmigration · docs · seo · support
BudgetLowbudget tier
Suggested operator signalQualified search visitors who complete the intended next action

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.

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-reported evidence

Source: Intercom Help · Browse Intercom Help tactics

HTTP 301 redirects from the old help-center host to the new host

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 25, 2026

SEOWebsiteSupportmigrationdocsseosupport
GrowthDex operator note

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.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Adapt the tactic to SEO and Website, using evidence from Intercom Help as context—not as a promised result.
  3. Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
  4. 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.
  5. 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.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

Explore the context

Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

Turn isolated search tactics into a crawlable visibility system tied to demand and proof.

Work with Ian

SOURCE HUB

More tactics from Intercom Help

Explore related GrowthDex examples and evidence connected to Intercom Help.

Open Intercom Help source hub