# The help center homepage should route the first click > Why collection gates, scan-copy descriptions, top-question ordering, workflow sequencing, and customer card sorts usually matter more than one more docs redesign. - Canonical HTML: https://growth.iangoh.com/blog/the-help-center-homepage-should-route-the-first-click/ - Published: 2026-05-28 - Updated: 2026-05-28T02:40:00Z - Categories: support-led growth, technical SEO, brand trust - Niches: SaaS, AI products, developer tools, customer support software, marketplaces ## On this page - Publishing is not finished until the article has a place - The short line under the heading often does more work than the heading - Order is a product decision - Some collections should behave like guided onboarding - If customers sort the cards differently, believe them ## Start with these related tactics - [Collection-only search gate before Help Center launch](/growth-ideas/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. - [Collection-description scan copy for support routing](/growth-ideas/collection-description-scan-copy-for-support-routing/): Write collection descriptions like routing copy, because a short line of context often decides whether a visitor opens the right support section or starts guessing. - [Highest-volume question first in each help collection](/growth-ideas/highest-volume-question-first-in-each-help-collection/): Put the most asked question at the top of each support collection so the page answers the likeliest job before the visitor has to scan the rest. Most help centers do not lose trust because the colors are wrong. They lose it because the first click feels like a guess. A support surface can look polished and still make the reader hunt. That is usually the moment the ticket gets opened, the bounce happens, or the buyer quietly decides the product will be harder to live with than it claims. ## Publishing is not finished until the article has a place The basic structural move is [collection-only search gate before Help Center launch](/growth-ideas/collection-only-search-gate-before-help-center-launch/). Intercom is direct here: an article has to be part of a collection to be searchable in the Help Center. That sounds operational, but it changes user experience. It belongs in the same family as [docs live only after first published article](/growth-ideas/docs-live-only-after-first-published-article/). Both ideas force the team to stop treating thin, half-routed surfaces as good enough to publish. ## The short line under the heading often does more work than the heading I like [collection-description scan copy for support routing](/growth-ideas/collection-description-scan-copy-for-support-routing/) because it respects how people actually use support homepages. They skim. They do not read the taxonomy like a manual. That also connects to [search-intent collection copy in every help-center language](/growth-ideas/search-intent-collection-copy-in-every-help-center-language/). The collection label and description are not decoration. They are routing copy for humans and, sometimes, search copy too. ## Order is a product decision The cleanest practical win is [highest-volume question first in each help collection](/growth-ideas/highest-volume-question-first-in-each-help-collection/). If one article gets asked for constantly, put it where the visitor sees it first. This pairs naturally with [high-traffic help articles linking to low-traffic answers](/growth-ideas/high-traffic-help-articles-linking-to-low-traffic-answers/). One tactic improves the first choice inside a collection. The other improves the next click after that. ## Some collections should behave like guided onboarding The best activation-oriented tactic in this batch is [workflow-step sequencing inside help collections](/growth-ideas/workflow-step-sequencing-inside-help-collections/). Install before configuration is a small example, but the point is larger: some docs pages are not references. They are paths. That is why it fits beside [role-based quickstarts that skip irrelevant setup](/growth-ideas/role-based-quickstarts-that-skip-irrelevant-setup/) and [sub-5-minute time-to-value onboarding sprint](/growth-ideas/sub-5-minute-time-to-value-onboarding-sprint/). Good support content can carry part of the activation burden when it is sequenced like the work itself. ## If customers sort the cards differently, believe them The humbling move is [customer card sort before Help Center IA lock](/growth-ideas/customer-card-sort-before-help-center-ia-lock/). Teams tend to organize support around product teams, internal vocabulary, or whatever structure happened to be there first. Customers do not care about any of that. A simple card sort is often enough to show that the labels make sense internally but not at the moment of need. This cluster is strongest for SaaS, AI products, developer tools, support software, and marketplaces where users judge product quality partly through the self-serve experience. If I were tightening one this week, I would ask five blunt questions. Does every live article belong to a findable collection. Do collection descriptions tell the reader what job lives there. Is the top article the one people need most. Do workflow collections follow the real step order. Has any customer tested the taxonomy before the team locked it in. ## Related GrowthDex tactics - [Collection-only search gate before Help Center launch](/growth-ideas/collection-only-search-gate-before-help-center-launch/) - Support, SEO, Documentation - [Collection-description scan copy for support routing](/growth-ideas/collection-description-scan-copy-for-support-routing/) - Support, Brand, Documentation - [Highest-volume question first in each help collection](/growth-ideas/highest-volume-question-first-in-each-help-collection/) - Support, Documentation, SEO - [Workflow-step sequencing inside help collections](/growth-ideas/workflow-step-sequencing-inside-help-collections/) - Support, Onboarding, Documentation - [Customer card sort before Help Center IA lock](/growth-ideas/customer-card-sort-before-help-center-ia-lock/) - Support, Research, Documentation ## Essay chronology - [Newer essay: 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 - [Older essay: The help center search page is a product surface](/blog/the-help-center-search-page-is-a-product-surface/) - support-led growth, technical SEO, brand trust ## Keep reading - [The answer should interrupt the ticket before it opens](/blog/the-answer-should-interrupt-the-ticket-before-it-opens/) - support-led growth, technical SEO, brand trust - [The docs page should know when to finish the job and when to hand off](/blog/the-docs-page-should-know-when-to-finish-the-job-and-when-to-hand-off/) - support-led growth, brand trust, technical SEO - [The help center stops feeling generic when the brand context stays intact](/blog/the-help-center-stops-feeling-generic-when-the-brand-context-stays-intact/) - support-led growth, technical SEO, brand trust ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Intercom Help: Set up your Help Center](https://www.intercom.com/help/en/articles/1970126-set-up-your-help-center) · [GrowthDex source hub](/sources/intercom-help-set-up-your-help-center-intercom-com/) - [Intercom Help: Optimize your Help Center article order](https://www.intercom.com/help/en/articles/56648-optimize-your-help-center-article-order) · [GrowthDex source hub](/sources/intercom-help-optimize-your-help-center-article-order-intercom-com/) ## Editing notes - Kept the essay on one plain claim about routing the first support click instead of drifting into generic docs strategy. - Used concrete objects like collections, descriptions, article order, workflows, and card sorts so the piece stays physical. - Cut broad customer-support platitudes and let the Intercom mechanics carry the proof. - Ended with blunt review questions instead of a padded conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.