Help center noindex during duplicate-content phase
Turn off help-center indexing when the same answers need to live elsewhere, so support content can still work in Messenger without splitting search authority.
Why this can grow a startup
A support article can be useful before it should be crawlable. Teams often need the answer inside Messenger, inside a product assistant, or mirrored on a more canonical docs host before they want Google to treat the help center as the primary search surface. Intercom gives teams a clean switch for that situation. The point is not to hide content forever. It is to avoid letting duplicate support pages compete with the site that is supposed to rank.
Company example
Intercom says teams using a custom Help Center domain can disable the setting that allows the Help Center to appear in search results, while still sharing article content in Messenger or hosting it elsewhere.
Source and metric
Source: Intercom Help: Prevent search engines indexing your Help Center
One privacy toggle removes Help Center articles from search results on a custom domain.
When to use it
Use this when SEO, Support, AI Search is relevant to duplicate content, crawl control, messenger 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: Prevent search engines indexing your Help Center and identify what is directly supported.
- Choose one channel context: SEO, Support, AI Search.
- Define the test around One privacy toggle removes Help Center articles from search results on a custom domain..
- 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.