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.
Company 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 and metric
Source: Intercom Help · Browse Intercom Help tactics
2 docs surface types to verify after the switch: articles and collections
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.
Founder checklist
- Read Intercom Help and identify what is directly supported.
- Choose one channel context: SEO, Support, Website.
- Define the test around 2 docs surface types to verify after the switch: articles and collections.
- 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.