How to Structure Your Help Center: The 4 Categories That Work

Almost every help center that works well is built on the same four categories: Getting Started, Billing & Subscription, Troubleshooting, and Profile & Account. Your product might need one or two more, but these four cover the questions nearly every customer asks, and they give people an obvious place to look before they give up and email you.

Structure sounds like the boring part of building a help center. It's actually the part that decides whether the whole thing works. A help center with great articles and confusing navigation fails exactly like one with no articles at all: the customer can't find the answer, so they open a ticket.

Why structure fails (and how people actually search)

Customers arrive at your help center in one of two modes:

1. Searchers type what's wrong into the search bar and click the first sensible result.
2. Browsers scan your categories, pick the one that sounds right, and drill down.

Searchers are served by good article titles, which we cover in the writing chapter. Browsers are served by your categories. A browser who opens a category and finds unrelated articles inside loses trust in the whole help center and stops browsing. That's why category names need to be predictable rather than clever. "Billing" beats "Money matters." Nobody guesses what "Resources" contains.

The four categories, with starter articles

Here's the structure, along with the sample articles we recommend starting each category with. Steal all of it.

1. Getting started

Help users learn the basics of your product and take their first steps. This is your most-visited category and also your best sales asset, since prospects read it to judge how hard your product will be to learn.

Starter articles:

• What is {Your Product}?
• How do I install / log in to {Your Product}?
• {Your Product} glossary

That glossary article earns its place: every product accumulates its own vocabulary, and defining it once saves confusion everywhere else.

2. Billing & subscription

Money questions feel urgent to the person asking. When someone gets charged unexpectedly or wants to cancel, a missing answer turns irritation into a churn risk or an angry email.

Starter articles:

• How do I upgrade my current plan?
• How do I cancel my subscription?
• What payment methods are available?

Write the cancellation article. Companies that hide it don't reduce cancellations, they just add an angry ticket in front of each one.

3. Troubleshooting

Things break, or users think they broke. Either way they arrive here stressed, so this category rewards short, calm, step-shaped articles.

Starter articles:

• How do I fix {common issue}?
• I found a bug, how can I report it?
• Why can't I do {common thing}?

Fill this category from your support inbox. Each troubleshooting ticket you receive is an article title waiting to be written.

4. Profile & account

The quiet workhorse category: settings, notifications, account data. Rarely exciting, constantly visited.

Starter articles:

• How do I change my profile settings?
• How do I delete my account?
• How do I manage email notifications?

Adapting the framework to your product

Four categories is the floor, not a rule. Add a category when both of these are true: you have at least four or five articles that clearly belong together, and the category name is something a customer would recognize instantly. Common additions:

• Integrations, once you connect to other tools
• For developers or API, if you have a technical audience
• Feature guides, one category per major product area, once Getting Started gets crowded

The mistake to avoid is creating a category for every feature on day one. Ten categories with two articles each force people to guess where things live. Three articles in the wrong category is a smaller problem than ten categories that are nearly empty.

Structure inside each article collection

Order matters within a category too. Put the most-asked article first, not the alphabetically first one. Most help center tools, HelpKit included, let you order articles manually. Use the order your customers' journey follows: install before configure, configure before customize.

If a category grows past ten or so articles, split it into subcategories before it turns into a wall of links.

Doing this in Notion

If you build your help center from Notion, the structure maps directly: one database for articles, with properties for category and order. Our Notion knowledge base template ships with the four categories and the starter articles above already in place, so you can duplicate it and start writing instead of designing a system from scratch.

With the skeleton standing, the next job is filling it with articles people actually want to read. That's chapter 3: writing help articles.

Common questions

How many categories should a help center have? Start with the four above. Most products do fine with four to seven. Past that, look for categories you can merge before adding more.

Should I organize by feature or by task? By task, in the customer's words. Customers think "how do I get my logo on this" rather than "Branding module." Feature-based categories work only when your customers already speak in feature names.

Where do FAQs fit into this structure? Spread them into their categories. A standalone FAQ category becomes a junk drawer that competes with your real structure. The question format is fine for article titles; the catch-all category is the problem.