# Two-level help-center navigation cap

> Limit public help-center navigation to two layers so the archive stays shallow enough to scan, maintain, and crawl.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/two-level-help-center-navigation-cap/
- Source: [productlane.com](https://productlane.com/docs/docs/support-docs)
- GrowthDex source hub: [Productlane Docs](/sources/productlane-docs-productlane-com/)
- Last checked: 2026-05-27
- Rarity: uncommon
- Budget: free
- Channels: Documentation, SEO, UX
- Stages: information architecture, help center, internal linking, readability


## Why this can grow

Most docs libraries get weaker as the structure gets deeper. Two layers force the team to organize around plain customer jobs instead of an internal org chart. The result is faster scanning for readers, cleaner internal linking, and fewer orphan pages that only exist because the hierarchy became too complicated to prune.

## 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 two-level help-center navigation cap can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Documentation and SEO channel.
3. Use the evidence from productlane.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

Productlane supports only two navigation layers in its docs system to keep the content simpler for end users.

## Adjacent tactics in the same lane

- [Docs live only after first published article](/growth-ideas/docs-live-only-after-first-published-article/) - same source, 2 shared channels, 1 shared stage
- [Help-center importer before portal rewrite](/growth-ideas/help-center-importer-before-portal-rewrite/) - same source, 1 shared channel, 1 shared stage
- [Bulk publish imported release history after review](/growth-ideas/bulk-publish-imported-release-history-after-review/) - same source, 1 shared channel
- [AI chat weekly doc-gap report](/growth-ideas/ai-chat-weekly-doc-gap-report/) - same source, 1 shared channel

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The support doc starts working when the product can point to it](/blog/the-support-doc-starts-working-when-the-product-can-point-to-it/) - support-led growth, documentation, seo

## Advisory

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