# Help-center homepage section order by job

> Reorder articles and collections on the help-center homepage around the first job the visitor needs done, not the internal information architecture.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/help-center-homepage-section-order-by-job/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/56644-customize-your-help-center)
- GrowthDex source hub: [Intercom Help](/sources/intercom-help-intercom-com/)
- Last checked: 2026-05-28
- Rarity: uncommon
- Budget: free
- Channels: Support, UX, Website
- Stages: routing, information architecture, self-serve, brand trust


## Why this can grow

The first screen of a help center is a routing surface, not a sitemap. If the homepage always leads with collections when the fastest answer lives in a hand-picked article block, the layout is doing politics, not support. Reordering the sections around the most common job reduces the number of guesses before the reader hits a useful page. It is one of the cheapest ways to make a support surface feel more obvious.

## 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. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. 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 help-center homepage section order by job can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and UX 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 lets teams drag and drop homepage sections so Articles can sit above or below Collections.

## Adjacent tactics in the same lane

- [Translated collection gate before multilingual help-center launch](/growth-ideas/translated-collection-gate-before-multilingual-help-center-launch/) - same source, 2 shared channels, 2 shared stages
- [Unlisted public article preview before search release](/growth-ideas/unlisted-public-article-preview-before-search-release/) - same source, 2 shared channels, 1 shared stage
- [Single collection home for each public help article](/growth-ideas/single-collection-home-for-each-public-help-article/) - same source, 2 shared channels, 1 shared stage
- [Private help-article login redirect before publish](/growth-ideas/private-help-article-login-redirect-before-publish/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The help center should know who it is for](/blog/the-help-center-should-know-who-it-is-for/) - support-led growth, brand trust, technical SEO

## Advisory

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