Content KPIs by Content Type

Last reviewed on 2026-05-12.

"Are we measuring content properly?" is the wrong question. The right question is whether you are measuring the right thing for the kind of content you are producing. A KPI that makes perfect sense on a landing page can be actively misleading on a long-form blog post.

The framing here is simple: each major content type has a primary KPI (the one that tells you whether the content is doing its job), a few supporting metrics (which give context), and one or two vanity metrics that look impressive but rarely tell you anything useful about the underlying decision.

Blog and long-form content

Primary KPI: Organic traffic to the page, weighted by relevance. Total sessions tells you it is being read. Sessions filtered to the target audience (or a proxy: search query, source, geography) tells you whether the right people are reading it.

Supporting metrics: Keyword position for the primary query, scroll depth or read-time on the page, internal-link clicks out of the page, assisted conversions over a longer window.

Where teams go wrong: Measuring blog content on direct conversions. Most blog pieces are top- or mid-funnel. If the only thing you track is "demos booked from this page", you will defund pages that are doing the actual work of bringing buyers into the funnel weeks earlier.

Time horizon for blog content is also routinely too short. A piece published this month rarely shows its real performance until three to nine months later, after Google has settled on a ranking and the page has had time to accumulate internal and external links.

Landing pages and product copy

Primary KPI: Conversion rate against the page's defined goal, compared to the previous version under similar traffic conditions.

Supporting metrics: Bounce rate, scroll depth, time-to-first-CTA-click, traffic mix by source (paid vs organic vs referral), heatmap of where readers stop scrolling.

Where teams go wrong: Comparing conversion rate across pages with different traffic sources. A landing page that converts at 8% from paid search and one that converts at 3% from organic discovery are often doing the same job differently — paid traffic is more pre-qualified. Comparing them like-for-like leads to bad decisions about rewrites.

Another common mistake: changing copy and design in the same release. If conversion improves, you do not know why.

Technical documentation

Primary KPI: Reduction in support volume on the topics the docs cover. Hardest to measure cleanly, but the most honest signal that the documentation is doing its job.

Supporting metrics: Time-to-first-successful-API-call (for developer docs), in-page search queries (which reveal where readers cannot find what they need), feedback-button ratios on individual pages, completion of a "first task" defined in advance.

Where teams go wrong: Measuring docs on traffic. High-traffic doc pages can mean the docs are doing well or that the same page keeps being googled because the in-product help failed. The two have opposite implications.

Email programmes

Primary KPI: Depends on the email's job in the lifecycle.

• For onboarding: activation rate of the cohort that received the sequence vs a holdout.
• For promotional: revenue per email (and revenue per recipient, which controls for list size).
• For retention: churn rate among engaged recipients vs the rest.

Supporting metrics: Click-through rate, unsubscribe rate, bounce rate, deliverability indicators. Open rates have become noisy since Apple Mail Privacy Protection; treat them as directional, not precise.

Where teams go wrong: Optimising for open rates. Subject-line A/B tests that improve opens but hurt clicks or conversions are common. The metric is not what gets opened — it is what gets actioned.

The vanity-metric problem

Most "vanity metrics" are not useless; they are just easily over-weighted. A short list of metrics worth keeping a wary eye on:

• Pageviews in isolation. Useful as a sanity check, not as a target.
• Average time on page at the site level. Heavily distorted by sessions where the user opened a tab and left.
• Social shares. Easy to count, weakly correlated with anything else that matters.
• Newsletter open rate in 2026 — noisy enough that movements of a few percentage points are not necessarily real.

Use them, but do not steer by them.

A small checklist before agreeing a KPI

Before locking in a KPI for a piece of content, run through five questions:

1. What decision will this metric change? If "none", do not bother tracking it.
2. How long will it take for the metric to be reliable? Some metrics need weeks; some need quarters.
3. Could the metric move for reasons unrelated to the content? If yes, name them up front.
4. Is the metric inside the team's control? Pipeline metrics often are not.
5. Is there a baseline to compare against? Without one, "improvement" is a feeling.

Where this fits

Choosing the right KPI is a part of the brief — it is where the "success measure" line gets filled in. The KPI also drives what you look for in a content audit: a page that "did not work" probably did not move the KPI you originally chose. And in B2B contexts, the right KPI tends to look different to its B2C counterpart, which is the subject of the B2B vs B2C piece.

If you are setting up KPIs for a new content programme and want a second pair of eyes on the framework, the next step is a short conversation. [email protected] or the contact form.