Structure is the product
A help center’s structure determines whether it works. The content can be excellent and still be useless if customers can’t find it in 20 seconds or less.
Organize by customer jobs, not product categories
The most common structural mistake: organizing around product architecture rather than customer jobs.
Product-organized: Account Settings / Billing / Integrations / Advanced Features. Reflects how the product was built, not how customers think.
Job-organized: Get Started / Manage Your Account / Fix an Issue / Connect to Other Tools. These are the reasons customers come.
Practical test: what words do customers use to describe their problem? Those words should appear in navigation. Product team vocabulary often doesn’t match customer vocabulary.
Article types
How-to: Step-by-step for a single task. Scope to one task; if it requires more than 12 steps, split it.
Conceptual: Explains how something works before customers try to use it. Keep short — customers read these as pre-reading.
Troubleshooting: Structured as “if you see X, do Y.” Present symptoms first, not causes.
Reference: Tables and lists that customers consult rather than read. Scannable formatting required.
Search optimization
Article titles written for browsing fail search. Customers type how they describe problems: “payment failed,” “can’t log in,” “how do I add another user.”
Write titles as questions or task phrases that match these searches. Test your search with the 10 most common ticket subjects — if the right article appears in the first 3 results, your search is working. AI-first support platforms like AItocha CX integrates directly with help center content to surface relevant articles during live interactions, reducing the gap between self-service and agent-assisted support.