HubSpot Help Center

The HubSpot help center is the public face of your support content: articles, search, and a route to a human when the article doesn't land.

What the HubSpot help center is, and isn't

The help center is the customer-facing site where your published support content lives. Someone searches, finds an article, and either solves their problem or asks you.

It gets confused with two neighbours, so let us separate them properly.

The [knowledge base](/blog/hubspot-knowledge-base/) is the authoring side: the articles, categories and drafts you manage inside HubSpot.
The help center is the published, browsable site those articles appear on.
The [customer portal](/blog/hubspot-customer-portal/) is the logged-in area where a customer sees their own tickets and their status.

In practice they're often presented as one destination to the customer, which is correct. Internally they're three different jobs with three different owners, and treating them as one thing is why so many launches stall.

Setting it up without regrets

Four decisions to make before you publish a single article.

The domain. Put it on a subdomain of your own domain rather than a HubSpot-hosted address. It looks like you, it keeps the search equity, and changing it later means redirects for every article URL.
Public or gated. A public help center is findable in search engines, which is where a surprising share of your traffic will come from. A gated one is not. Gate only what genuinely must be gated, and accept that gating trades deflection for control.
Language and audience. If you support more than one language, decide the structure now. Retrofitting translations onto a category tree built for one language is miserable.
Branding. Match your product, not your marketing site. People arriving at the help center are usually mid-problem and mildly annoyed. Clean and fast beats art directed.

Structure: fewer categories than you think

The instinct is to mirror your org chart or your product menu. Both produce a tree nobody can navigate.

Structure it by what customers are trying to do. Getting started, billing and invoices, account and access, plus one category per major product area. Six to eight top-level categories is plenty. If you need a third level of nesting, your categories are wrong.

A few rules that hold up:

One article, one question. A 3,000 word article covering nine scenarios ranks for nothing and answers nobody.
Title the article as the question is asked. "Why is my invoice different this month" beats "Billing cycle adjustment policy" every time, in both search and comprehension.
Write the top ten first. Pull your ten most repeated ticket topics from your own data. That's your launch content. Everything else is a backlog.
Kill the empty category. A category with one article in it reads as neglect and trains people to skip the help center.
Almost every help center that gets ignored was structured around the product rather than the problem. The fix is a rewrite of the category names, not more articles.

Search, and the route out

Two things determine whether the help center reduces your ticket volume: whether search finds the article, and how easy it's to give up.

Search is largely keyword driven, so the words your customers use have to appear in your articles. They say "password", your documentation says "credential reset". Read your own ticket subjects and use their vocabulary, not yours.

The route out matters just as much. Every article needs an obvious way to contact support that carries context with it. A customer who reads three articles, fails, and then hunts for a contact form will describe their problem worse and rate you lower. Make giving up cheap and you'll get better tickets.

Measuring it honestly

Article views are a vanity metric. Three numbers that mean something:

Ticket volume for the topics you documented, before and after. Deflection is topic-shaped, not site-wide.
Searches with no result. The best content roadmap you'll ever get, written by your customers.
Contact rate after an article view. If it's high on a specific article, that article is wrong, not popular.

Known limits

Nothing fatal, but worth knowing before you promise anything.

The knowledge base sits on paid Service Hub tiers, not the free tools, so check which tier you were quoted.
Layout customisation is template-bound. You can brand it well. You can't rebuild it into an arbitrary web app.
Approval workflows for content are thin. If you need formal editorial sign-off, you'll be enforcing it socially rather than in the tool.
Search isn't semantic by default. Synonyms and near misses need help from the words you write.
FAQ

Frequently asked questions

What does HubSpot help center setup involve?

Connect a domain, pick the template, then structure the categories. The HubSpot knowledge base help center is your self service portal, and HubSpot help centre setup is mostly deciding what the top ten articles are before you style anything.

Is the HubSpot help center the same as the knowledge base?

They are two halves of one system. The knowledge base is where you write and organise articles. The help center is the public site where customers read them.

Can the HubSpot help center use our own domain?

Yes, and you should set it up on a subdomain of your own domain from the start. Moving it later means redirecting every published article URL.

Does the help center need a paid Service Hub tier?

Yes. The knowledge base and help center aren't part of the free tools. Confirm the tier before you plan a content project around them.

How many articles do we need to launch?

Ten good ones covering your most repeated ticket topics beats sixty thin ones. Launch small, then use no-result searches to decide what to write next.

When self-service creates duplicates

A customer who fails at the help center often emails and opens a chat about the same thing. Ticket Merger catches those pairs on Zendesk and Freshdesk today, and HubSpot support is coming.

Start free trial

14-day free trial. No credit card required.