One help article per search job
Split support content into one article per customer question so search, linking, and recirculation work on a clear job instead of a blended catch-all page.
Why this can grow a startup
Help centers get muddy when one page tries to answer three different questions. Search ranking gets less precise, related-article suggestions get weaker, and support links are harder to reuse in product or replies. A one-job article is easier to rank, easier to link, and easier to keep current when the product changes.
Company example
Intercom's Help Center search guidance recommends using one article per idea so readers and the search engine can find the right answer more easily.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
Intercom explicitly recommends one article per idea for clearer help-center search retrieval
Source discovered: May 27, 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.
Founder checklist
- Read Intercom Help and identify what is directly supported.
- Choose one channel context: Support, SEO, Documentation.
- Define the test around Intercom explicitly recommends one article per idea for clearer help-center search retrieval.
- 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.