Skip to main content
All posts

Measuring content

Is NPS still worth it on a content site?

By 9 min read

Net Promoter Score is the most familiar customer question there is. You ask how likely someone is to recommend you on a scale of 0 to 10, subtract the share of detractors from the share of promoters, and get one number to track.

It also has a long list of critics, including the people who invented it. This post covers what they say, why NPS fits content sites and single web pages particularly badly, and what to ask instead. The NPS calculator covers how the score is worked out, so this post skips that part.

The short answer

For a product or a membership, asked a few times a year, NPS still works as a trend line. On a content site it usually asks the wrong thing. "How likely are you to recommend us?" is about your whole brand, and a reader who arrived from search has just read one page. Ask about that page instead: a one-tap "Did this page help?", a 1 to 5 satisfaction rating (CSAT) or an effort question (CES). Keep NPS for the few places where readers know you well enough to answer it.

What NPS was built to measure

Fred Reichheld and Bain & Company introduced NPS in the early 2000s as a measure of customer loyalty for a whole company. The idea was simple: people who would recommend you are likely to come back and to bring others, so the share of them should predict growth.

That design shows in the question. It asks about "us", the company, and it asks about a future action, recommending. Both make sense for a bank, an airline or a software subscription that a customer uses every week. They make less sense for a guide someone found ten minutes ago.

What the critics of NPS say

The main criticisms fall into three groups.

  • It may not predict growth as claimed. In 2007, Timothy Keiningham and colleagues published a study in the Journal of Marketing that tried to repeat the original growth findings with longitudinal data from Norwegian firms. They could not reproduce the "clear superiority" of NPS over other measures such as customer satisfaction.
  • It is too broad to act on. In May 2021, Gartner predicted that by 2025 more than 75% of organisations would have abandoned NPS as a measure of success for customer service and support. Its analyst said NPS "consistently fails to provide actionable insight" for those teams, because the question covers far more than the service itself.
  • It is easy to game. When a score is tied to targets or bonuses, people start asking customers for a 10.

Note what the Gartner prediction was about: customer service and support teams, not NPS everywhere. It was a forecast, not a count of companies that stopped. It still points at the real weakness: one broad score doesn't tell a team what to change.

What its inventor now says

The sharpest criticism came from Reichheld himself. In his 2021 book Winning on Purpose, written with Darci Darnell and Maureen Burns, and in their Harvard Business Review article "Net Promoter 3.0", the authors admit that NPS has been badly misused.

They write that "self-reported scores and misinterpretations of the NPS framework have sown confusion". They describe companies linking scores to bonuses for frontline staff, staff pleading with customers for a top score, and one offer of free oil changes for a 10. They also point to "the response biases that plague the results of non-anonymized surveys", where customers know their answer can be traced back to them.

Their fix is a second number, earned growth, based on audited revenue rather than surveys. If you run NPS on a website, the same problems apply to you: a score someone is paid on, or one the customer knows can be traced back to them, tells you less than it seems to.

Why NPS fits a content site badly

On a content site or a marketing page, NPS has some extra problems on top of the ones above.

  • It asks about the wrong thing. A reader who landed on one article from search has no settled view of your brand. Their answer mixes the article, the ads, the page speed and their mood, and you can't separate them.
  • It takes thought. Picking a number from 0 to 10 is harder than tapping Yes or No, so fewer readers answer, and those who do are more often the ones with a strong opinion.
  • It hides the page. A site-wide NPS of 30 tells you nothing about which pages pull it down. Even per page, a low score says something is wrong without saying what.
  • It needs many answers. The score is the difference between two shares, so it moves a lot with a small sample. A page with 20 answers can move by 20 points from one month to the next by chance alone.

What to ask instead

Ask about the page the reader is on, in a form they can answer in one tap. These questions usually tell a content team more than NPS:

QuestionTypeWhat it tells youBest for
"Did this page help?"Yes / NoWhether this page did its jobArticles, guides, docs pages
"How satisfied are you with this page?"CSAT, 1 to 5 starsHow well a page or step went, with more range than Yes / NoHelp pages, checkout and sign-up steps
"How easy was it to find what you needed?"CES, a short choice list from "Very hard" to "Very easy"Where readers struggle to get what they came forDocs, help centres, long how-to pages
"What would make this page better?"Multiple choiceThe reason behind a low answerAfter any of the above
"How likely are you to recommend us?"NPS, 0 to 10Loyalty to the whole brandMembers, subscribers, logged-in product users

The CSAT calculator and the CES calculator work out those scores from your counts, and the NPS calculator does the same for NPS.

Tip: Whichever question you pick, follow it with one multiple choice question about the reason. A score tells you where to look; the reason tells you what to fix.

When NPS is still worth keeping

NPS is not useless. It still earns its place when:

  • The people answering know you well: paying members, subscribers, users of your product.
  • You ask it now and then, such as once a quarter, not on every page view.
  • You compare the score with your own past scores, collected the same way, more than with other companies.
  • Nobody is paid on it, so nobody has a reason to push it up.
  • You always ask for the reason straight after the score.

If your NPS is already part of a board report, you don't have to drop it. Move it to the place where it fits, such as the account page for members, and use page questions everywhere else.

Example

Example: a recipe site that swapped its question

Say you run a recipe site with 900 recipes and a paid membership for meal plans. Every recipe page ends with "How likely are you to recommend us to a friend?" and your site-wide NPS hovers around the same number each month. It never tells you which recipes to fix.

So you change the question on recipe pages to "Did this recipe work for you?" with Yes / No, then "What went wrong?" with the options "Timings were off", "Missing an ingredient", "Steps unclear" and "Something else". After a month, a dozen bread recipes stand out with a low Yes share, and most of their No answers pick "Timings were off". You retest the proving times, update the recipes and watch the Yes share on those pages.

You keep NPS, but only on the members' account page, asked once a quarter, because members are the people who can say whether they would recommend the meal plans. The score now describes the membership, which is the thing it can actually measure.

Where Asklet fits

Asklet asks short questions on the page they are about, from one snippet. Its question types include Yes / No, a 1 to 5 star rating, multiple choice and NPS (0 to 10), so you can run CSAT, an effort question and NPS from the same question bank, on different paths.

For NPS, results show the score with promoters, passives and detractors for each page, next to the reasons readers gave. Answers are anonymous, and a page shows only counts until it has 10 responses, so a handful of answers never turns into a dramatic score.

Your next steps

  1. Write down what your NPS is for

    If nobody can name a decision it changed in the last year, it is a candidate to move or drop.

  2. Ask a page question on your content pages

    Start with a one-tap "Did this page help?" and the same follow-up on every page.

  3. Use CSAT or an effort question on task pages

    Help pages, sign-up steps and how-to guides, where readers are trying to get something done.

  4. Keep NPS where people know you

    Members, subscribers or product users, a few times a year, always with a reason question.

  5. Never tie a score to pay

    Once a score decides a bonus, it starts measuring how hard people asked for it.

Try these steps on your own site. Asklet adds the questions to every page with one snippet. Free plan, no card needed. Compare the plans.

Start free

Common questions

Is NPS dead?

No. Plenty of companies still use it, and it works as a loyalty trend for a product or a membership. What its critics, including its inventor, reject is treating it as the one number that explains everything. On content pages, a question about the page is usually more useful.

What is the best alternative to NPS for a website?

For content pages, a one-tap "Did this page help?" with a reason question after it. For pages where readers try to complete a task, a CSAT rating or an effort question. Each one is about the page, so you know which page to fix.

Did 75% of companies really stop using NPS?

That figure was a 2021 Gartner forecast, and it was about customer service and support teams measuring their own success. It predicted a change; it did not count one. Treat it as a sign that service teams found NPS too broad, not as proof that most companies dropped it.

Can I ask NPS and a page question in the same survey?

You can, but each extra question loses some readers. On content pages, lead with the page question. If you want NPS too, ask it on fewer pages, such as your account or membership pages.

Sources

More from the blog

Get your first answers today.

Set-up takes a few minutes, and the free plan covers one website or app.

Start free

Free plan, no card needed.

en