HubSpot Knowledge Base: Plans, Setup, and Key Limits

Documentation and plan limits checked November 22, 2026. This independent guide is based on HubSpot’s published documentation.

Looking for help using HubSpot? Visit the official HubSpot Knowledge Base for product instructions and troubleshooting. The guide below explains the separate tool you use to build a knowledge base for your own customers.

HubSpot Knowledge Base is a customer self-service publishing tool available through Service Hub Professional and Enterprise. It lets teams organize help articles into a branded, searchable resource. HubSpot documents capabilities for article creation, language variations, access restrictions, and performance reporting on its knowledge base product page.

The buying decision depends on more than whether you can publish articles. Check the allowances attached to your account, how customers will authenticate, how much design control you need, and who will maintain the answers. If you plan to use AI, evaluate its content sources separately from the permissions on the published help center.

Jump to: Plans and limits · Setup · Private access · Languages · AI agents · Analytics · Migration · Fit and launch checklist

Which HubSpot Plan Includes a Knowledge Base?

Under HubSpot’s standard Service Hub packaging, the knowledge base starts at Professional. Free tools and Service Hub Starter do not include the builder. The following allowances come from the current HubSpot Product & Services Catalog, rather than older setup tutorials.

Standard Service Hub planKnowledge basesArticle allowance
Free tools / StarterNot includedNot applicable
Professional1Up to 2,000 articles
EnterpriseUp to 100Up to 10,000 articles total per account
Standard catalog allowances checked November 22, 2026. The Enterprise total is shared across the account’s knowledge bases.

There is a separate packaging exception. For customers enrolled in HubSpot’s flexible seats-and-credits pricing program, the applicable catalog supplement currently lists 100 knowledge bases and 10,000 total articles for both Professional and Enterprise. That supplement takes precedence where its terms conflict with the standard catalog. Confirm which program applies to your account before using a plan comparison to make a purchase.

For a quote, use the current Service Hub pricing page and your applicable order terms. Ask for a breakdown covering the subscription, staff seats, any required onboarding, and expected AI-credit usage. A plan name alone does not describe the whole operating cost.

Check Seats and Permissions Before Troubleshooting the Editor

The standard knowledge base creation instructions require an assigned Service Hub seat and either Super Admin or knowledge base settings permission. Accounts using alternative packaging should confirm their corresponding seat entitlements. These staff requirements are separate from customers’ access to published content.

Check the user permissions guide when someone can open an article but cannot create or publish it. HubSpot distinguishes article editing, creation through knowledge base settings access, publishing, and managing private content. Grant permissions for the person’s job instead of making every contributor a Super Admin.

An effective operating model separates the subject expert who verifies the answer, the editor who maintains the article, and the administrator who controls domains and audience access. Record those responsibilities before importing a large content collection.

How to Set Up a HubSpot Knowledge Base

These steps follow the current knowledge base editor. If an older account shows a different interface, check its migration status before combining instructions from current and legacy documentation.

1. Choose the Domain and Create the Knowledge Base

In HubSpot, go to More → Service → Knowledge Base, or directly to Service → Knowledge Base if More is absent. For the first knowledge base, select Set up your new knowledge base. Enter its title, primary language, hosting domain, and URL path; then choose a homepage template and initial categories. Complete the wizard with Done. See HubSpot’s current setup workflow.

HubSpot knowledge base setup fields for title, primary language, domain, and URL slug.

Plan the address before distributing article links. If your main website is hosted on WordPress or another platform, a dedicated help subdomain, such as help.example.com, is a practical separation. HubSpot’s domain connection documentation explains the DNS and hosting requirements; a domain or subdomain cannot simultaneously host different content in two locations.

Assign someone with DNS access to the connection work. Keep a list of existing help URLs and their intended destinations if you are replacing a previous site. Coordinate domain changes with link and redirect checks.

2. Organize Articles Around Customer Tasks

Use category names customers recognize. A software help center might start with Getting Started, Account Access, Billing, and Troubleshooting. Those are illustrative categories, not a required HubSpot structure. Add subcategories when they help people distinguish tasks; avoid copying your internal department chart.

HubSpot requires an article to belong to a category before publication. Its category and tag documentation also clarifies that tags assist internal knowledge base search without appearing to visitors. Moving an article into another category does not automatically change its URL.

Give each question one authoritative answer. For example, put the password-reset procedure in a single article and link to it from onboarding and troubleshooting content. Separate articles are more useful when the instructions differ, such as an administrator resetting another person’s access.

3. Write, Preview, and Publish a Complete Answer

Create an article and add its title and body. In the article settings, review the URL, category, language, metadata, and audience access. HubSpot’s article editor documentation covers these controls and previews for desktop, tablet, and mobile.

A useful article should let a reader complete one task without guessing. Use this content pattern as an editorial starting point:

  • Outcome: state what the reader will accomplish.
  • Prerequisites: identify the necessary role, access, or information.
  • Steps: use the actual interface labels in the order someone encounters them.
  • Expected result: explain how the reader can confirm success.
  • Exceptions: cover the likely blocker and provide the appropriate support route.

For an illustrative “Change the billing contact” article, identify who can make the change, explain where to edit the address, and distinguish future notifications from invoices already issued. Have someone who did not write the draft follow it before publication. That exercise tests the answer’s usefulness without relying on article length as a quality measure.

4. Customize the Theme Within Its Supported Boundaries

Open Configure → Theme to adjust the available styling and layouts. HubSpot’s theme customization guide distinguishes theme controls from the global content editor used for header and footer content. It also states that knowledge bases do not support Design Manager or custom themes.

HubSpot knowledge base homepage layout options: Content rich, Tiles, Minimal, Cards, and Classic.

Start with readable typography, a clear search entry point, and category names that fit on a phone. Then test a long troubleshooting article, a numbered procedure, and a page containing a table. A polished homepage does not show whether real support content remains usable.

If your design requires an unusual article layout or deeply customized navigation, validate that requirement in a representative prototype before purchasing or migrating. Supported code settings should not be treated as a promise of unrestricted theme development.

How Public and Private Knowledge Base Access Works

Under Settings → Content → Knowledge Base, the knowledge base settings support mixed public/private content, required access-group membership, or required single sign-on. Individual article restrictions still matter when public and private content coexist. Saving changes to the knowledge base domain or slug immediately changes live article URLs.

For membership-based access, HubSpot organizes contacts into static or dynamic access groups. Its private-content documentation requires a connected subdomain configured for the content type; default HubSpot domains are not supported for that setup. Decide who should qualify for access before adding contacts or changing group rules, because those actions can trigger registration invitations.

HubSpot article access settings with access-group membership required and a support members group selected

Content-access SSO is separate from the login your employees use to enter the HubSpot application. Follow the private-content SSO instructions with an IT administrator. HubSpot warns that assets such as images and forms can be accessible through their direct URLs even when the containing page requires SSO. Review sensitive attachments independently.

Search visibility is also a separate control. The crawler setting documented for the knowledge base concerns its search-results pages. It does not make every article private. A noindex directive tells search engines about indexing; it does not authenticate a reader.

Before launch, test the same restricted article in three situations: signed out, signed in as an eligible contact, and signed in as an ineligible contact. Check direct links and embedded files as well as navigation. Use representative test accounts rather than relying on an administrator’s view.

How to Add Multiple Languages

HubSpot supports language variations for knowledge base content. The documented workflow is to add the language in settings, translate the relevant categories and subcategories, and create article variants. The multilingual knowledge base guide explains that untranslated categories and subcategories display a Needs translation label.

Treat each translation as maintained content. Assign a reviewer who understands the product terminology, and include linked articles, screenshots, and error messages in the review. Creating a language variant does not establish a process for keeping it accurate when the original changes.

Keep a small change log identifying the source article, the changed instruction, affected languages, and translation owner. Prioritize changes that affect whether a customer can complete the task. A revised button label deserves faster attention than a stylistic rewrite.

Knowledge Base Agent vs. Customer Agent

HubSpot’s AI features serve different jobs. One helps your team develop knowledge content; the other uses selected content to answer customer questions. Evaluate the quality and disclosure risks of each workflow separately.

Knowledge Base Agent Helps Create and Improve Articles

The Knowledge Base Agent, currently documented as beta, uses closed-ticket conversations to identify knowledge gaps and suggest articles or changes. Requirements include an existing knowledge base, at least five closed ticket records, and the Customer conversation data setting enabled by a Super Admin. The agent can be active on only one knowledge base at a time and drafts in its primary language. Generating a new article uses HubSpot Credits; accepting edits to an existing article does not.

HubSpot Knowledge Base Agent suggestion with a summary, Generate article button, and source conversations

Review the underlying conversation before approving a suggestion. A successful one-off workaround may depend on a particular customer’s configuration and should not become universal guidance. Remove personal information, check product behavior, and verify that the final steps are repeatable.

Customer Agent Answers From the Sources You Provide

The Customer Agent setup guide describes an answering workflow that can respond from supplied content, ask clarifying questions, and hand conversations to a person. Its deployment uses credits under the applicable billing rules. Do not assume knowledge base publishing allowances also cover unlimited AI usage.

Review private sources before connecting them. HubSpot’s Customer Agent source-management documentation says sources marked public or private may inform publicly shared responses. A private source may be omitted from citations while its content still informs an answer. Private article access is therefore not a sufficient control over what the agent can disclose.

The same documentation distinguishes update behavior: connected HubSpot knowledge base articles resync when updated, while other source types resync weekly. After a consequential policy or procedure change, verify the answer in the deployed experience instead of assuming every source has already refreshed.

Build a test set containing a routine question, an ambiguous request, an outdated procedure, a question the approved sources cannot answer, and a request for restricted information. Decide the acceptable response or handoff for each before activation. Keep the test questions for later regression checks.

Measure Whether Customers Find Useful Answers

Open the knowledge base’s Analyze tab and select the reporting period. HubSpot’s performance reporting documentation explains article views, viewing time, helpfulness feedback, search queries, and result clicks. Older interfaces may label this area Insights.

HubSpot article health report with views, average time on article, and helpful and unhelpful ratings
SignalWhat it tells youUseful follow-up
Article viewsHow often an article was loaded, including supported chat-widget views.Check whether frequent views reflect a common task or a recurring product problem.
Average time on articleAverage viewing duration, not proof that the instructions worked.Observe a reader performing the task before concluding that more time is better.
Helpful / unhelpful responsesReader feedback on the article.Review the answer, prerequisites, and missing exceptions when negative feedback accumulates.
Searches with no resultsQueries for which the knowledge base returned no matching articles.Look for missing coverage, customer vocabulary, or unclear titles.
Average result clicksArticle clicks per search; this is not a percentage of successful searches.Investigate whether readers are comparing useful answers or opening several unsuccessful results.
Use reporting signals to select questions for investigation; do not equate activity with resolution.

A practical review starts with a troublesome search query and follows the whole journey: what the customer typed, what appeared, which article they opened, and whether the instructions answered the question. Change the title, content, or category that caused the failure, then repeat the task with the revised experience.

Do not calculate “tickets prevented” by counting page views. To evaluate self-service outcomes, define what success means, connect the available support and feedback evidence, and acknowledge customers who leave without resolving anything. Changes in ticket volume can also reflect customer growth, outages, or changes in support availability.

Assign an owner and a review trigger to important content. A product release, policy change, or repeated escalation should trigger a check even when the article’s traffic looks healthy. Prioritize incorrect instructions that block a task over articles that merely need polishing.

Importing, Migrating, and Exporting Articles

Importing From Another Help Center

HubSpot documents imports from Freshdesk, Help Scout, Zendesk, and Intercom, as well as CSV. The article import guide limits each import to 400 articles, does not support importing tables, and places imported articles in the knowledge base’s primary language. Its smart-copy option is available for newly created or migrated knowledge bases.

For CSV preparation, include columns for URL, Title, Category, Meta description, and Article Body. The guide’s detailed mapping marks Meta description as required even though its introductory field list omits it. Prepare that field to avoid an unnecessary mapping interruption.

Run a small pilot containing the hardest article types before a full import. Choose drafts for review, then inspect images, lists, links, formatting, audience access, and the published result. Rebuild unsupported table content deliberately. Map old URLs to the new destinations and test redirects before retiring the previous help center.

Migrating a Legacy HubSpot Knowledge Base

This is a different process from importing a competitor’s content. HubSpot’s legacy migration documentation describes copying content to the newer platform, making the original read-only, and using temporary review URLs before publication. Published migrated articles use their original URLs. The old version remains available for 30 days after publication and is then deleted.

Review the migrated experience before publishing it. Check navigation, images, drafts, private access, and frequently shared article links. Do not treat the presence of a migrated copy as confirmation that the replacement is already live.

Exporting Article Data

HubSpot’s export documentation provides an article export through the knowledge base’s Actions menu, with spreadsheet formats such as CSV, XLS, and XLSX. Treat this as an article-data export. The documented workflow does not establish that it is a complete, restorable backup of the theme, domains, assets, and access configuration.

Keep a separate record of the configuration you would need to rebuild the help center. Before committing to a migration, inspect an actual export and confirm that it contains the content your next system requires.

Is HubSpot Knowledge Base the Right Fit?

It is worth evaluating when your service team already operates in HubSpot and wants a customer help center within that environment. It deserves a closer comparison when the knowledge base is your main purchase, your design requirements exceed the supported theme controls, or your migration depends on preserving complex content.

Your priorityWhat to validate before committing
A help center within existing service operationsWho will own the articles and how support conversations will produce content improvements.
Several brands or product linesKnowledge base and article allowances under your actual commercial program.
Restricted customer or employee documentationThe complete membership/SSO journey, direct asset access, and separate AI-source approval.
A heavily customized documentation siteThe exact layout and navigation requirements in the supported theme editor.
Moving a large existing libraryImport batches, unsupported formatting, language mapping, redirects, and export suitability.
Use a representative article and customer journey to compare HubSpot with a dedicated knowledge base platform.

Ask for a demonstration using your difficult requirements rather than a generic feature tour. Bring an article with a table, a restricted document, a translated procedure, and a search query customers commonly phrase incorrectly. Record what works, what requires manual effort, and what remains unverified.

Prelaunch Checklist

  • Confirm the account’s applicable plan, seat model, article limits, and AI-credit terms.
  • Verify the help domain, final URLs, inbound links, and required redirects.
  • Have someone outside the writing team complete a common task using a published article.
  • Test restricted content as an eligible reader, an ineligible reader, and a signed-out visitor.
  • Review translated categories, article variants, and links in each launched language.
  • Approve AI sources separately and test unclear, unsupported, and restricted questions.
  • Establish a reporting baseline and assign content owners and review triggers.

Start with a coherent set of answers to recurring customer tasks. Publish only when those answers are accurate, reachable by the intended audience, and easy to follow. Then use searches, feedback, and support conversations to decide what to improve next.