
Measurement
Part of Reputation management measurement in review software
What the UK fake-review research can and cannot tell your reputation team
Reputation management benchmark research for England teams: interpret dated UK fake-review evidence, check comparable units and reject unsuitable targets.
Reputation management benchmark research should establish whether an external number is comparable before anyone uses it as a target. An England business needs the original population, measurement period, unit and collection method. A familiar percentage from a UK report may still be unsuitable for a branch dashboard.
The evidence below concerns a government-commissioned study of fake product reviews. It provides a dated research reference and a worked comparability decision, rather than an invented national norm for ratings, reply speed or conversions.
What to take away
- A UK fake-review estimate covers product categories, not services, so it cannot benchmark an England service business.
- Keep the April 2023 publication date attached, because the figure cannot establish present prevalence.
- The modelled prevalence estimate and the consumer experiment are separate components and should not merge into one score.
- Build a local reference series from your own branch records with matching platforms, dates and review types.
- Store the original figure, population, permitted use and rejected comparison on an evidence card.
What the published research measures
The Department for Business and Trade published its fake-review research record on 25 April 2023. It reports that 11% to 15% of reviews in three product categories on the e-commerce platforms studied were likely fake. Those categories were consumer electronics, home and kitchen, and sports and outdoors.
Fake-review research key figures
- 11% to 15%likely fake reviews
- 2.1 millionreviews modelled
- 9platforms studied
- 4,900UK experiment participants
The unit is a proportion of product reviews estimated to be fake. It is not a percentage of businesses, reviewers or customer complaints. The geography is UK e-commerce research, not an England-only branch sample. The publication date must remain attached to the number; a 2027 planning document does not make the observations contemporary.
The executive summary describes a predictive model applied to 2.1 million reviews across nine platforms. It separately describes an online shopping experiment involving 4,900 UK participants. These are different research components: a modelled prevalence estimate and an experiment about consumer choice. They should not become one general review-performance score.
Decide whether the figure belongs in your comparison
Decide whether the figure belongs
Research boundary
- Review subject
- Specified consumer product categories
- Geography
- UK platform and consumer context
- Measurement
- Predicted fake-review prevalence
- Date
- Research published April 2023
- Decision
- Understanding a research estimate
Implication for an England service business
- Review subject
- A service-review population is outside scope
- Geography
- No England estimate can be extracted from the headline
- Measurement
- Not equivalent to observed removal counts
- Date
- Cannot establish present prevalence without new evidence
- Decision
- Does not set an acceptable local fraud rate
The original publication says its findings do not extend to services purchased online or the impact of inflated star ratings. For a service firm, the defensible decision is to retain the report as background and reject it as a direct performance benchmark. A numerical value can be well sourced and still fail the comparison.
Research vs local benchmark fit
Research boundary
- Review subject
- Product categories
- Geography
- UK platform context
- Measurement
- Predicted prevalence
- Date
- Published April 2023
- Decision
- Research estimate
Implication
- Review subject
- Service reviews out of scope
- Geography
- No England estimate
- Measurement
- Not removal counts
- Date
- No present prevalence
- Decision
- Not a local fraud rate
Design a useful local reference series
Begin with comparable records from the business's own approved branch population. Define which platforms, dates and review types are included. Preserve branch-level results before constructing an aggregate so changes in branch mix remain visible.
Build a local reference series
- Start with approved branch records
- Define platforms, dates and review types
- Preserve branch-level results before aggregating
- Use same start event and time unit
- Show answered and unanswered reviews
- Request peer study selection method and coverage
- Disclose weighting before inspecting results
If benchmarking response handling, use the same start event and time unit across branches. State whether the series includes only answered reviews and display unanswered cases alongside it. A supplier's advertised response time cannot substitute for a measured reference series with matching definitions.
For a peer study, request the selection method, number of participating businesses, sector mix, coverage dates and exclusions. Find out whether participation was voluntary and whether the publisher sells services to the businesses measured. Such questions are proposed due-diligence steps, not assertions about any named report.
Avoid labelling a branch above average until the calculation is reproducible. Averages of branch averages weight branches equally; pooling underlying records weights them by record volume. Choose the weighting for the decision and disclose it before inspecting the result.
Keep an evidence card with every benchmark
Store the original figure, page or table location, publisher, publication date, access date and population. Add the permitted use and the comparison you rejected. Retain ranges as ranges when the source does not support a single preferred estimate.
Evidence card fields
- Original figure and page or table
- Publisher and publication date
- Access date and population
- Permitted use
- Rejected comparison
- Ranges retained as ranges
Before adding a benchmark to the next report, ask whether its unit can be reconciled with the dashboard measure without extra assumptions. If the answer is no, use an explanatory note and commission the missing research. Leaving a target unset is preferable to presenting a product-study estimate as measured performance for an unrelated English service.
Before you act
- Check the unit, population, period and collection method before comparing.
- Reject the product-review figure as a direct service benchmark.
- Define included platforms, dates and review types for your local series.
- Use the same start event and time unit across branches.
- Disclose the weighting before inspecting the result.
- Record the permitted use and the rejected comparison.
Common questions
What does the fake-review research actually measure?
It reports that 11% to 15% of reviews in consumer electronics, home and kitchen, and sports and outdoors on the platforms studied were likely fake. The unit is a proportion of product reviews, not businesses, reviewers or complaints, and the geography is UK e-commerce.
Why can the headline figure not be used for an England service business?
The research covers specified consumer product categories and a UK platform context, so no England estimate can be extracted. The original publication says its findings do not extend to services purchased online or the impact of inflated star ratings. Retain it as background only.
How should a reputation team build a defensible local benchmark?
Start with comparable records from your own approved branch population. Define platforms, dates and review types, preserve branch-level results before aggregating, and use the same start event and time unit. For peer studies, request selection method, participant numbers, sector mix, coverage dates and exclusions.



