Same-workspace 301 map after help-center migration
Keep a same-workspace 301 map for imported or renamed help-center URLs so old article paths continue carrying traffic and trust after a migration.
Why this can grow a startup
Docs migrations often lose value in the handoff. Intercom's redirect system creates permanent redirects, auto-generates them during Zendesk imports, and lets teams keep several old paths pointed at one destination. Used well, that means a migration can preserve search demand and customer bookmarks instead of treating every URL change like a fresh start.
Company example
Intercom's Manage redirects feature adds 301 redirects, auto-generates them during Zendesk imports, supports multiple old URLs pointing to one article, and blocks cross-workspace redirects.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
Intercom uses 301 redirects, auto-creates them during Zendesk imports, and limits redirect targets to the same workspace
Source discovered: May 28, 2026
When to use it
Use this when SEO, Support, Website is relevant to redirects, migration, technical seo and you can run a bounded test with a medium 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 Intercom uses 301 redirects, auto-creates them during Zendesk imports, and limits redirect targets to the same workspace.
- 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.