Resources · 85

Customer reviews: provenance, moderation and consistent ratings

Explain verified-review labels and keep moderation fair from submission to structured data.

· 3 min

Product checking with a parcel, an item card and printed feedback Illustration · fictional scene

What this guide helps achieve

  • Define what verification means
  • Link reviews to the right item
  • Moderate against explicit reasons
  • Recalculate displayed ratings
  • Investigate without premature conclusions

Quick check

  • Should a negative review be removed?
  • Can variants share reviews?
  • Does automated detection prove a fake review?

Step-by-step method

  1. 01

    Define what verification means

    Distinguish a linked purchase, declared use and an unrestricted submission. In France, claiming reviews come from purchasers or users requires checking measures; ministry guidance also covers transparency about dates, ordering, incentives and moderation. Describe what your checks actually establish without claiming absolute assurance.

    Deliverable: provenance labels and applicable rules.

  2. 02

    Link reviews to the right item

    Retain a stable product or service identifier. Explain whether reviews are shared across variants and why. During migration, check origin, experience date and publication date; do not present imported reviews as locally collected.

    Deliverable: review-to-item and origin mapping.

  3. 03

    Moderate against explicit reasons

    Separate negative opinion, abusive content, personal information and off-topic submissions. Apply the same rules regardless of rating. Retain rejection reason, decision, date and available appeal. A generated summary must not become a new review attributed to a customer.

    Deliverable: moderation rules and decision register.

  4. 04

    Recalculate displayed ratings

    Define scale, included population, rounding and withdrawn-review handling. Reconcile counts, visible averages and structured data for the same item. Follow Review snippet requirements; correct markup does not guarantee a rich result.

    Deliverable: reproducible calculation and markup check.

  5. 05

    Investigate without premature conclusions

    Grouped submissions, similar wording or rating shifts may warrant investigation; alone they do not prove fraud. Examine campaign invitations or genuine incidents before deleting content. Let readers access ordering and verification rules.

    Deliverable: signal-investigation procedure.

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
OriginCollection channel, item, experience and publication dates
VerificationCheck performed and exact meaning of the verified label
ModerationRule, reason, decision and appeal route
AggregateIncluded population, count, average, rounding and markup

Worked example

Illustrative situation

Fictional example: a store combines two colors and a new technical product version under one rating.

Decision and expected evidence

It retains color-level sharing where relevant but separates the technical version and identifies imported review origins.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
Linked purchaseConnect a review to a transactionDoes not prove every statement is accurate
ModerationApply publication rulesMust not select only favorable opinions
Average ratingSummarize a review populationConceals spread, age and exclusions

Management indicators

IndicatorWhat it measuresFirst action
Rating consistencyMatching interface and structured-data aggregatesCorrect item or calculation population
Justified decisionsRejections linked to explicit rulesReconsider decisions lacking a reason
Traceable importsReviews retaining origins and datesRelabel unsupported verification claims

Common pitfalls

  • Does not prove every statement is accurate
  • Must not select only favorable opinions
  • Conceals spread, age and exclusions

Frequently asked questions

Should a negative review be removed?

Its rating alone is insufficient. Examine publication rules and handle the complaint without manufacturing an impression of universal satisfaction.

Can variants share reviews?

Define the scope and inform readers. A different characteristic may make a review less relevant to another variant.

Does automated detection prove a fake review?

No. Use signals for documented review with a route to correct mistaken decisions.

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.