Help-center collection link cleanup after domain switch
After a help-center domain switch, audit collection and index pages separately instead of assuming the article redirects covered the whole docs surface.
Why this can grow a startup
Most teams verify one article, see a redirect, and call the migration complete. But collection and category pages often hold the real internal-link graph for search and support navigation. If those pages still live on the old host or split discovery, the new help center feels half-moved to both crawlers and customers.
Source-backed example
Intercom's custom-domain troubleshooting notes that article links redirect automatically after setup, while collection page links may still load under the default domain when accessed directly.
Source-reported evidence
Source: Intercom Help · Browse Intercom Help tactics
2 docs surface types to verify after the switch: articles and collections
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
When to use it
Use this when SEO, Support, Website is relevant to crawlability, docs, migration 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
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to SEO and Support, using evidence from Intercom Help as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
- 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.
- 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.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.
SOURCE HUB
More tactics from Intercom Help
Explore related GrowthDex examples and evidence connected to Intercom Help.
Open Intercom Help source hub