How to structure a SaaS knowledge base (with examples)

The most common knowledge base mistake is not bad writing — it is bad structure. Articles get dumped into one long list, customers cannot find anything, and the help center quietly fails at its one job: answering questions before they become tickets. The fix is a predictable category structure and a small set of repeatable article types.

Almost every SaaS knowledge base can start with the same five top-level categories. You can rename them to match your product's vocabulary, but the intent behind each one should stay the same:

• Getting started — onboarding guides that take a new user from signup to first value.
• Account and billing — passwords, team members, invoices, plan changes, cancellations.
• Features — one category (or sub-category) per major feature, explaining what it does and how to use it.
• Troubleshooting — error messages, common failure states, and step-by-step fixes.
• FAQ — short answers to the questions your support inbox sees every week.

The best-performing help articles solve exactly one problem and say so in the title. 'How to connect a custom domain' will be found and read; 'Domains, DNS, and other settings' will not. One problem per page is also what search engines and AI assistants reward — a focused page is easy to match to a focused query.

Use task-based titles that mirror how customers phrase the problem ('How do I…', 'Why is my…'). Put the answer high on the page, then add detail below for readers who need it.

Consistency makes a knowledge base feel trustworthy. A simple template that works for most help articles:

• Title: the task or question in the customer's words.
• First paragraph: the direct answer or outcome in two or three sentences.
• Steps: numbered, one action per step, with screenshots where they help.
• Notes: edge cases, limits, and links to related articles.

Most visitors will not browse your category tree — they will arrive from your help center's search box or from Google. That means every article needs a descriptive title, a clear first paragraph, and headings that match real queries. Publishing on a platform with server-side rendering (so crawlers get full HTML) and clean URLs does the technical half of this for you.

This is the approach LightDocs takes by default: articles are organized into categories, rendered server-side, and published on your own domain so your knowledge base builds search authority for your brand. Start with the five categories above, write ten articles against your most common tickets, and your help center will be useful from day one.