Collection-only search gate before Help Center launch
Do not call a help article live until it sits inside the right collection, because orphaned articles are harder to find and cannot be searched in the Help Center.
Why this can grow a startup
A help center usually fails on the first click, not the fifth. When articles sit outside the collection structure, the user loses the category cues that tell them where to look next, and internal search loses access to the page entirely. Treating collection placement as part of publishing keeps the support surface browseable, searchable, and easier to maintain as the archive grows.
Source-backed example
Intercom says articles must be added to a collection to appear in the Help Center and to be searchable there.
Source-reported evidence
Source: Intercom Help · Browse Intercom Help tactics
Intercom explicitly states that articles must be part of a collection to be searchable in the Help Center.
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 28, 2026
When to use it
Use this when Support, SEO, Documentation is relevant to help center, information architecture, search ux 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Support and SEO, 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