Single indexed help center during knowledge sync
When syncing one public help center into another system, keep only one version indexable so the migration does not create duplicate content.
Why this can grow a startup
A synced knowledge base can quietly produce two copies of the same answer. That confuses crawlers and weakens trust. Keeping one source of truth indexable protects rankings while still letting the second system power in-product search, AI answers, or support workflows.
Company example
Intercom's Zendesk sync documentation says Intercom prevents search engines from indexing the synced Intercom Help Center so Zendesk remains the primary searchable version.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
Source discovered: May 25, 2026
When to use it
Use this when SEO, Support, AI Search is relevant to knowledge base, duplicate content, crawlability and you can run a bounded test with a free 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, AI Search.
- Define the test around one observable customer behavior.
- 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.