Help center article views

Help center article views are the total number of times articles in your help centre or knowledge base are opened within a defined period. It counts each page load of an article, including repeat visits, and it includes both customers who are signed in and anonymous visitors who arrive from search engines. A single customer reading three articles in one session contributes three views.

This metric matters because it is the most direct measure of self-service activity. Every article view is a moment where a customer tried to answer their own question instead of contacting support. When article views rise relative to ticket volume, more demand is being deflected before it reaches an agent, which lowers cost and shortens the time customers wait for an answer.

Views on their own do not tell you whether the customer succeeded. A high view count next to a high ticket count can mean the articles are being found but are not actually solving the problem. For that reason article views are most useful when read alongside deflection rate, article helpfulness votes and the volume of tickets in the same category.

The raw count is a simple sum of article page loads in the period. The decisions that make the number trustworthy are about what you include and how you segment it. Define each input once and apply it consistently so week-to-week comparisons hold.

1. 1

   Count article page loads

   Sum every page load of a help centre article in the period. Decide whether repeat views within a single session count once or each time, then keep that rule fixed across reporting periods.

2. 2

   Filter out internal and bot traffic

   Exclude views from your own support and content teams, and exclude crawler and bot traffic. Internal review activity and search engine bots can inflate the count and hide the real customer signal.

3. 3

   Segment by source

   Split views into search engine arrivals, in-product help links and in-app widget opens. The source tells you whether customers find articles through Google or through the product, which changes where you invest.

4. 4

   Normalise against demand

   Divide views by active customers, or compare views to ticket volume in the same category. A normalised rate reveals whether self-service is growing faster than the customer base or simply tracking it.

Article views are an outcome of three things working together: how many people need help, how easily they can find an article, and whether the content is worth reading once found. A metric tree separates these so you can tell why views moved rather than just that they did.

KPI Tree lets you connect each branch to the team that owns it. Search ranking sits with content and SEO, in-product links sit with product, and feature coverage sits with documentation. With RACI ownership on every node, a change in views routes a push to the accountable owner, and the verified impact loop checks whether the article they shipped actually moved deflection rather than just adding pages. That is the difference between a dashboard that reports views and a system that turns the number into a decision.

Absolute view counts are not comparable between companies because they scale with customer base and traffic. The useful benchmarks are ratios: views relative to tickets, the share of views from search, and the helpfulness rate of the articles being read. Use these ranges as a starting point and track movement against your own baseline.

Growing views is rarely about producing more articles. It is about making the right articles easy to find at the moment a customer needs them, and keeping the content good enough that people read it through. The following moves target discoverability and relevance rather than raw output.

1. 1

   Treating views as resolutions

   A view means an article was opened, not that the customer left satisfied. Counting views as deflected tickets overstates self-service success. Pair views with helpfulness votes and follow-on ticket rates to see the true outcome.

2. 2

   Leaving internal and bot traffic in the count

   Content reviewers, support agents and search crawlers all load articles. If they are not filtered out, the headline number climbs without any change in customer behaviour.

3. 3

   Chasing total views instead of high-value views

   Ten thousand views spread across low-demand articles matter less than a thousand views on the topics that drive your ticket volume. Optimise the articles that map to real support cost, not the vanity total.

4. 4

   Reading views in isolation

   Views only become meaningful next to demand. A rise in views during a product incident is expected, not a content win. Always read the metric against ticket volume and active customers in the same window.