This guide covers a five-step knowledge base gap analysis you can run in an afternoon on a WordPress help desk, using ticket reasons, doc reads, helpfulness votes, and failed searches. We tested it on our own setup for almost a year and are now sharing it with you.<\/p>\n\n\n\n
What Is a Knowledge Base Gap Analysis?<\/h2>\n\n\n\n
A knowledge base gap analysis (also called a knowledge base audit or documentation gap analysis) is a review that compares the questions customers bring to support with the answers your documentation already gives. <\/p>\n\n\n\n
It finds the topics with no doc, the docs nobody can reach, the docs that mislead, and the docs that have gone out of date. Support tickets are the best place to start, because every ticket is a customer who looked for an answer and did not get one.<\/p>\n\n\n\n
Four Kinds of Knowledge Base Gaps<\/h3>\n\n\n\n
Not every gap is a missing article, and the difference matters because each kind has a different fix.<\/p>\n\n\n\n
- \n
- Missing:<\/strong> no doc covers the question. Write one, titled the way customers phrase the problem.<\/li>\n\n\n\n
- Buried:<\/strong> a doc exists, but customers do not reach it. This is usually a title, topic or linking problem.<\/li>\n\n\n\n
- Wrong:<\/strong> customers read the doc and still write in. Helpfulness votes are the tell. The cause is often a doc written for a different reader than the one asking, such as a developer guide answering a beginner’s question. Rewrite it around the task.<\/li>\n\n\n\n
- Stale:<\/strong> the doc describes an old version of the product, or two docs give conflicting answers. Update it, merge the duplicates, and record a review date.<\/li>\n<\/ul>\n<\/div>\n\n\n\n
A fifth case sits outside the docs entirely. A bug or a missing feature that no article can repair. Enterpret’s guide to help center content gaps<\/a><\/strong> draws the same line between missing, outdated, hard-to-find, and needs-a-product-fix content, and estimates that about a third of apparent doc gaps are really product problems.<\/p>\n\n\n\n
Why Support Tickets Beat Page Analytics?<\/h3>\n\n\n\n
Page analytics describe the docs you have. Tickets describe the docs you need.<\/p>\n\n\n\n
A traffic report cannot show you an article that does not exist, and it cannot tell you which question sent a customer to your inbox instead. Tickets also carry the customer’s own wording, which is what future search queries will look like. <\/a><\/p>\n\n\n\n
Gartner’s 2024 self-service survey<\/a><\/strong> found that only 14% of customer service issues were fully resolved in self-service, and just 36% even for issues customers called very simple. Read that as context rather than a target. Your own tickets will show you faster where your docs sit on that scale.<\/p>\n\n\n\n
How to Run a Knowledge Base Gap Analysis From Support Tickets<\/h2>\n\n\n\n
You can find your knowledge base gaps in five steps, using ticket reasons, doc reads, helpfulness votes, and failed searches.<\/p>\n\n\n\n
\n- \n
- Give every ticket a reason.<\/li>\n\n\n\n
- Count tickets by reason.<\/li>\n\n\n\n
- Check the docs behind each top reason.<\/li>\n\n\n\n
- Add failed searches to the picture.<\/li>\n\n\n\n
- Sort each finding into a gap type and choose the fix.<\/li>\n<\/ol>\n<\/div>\n\n\n\n
The walkthrough uses NiroHelp, but the method works in any help desk that lets you tag tickets and see doc stats. The screenshots come from a demo desk for a fictional form plugin called Acme Forms, with 70 tickets and 14 docs.<\/p>\n\n\n\n
Step 1: Give Every Ticket a Reason<\/h3>\n\n\n\n
A reason is a short label that says why the customer wrote in. It is the field the rest of this analysis counts, so get it right before anything else.<\/p>\n\n\n\n
![\"Knowledge](\"https:\/\/nirohelp.com\/blog\/wp-content\/uploads\/2026\/10\/knowledge-base-gap-analysis-tickets-reason-column.webp\")
<\/figure>\n\n\n\nIn NiroHelp, you create reasons under NiroHelp \u2192 Reasons<\/strong>. The customer picks one on the ticket form, where the dropdown is labelled “Topic” by default, and an agent can change it in the ticket editor when the customer picked the wrong one. The ticket reasons documentation<\/a><\/strong> covers renaming the field and making it optional.<\/p>\n\n\n\n
One catch:<\/strong> the Topic dropdown is optional by default, so customers can skip it and those tickets count as nothing. Make it required under Settings \u2192 Tickets \u2192 Form fields<\/strong>, or your counts will undercount your busiest problems.<\/p>\n\n\n\n
![\"Knowledge](\"https:\/\/nirohelp.com\/blog\/wp-content\/uploads\/2026\/10\/knowledge-base-gap-analysis-ticket-reasons-box.webp\")
<\/figure>\n\n\n\nKeep the list to six or eight reasons. A long list gets picked badly, and a reason nobody picks consistently counts for nothing. Describe the problem, not the product: “License activation” works, “Acme Forms Pro” does not. Because customers choose the reason themselves, treat your first counts as approximate and skim the ticket titles before you trust a number.<\/p>\n\n\n\n
Starting with a backlog? Tag the last 50 to 100 tickets by hand. It takes about an hour and gives you a usable count today instead of in a month.<\/p>\n\n\n\n
Reasons are part of the free plugin. You can install NiroHelp from WordPress.org<\/a><\/strong> on a staging site and add your first six reasons in a few minutes.<\/p>\n\n\n\n
Step 2: Count Tickets by Reason<\/h3>\n\n\n\n
Once tickets carry a reason, your biggest reasons are one screen away.<\/p>\n\n\n\n
The Reasons screen lists every reason with its ticket count. On the demo desk, License activation leads with 16 tickets, followed by How-to question with 14, then Billing and refunds and Bug report with 12 each.<\/p>\n\n\n\n
![\"Knowledge](\"https:\/\/nirohelp.com\/blog\/wp-content\/uploads\/2026\/10\/knowledge-base-gap-analysis-reasons-ticket-counts.webp\")
<\/figure>\n\n\n\nTo see what sits inside a reason, filter the agent queue. In NiroHelp, the queue built with the [nirohelp_all_tickets] shortcode can be filtered by agent, product, and time.<\/p>\n\n\n\n
![\"Knowledge](\"https:\/\/nirohelp.com\/blog\/wp-content\/uploads\/2026\/10\/knowledge-base-gap-analysis-queue-filtered-by-reason.webp\")
<\/figure>\n\n\n\nRead the titles, not just the number. Sixteen license tickets is a signal, but sixteen tickets asking five different questions is five docs. On the demo desk, they cover moving a license to a new domain, staging sites using up a seat, and finding the license key.<\/p>\n\n\n\n
Step 3: Check What Your Docs Say About Each Top Reason<\/h3>\n\n\n\n
For every top reason, ask three questions: is there a doc, do people read it, and does it help?<\/p>\n\n\n\n
The NiroHelp Docs list shows reads, a helpfulness percentage with the vote count, and the last updated date for each doc.<\/p>\n\n\n\n
![\"Knowledge](\"https:\/\/nirohelp.com\/blog\/wp-content\/uploads\/2026\/10\/knowledge-base-gap-analysis-docs-list-helpfulness.webp\")
<\/figure>\n\n\n\nThe dashboard’s Docs row adds four views:<\/p>\n\n\n\n
\n- \n
- Unhelpful docs<\/strong> ranks docs by their share of negative votes rather than the raw count, so a doc with three downvotes out of four outranks one with ten out of a thousand.<\/li>\n\n\n\n
- Gaps<\/strong> lists failed searches (Step 4).<\/li>\n\n\n\n
- Most read<\/strong> notes how many docs were never read or read only once.<\/li>\n\n\n\n
- Volume<\/strong> shows docs per topic, and a topic with no docs shows a 0.<\/li>\n<\/ul>\n<\/div>\n\n\n\n
The dashboard<\/strong> lists each panel.<\/p>\n\n\n\n
![\"Knowledge](\"https:\/\/nirohelp.com\/blog\/wp-content\/uploads\/2026\/10\/knowledge-base-gap-analysis-dashboard-docs-row.webp\")
<\/figure>\n\n\n\nHere is what that picture showed on the demo desk:<\/p>\n\n\n\n
\n- \n
- Licensing has 0 docs<\/strong>, while License activation is the biggest reason. That is a missing gap.<\/li>\n\n\n\n
- Conditional logic has 742 reads<\/strong> but only 41% helpful across 75 votes, and 7 of the 14 how-to tickets are about conditional logic. That is a wrong gap.<\/li>\n\n\n\n
- Connect Google Sheets has 0 reads<\/strong> and no votes, while 6 of the 10 integration tickets ask about Google Sheets. That is a buried gap.<\/li>\n<\/ul>\n<\/div>\n\n\n\n
Helpfulness votes tell you more than page views. A doc with 742 reads looks healthy until you see that 59% of the people who voted said no. Those votes come from the “Was this doc helpful?” buttons at the bottom of every doc. NiroHelp stores them as counts only, with no IP address or visitor identity. The flip side is that it does not block repeat votes either, so treat the percentage as a rough signal, especially on a doc with few votes. The doc voting documentation<\/a><\/strong> explains how votes are recorded.<\/p>\n\n\n\n
Step 4: Add the Signal Tickets Cannot Show<\/h3>\n\n\n\n
A ticket only exists if the customer gave up and wrote in. Failed searches catch the people who are still trying.<\/p>\n\n\n\n
NiroHelp records every docs search that returns nothing and lists the most frequent ones in the Gaps card on the dashboard, busiest first. The card needs no AI connection. On the demo desk, “transfer license to new domain” was searched 31 times with no result, followed by “refund policy” (24) and “vat invoice” (14).<\/p>\n\n\n\n
![\"Knowledge](\"https:\/\/nirohelp.com\/blog\/wp-content\/uploads\/2026\/10\/knowledge-base-gap-analysis-gaps-card.webp\")
<\/figure>\n\n\n\nIf your site is connected to the AI service, Ask NiroHelp<\/a><\/strong> can return the same list when you ask what docs you are missing. Check your plan on the features page first, since AI access depends on it.<\/p>\n\n\n\n
A cheap third signal costs your agents two seconds per ticket. Add a yes\/no field such as “Self-service possible?” and have agents set it as they reply. eesel describes teams doing this to build a list of tickets a doc could have prevented, which is the list you actually want to write from.<\/p>\n\n\n\n
Doing This With Other WordPress Tools<\/h4>\n\n\n\n
NiroHelp is not the only way to run this. Most docs plugins surface part of the picture, and the tier you are on decides how much.<\/p>\n\n\n\n
\n- \n
- BetterDocs<\/strong> has analytics with a “Keywords With No Result” view, reactions, and a feedback inbox with Reviewed and Resolved states and CSV export. Its ticketing is separate, so reasons live in whatever help desk you pair it with.<\/li>\n\n\n\n
- Heroic Knowledge Base<\/strong> tracks failed searches and feedback in its analytics.<\/li>\n\n\n\n
- Echo Knowledge Base<\/strong> reports no-result searches, with ratings and feedback in its PRO tier.<\/li>\n<\/ul>\n<\/div>\n\n\n\n
Check your tier before relying on any of these, because features move between plans. If you already run BetterDocs and want tickets and docs in one place, NiroHelp can import your BetterDocs docs, categories, and votes<\/a> without touching the original data.<\/strong><\/p>\n\n\n\n
Step 5: Sort Each Finding and Choose the Fix<\/h3>\n\n\n\n
Now turn the findings into a short, ordered list. Each one gets a gap type and a matching fix.<\/p>\n\n\n\n
- Heroic Knowledge Base<\/strong> tracks failed searches and feedback in its analytics.<\/li>\n\n\n\n
- Conditional logic has 742 reads<\/strong> but only 41% helpful across 75 votes, and 7 of the 14 how-to tickets are about conditional logic. That is a wrong gap.<\/li>\n\n\n\n
- Gaps<\/strong> lists failed searches (Step 4).<\/li>\n\n\n\n
- Unhelpful docs<\/strong> ranks docs by their share of negative votes rather than the raw count, so a doc with three downvotes out of four outranks one with ten out of a thousand.<\/li>\n\n\n\n
- Buried:<\/strong> a doc exists, but customers do not reach it. This is usually a title, topic or linking problem.<\/li>\n\n\n\n