# Promoted help articles for homepage first-click routing

> Pin the few articles that answer the highest-volume problems so the first click from the homepage lands on the page most likely to stop a ticket.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/promoted-help-articles-for-homepage-first-click-routing/
- Source: [support.zendesk.com](https://support.zendesk.com/hc/en-us/articles/4408822265754-Promoting-an-article-to-the-top-of-the-section)
- GrowthDex source hub: [Zendesk Help: Promoting an article to the top of the section](/sources/zendesk-help-promoting-an-article-to-the-top-of-the-section-support-zend/)
- Last checked: 2026-05-29
- Rarity: uncommon
- Budget: free
- Channels: Support, Documentation, SEO
- Stages: homepage routing, ticket deflection, docs ops, support ux


## Why this can grow

Most help centers do not fail because search is unavailable. They fail because the first visible choices are too generic. Zendesk's promoted-article mechanic is useful because it overrides the normal sort order and can also place the article on the homepage, depending on the theme. That gives the team a blunt routing lever for migrations, incidents, pricing questions, and setup tasks that keep showing up. When the right article is visibly first, fewer users are forced to guess their way into the archive.

## 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 promoted help articles for homepage first-click routing can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Documentation channel.
3. Use the evidence from support.zendesk.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

Zendesk lets teams promote an article so it stays at the top of its section regardless of sort order, and notes that promoted articles might also appear by default on the home page.

## Adjacent tactics in the same lane

- [Fail docs build on broken links before release](/growth-ideas/fail-docs-build-on-broken-links-before-release/) - 2 shared channels, 2 shared stages
- [Frontload the answer inside the first 10,000 characters](/growth-ideas/frontload-answer-inside-first-10000-characters/) - 3 shared channels
- [Help-center search terms in title, description, and body](/growth-ideas/help-center-search-terms-in-title-description-and-body/) - 3 shared channels
- [High-traffic help articles linking to low-traffic answers](/growth-ideas/high-traffic-help-articles-linking-to-low-traffic-answers/) - 3 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The help center should stay private until it can carry the work](/blog/the-help-center-should-stay-private-until-it-can-carry-the-work/) - support-led growth, documentation, brand trust

## Advisory

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