# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/one-help-article-per-search-job/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/56655-optimize-your-help-center-search)
- GrowthDex source hub: [Intercom Help](/sources/intercom-help-intercom-com/)
- Last checked: 2026-05-27
- Rarity: uncommon
- Budget: free
- Channels: Support, SEO, Documentation
- Stages: help center, information architecture, search ux, content design


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where one help article per search job can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and SEO channel.
3. Use the evidence from intercom.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed 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.

## Adjacent tactics in the same lane

- [Collection-only search gate before Help Center launch](/growth-ideas/collection-only-search-gate-before-help-center-launch/) - same source, 3 shared channels, 3 shared stages
- [Help-center search terms in title, description, and body](/growth-ideas/help-center-search-terms-in-title-description-and-body/) - same source, 3 shared channels, 2 shared stages
- [Action-led help article titles and meta descriptions](/growth-ideas/action-led-help-article-titles-and-meta-descriptions/) - same source, 3 shared channels, 2 shared stages
- [High-traffic help articles linking to low-traffic answers](/growth-ideas/high-traffic-help-articles-linking-to-low-traffic-answers/) - same source, 3 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The help-center search starts working when the archive stops guessing](/blog/the-help-center-search-starts-working-when-the-archive-stops-guessing/) - support-led growth, seo, content strategy

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.