Help Centre Analytics: Know What Your Users Actually Read
SupportPages help centres now include analytics: visitors, article views, UTM attribution and bot filtering. See which articles your users actually read.
Here's a question most SaaS teams can't answer: which of your help articles did anyone read last week?
Support tickets get measured obsessively. Response time, resolution time, CSAT. But the thing that's supposed to prevent tickets - your documentation - usually has no instrumentation at all. You find out an article failed when someone opens a ticket anyway. You never find out an article succeeded, because success is silent.
That asymmetry bothered me. So SupportPages help centres now come with analytics built in.
What you get
Every SupportPages help centre now tracks, out of the box:
- Visitors and page views, per article and per section, with a live 24-hour view
- Where readers came from - referrers and UTM parameters, so a docs link in your onboarding email is distinguishable from organic search
- Bot filtering - crawlers are excluded, so the numbers reflect humans, not Googlebot politely reading everything twice
There's nothing to install and no third-party script to consent-manage. It's part of the help centre.
Why this matters for docs specifically
Documentation has a strange feedback loop. When it works, nothing happens. When it fails, the failure shows up somewhere else - in your support inbox, days later, wearing a different costume.
Analytics shortens that loop. A few things become visible almost immediately:
The articles nobody reads. If an article gets no traffic, either the feature is self-explanatory (great) or nobody can find the article (bad). Both are worth knowing before you write ten more like it.
The articles everybody reads. Your most-viewed help article is a signpost. It's the part of your product where users most often need help. That's not just a docs insight - it's a product insight.
The searches that go nowhere. When people arrive, search, and leave, you've found a gap. That's an article you should have written already - and with SupportPages, one you can generate today.
The bigger picture
SupportPages exists because docs drift out of date the moment you ship. Generation keeps them current. But current isn't the same as useful - and useful is something you can only judge with data.
This is the first piece of that. Measure what gets read, generate what's missing, and let the two feed each other.
We're still pre-launch and working closely with design partners. If you want a help centre that writes itself and tells you whether it's working, take a look at supportpages.io and get in touch.
About the Author
Simon Moxon has been building SaaS companies since 2009. He's scaled teams to 20+ people, hit £2m ARR, and learned most of the lessons the hard way. Now he's building SupportPages.io - help docs that write themselves when you ship code. He writes about what's changed in SaaS and what hasn't.