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.
Why this can grow a startup
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.
Company example
Intercom lets teams drag and drop homepage sections so Articles can sit above or below Collections.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
Intercom explicitly supports drag-and-drop ordering of homepage Articles and Collections sections
Source discovered: May 28, 2026
When to use it
Use this when Support, UX, Website is relevant to routing, information architecture, self-serve 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, UX, Website.
- Define the test around Intercom explicitly supports drag-and-drop ordering of homepage Articles and Collections sections.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.