Skip to content
GPLWP Guides

How to create a knowledge base for customer support on WordPress

Content Time About 30–60 minutes 6 steps Updated 9 Nov 2026

CONTENT
The short answer

You can build a small WordPress knowledge base with pages, parent pages, menus and the Search block. For a larger support library with article categories, dedicated archives, analytics or SupportCandy suggestions, use a knowledge-base plugin instead.

The route
  1. 01Plan the knowledge base
  2. 02Build it with WordPress pages
  3. 03Create the article structure
  4. 04Add navigation and search
  5. 05Choose a dedicated system
  6. 06Use the fast SupportCandy route

What you need

  • WordPress administrator access
  • A list of common customer questions
  • Support content, screenshots or product documentation

Plan the knowledge base

List the questions customers ask repeatedly, then group them into a small number of clear sections such as Getting started, Account and billing, Troubleshooting and Integrations. Use the words customers search for in section and article titles.

Give every article one job. A title such as How to reset your account password is easier to find than a broad title such as Account help.

Build it with WordPress pages

For a small library, go to Pages and create one top-level page for the knowledge base, then create child pages for sections and individual articles. WordPress supports parent pages and subpages, so the URL and page hierarchy can reflect your structure.

Add a Search block to the main page and place the knowledge-base page in your site navigation. This manual route is fine for a few dozen stable articles, but pages do not support categories or tags by default. You will also maintain section links and article groupings yourself, and the normal site search may return blog posts, pages and unrelated content together.

Create the article structure

Use the same layout for every article: a short answer first, numbered steps, warnings for destructive actions, screenshots where they clarify a screen, and links to related articles. Finish with a brief statement explaining what the reader should do if the article does not solve the problem.

Keep product names, button labels and screenshots current. A knowledge base becomes a support problem when an article describes an old dashboard and customers cannot find the controls it mentions.

Add navigation and search

On the knowledge-base landing page, list each section with a short description and links to its articles. Add the page to your Navigation block or classic menu, and test the menu on a phone. The Navigation block supports page links and nested submenus, but once a page list is converted into individual links, newly published pages are not added automatically.

Test searches for customer wording, not just your internal terminology. If results include too much unrelated site content, make the article titles more specific or move to a dedicated knowledge-base system.

Choose a dedicated system

Use a dedicated knowledge-base plugin when you need article categories, tags, archive pages, article feedback, analytics, restricted content or a separate search experience. The other technical route is a custom post type with taxonomies, but that requires development and careful decisions about templates, URLs, search visibility and data portability. WordPress recommends registering custom post types in a plugin rather than a theme so the content remains available if the theme changes.

Do not convert hundreds of support articles into ordinary pages without a migration plan. Changing post types or URL structures later can break internal links and search-engine indexing.

Use the fast SupportCandy route

If you already use SupportCandy, the fast route is to install a supported knowledge-base plugin and then use Support > Settings > Knowledgebase to select it. SupportCandy can show a knowledge-base link below the ticket reply box, let agents insert an article link or its content, and suggest articles by comparing ticket-subject words with article tags.

SupportCandy Knowledgebase Integration is the shortcut to consider when your goal is to deflect repetitive tickets and give agents article suggestions inside tickets. It is an integration layer rather than a replacement for the underlying knowledge-base plugin, so check that your chosen knowledge-base system is supported before installing it.

The fast route

Let SupportCandy Knowledgebase Integration do it

Connects searchable knowledge-base articles to SupportCandy to deflect repetitive tickets before users contact support.

Get SupportCandy Knowledgebase Integration

Sources

  1. wordpress.org /documentation/article/create-pages/?utm_source=openai
  2. wordpress.org /documentation/article/search-block/?utm_source=openai
  3. wordpress.org /documentation/article/navigation-block/?utm_source=openai
  4. developer.wordpress.org /reference/functions/register_post_type/?utm_source=openai
  5. supportcandy.net /docs/kb-general-settings/?utm_source=openai

Questions

Can I create a WordPress knowledge base without a plugin?
Yes, a small knowledge base can use WordPress pages, parent pages, menus and the built-in Search block. This works when you have a limited number of stable articles, but WordPress pages do not provide article categories or tags by default, and you must maintain navigation and related links manually.
Should knowledge-base articles be pages or posts?
Use pages for a small, mostly permanent support library because pages can be arranged in a parent-and-child hierarchy. Posts offer built-in categories and tags, but they are normally organised chronologically, which is not ideal for documentation. For a larger library, a dedicated knowledge-base post type is usually easier to manage than either ordinary pages or blog posts.
Will the normal WordPress search find knowledge-base articles?
Usually, the normal WordPress search can return published content such as pages and posts, but it is not automatically limited to your knowledge base. Results can therefore mix support articles with blog posts and other site content. Add the Search block for a basic search, then test customer wording and consider a dedicated knowledge-base search if the results are noisy.
When do I need a knowledge-base plugin?
You need a plugin when the knowledge base must have dedicated categories, article archives, feedback, analytics, restricted content or ticket-system integration. You can build those features with custom post types and taxonomies, but that is a development project involving content structures, templates, URLs and search behaviour.
How do I connect a knowledge base to SupportCandy?
Install a knowledge-base plugin supported by SupportCandy, then go to Support, Settings and Knowledgebase and select that plugin. SupportCandy can expose articles from the ticket screen and use article tags to suggest relevant content. If the knowledge-base plugin is not supported, the integration will not provide the expected article search and suggestions.