ReviewProof ⚖

How can you prove a review is real?

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Run the free review audit See pricing · See a sample provenance report

Short answer

You prove a review is real by showing what sits behind it: a link to a transaction record, a provenance certificate that displays the source, date, transaction reference and moderation history, and a chain of custody anyone can inspect. In ReviewProof, a review with that link shows as verified; a review without one is honestly labelled UNLINKED and kept out of the verified widget.

What is a provable review?

A provable review is a review whose claim rests on a record, not on the business's say-so. The record has three parts: a transaction link (an order, invoice or booking reference the business attests or imports with the review), a certificate page that shows the reviewer, rating, source, date, transaction reference and moderation state, and a chain-of-custody timeline logging import, analysis and every moderation decision. Anything less is an assertion.

Why stars alone prove nothing

A star rating is a number a platform displays; it carries no evidence about who bought what. Profiles built on stars alone collapse the first time anyone — a platform investigator, a competitor, a careful customer — asks a basic question: which transaction does this review describe? Businesses that cannot answer tend to answer louder, with more stars. Businesses that can answer point to the record. That is the whole shift provenance asks for: from displaying opinion about your business to publishing evidence about specific, dated, transaction-backed experiences your business actually delivered.

ReviewProof computes every signal from the rows you import, never from a reputation guess about your business. The risk score is 100 × (gating × 1.0 + incentive × 1.0 + duplicate × 0.8 + AI-signal × 0.6) ÷ (2.6 × number of reviews), plus 15 points when a burst is detected, capped at 100. Each flagged review in the report names the imported row that triggered the signal, so a human can open that row, read it in context, and decide. The product labels these patterns signals for human review, not verdicts — and that restraint is deliberate, because a heuristic that overclaims would be its own kind of false evidence.

What the certificate must show — and what it must admit

A useful certificate shows the underlying record, including its gaps. ReviewProof's certificate displays the transaction reference marked as attested or imported by the business, and for transaction-backed reviews under the Phase 8 provenance system the published result masks the reference (only a SHA-256 hash and a masked form are held; the raw reference is never stored). A third party holding the reference can present it and verify the match. A review with no link publishes as exactly that — unverified. Admitting the unlinked rows is what makes the verified rows believable.

In practice the routine takes minutes. Export or copy the reviews for the location, import them into ReviewProof by CSV or paste, and read the report top-down: total rows, flagged count, risk score, then the per-signal breakdown. Open the flagged rows themselves — the report traces each signal to its row precisely so you can do this. Decide moderation openly (kept, published, or flagged internally; there is no delete), check which reviews carry a transaction link, and publish or refresh the verified widget so the public claim matches the audited record. On Pro, export the evidence pack while the file is fresh.

Mistakes that undo the work

Three mistakes undo proof faster than anything. First, treating a screenshot of a review as evidence — it shows text, not provenance. Second, quietly dropping the unlinked or negative rows before showing anyone the file, which converts an honest audit into suppression. Third, claiming every review is verified when only some carry a transaction link: one overstated claim, once noticed, discounts all the true ones beside it.

Two design choices keep the detection honest. First, nothing is scored until you import it: there is no scraping of your public profiles and no third-party score blended in. Second, the weights reflect what the FTC fake-review rule (16 CFR Part 465) actually prohibits — how a review was solicited weighs heaviest (gating and incentive markers at 1.0 each), while wording patterns weigh less (duplicates 0.8, AI-generation patterns 0.6). A burst of same-day reviews adds a flat 15 points because timing is visible in the dates you supply. You can reproduce every number in the report from your own file, which is exactly the point.

Worked example: a Belize tour operator with 86 imported reviews

A fictional worked example, written to show the numbers and the decisions in practice.

A tour operator in Belize imported 86 reviews collected over one season. ReviewProof found 61 with a transaction link to a booking reference and 25 UNLINKED. The operator published the verified-experience widget, which displayed only the 61 linked reviews that were also in a kept or published state. When a resort partner asked how the operator could stand behind its rating, the answer was a link: the partner opened three certificates, saw booking references, dates and moderation history, and checked one reference against the booking system. The 25 unlinked reviews stayed in the audit — visible, counted, and never dressed up as verified.

Your five-action checklist

  1. Import the location's reviews by CSV or paste, including transaction references where you hold them
  2. Open the report and note the split between transaction-linked and UNLINKED reviews
  3. Open a certificate for a linked review and read it as a stranger would
  4. Publish the verified-experience widget so only linked, kept or published reviews display
  5. Keep the unlinked and negative reviews in the record — never edit them away

Frequently asked questions

What makes a review verified in ReviewProof?

A link to a transaction record imported or attested with the review. Its certificate then shows a verified seal with the reference, source, date and moderation state; a review without the link is UNLINKED.

Can a business just assert its reviews are real?

It can, but the assertion is not proof. The certificate shows what the claim rests on — and, just as usefully, which reviews carry no transaction link at all.

Does a verified link mean the review text is true?

No. Verification proves the review is backed by a specific transaction in the business's records. The risk signals on the text itself remain heuristics for human review.

What happens to reviews with no transaction link?

They stay in the audit and the risk report, marked UNLINKED. They simply cannot display in the verified-experience widget, which is the honest line the product draws.

Keep reading

Related guides from the ReviewProof library:

Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.