Fake Reviews: Why They Exist and What Can Be Done
Fake reviews are a structural challenge in systems where publication doesn't require proof of transaction. When anyone can write a review about any business without evidence of a transaction, the cost of fabrication is near zero and the incentive is enormous.
The structural problem
The economics are straightforward. A positive review can increase revenue by 5–9% for a local business (Luca, 2016, Harvard Business School). A negative review can drive away customers for months. When the barrier to publishing is nothing more than an email address, and the financial impact is measured in thousands of dollars, fake reviews become an economically rational strategy. This is not a moral failing — it is a structural one.
What the data shows
The scale is documented. Major platforms report removing millions of fraudulent reviews annually. The FTC has issued enforcement actions and updated guidelines specifically targeting fake reviews (2023). Academic research estimates that between 10% and 40% of online reviews may be inauthentic, depending on the platform and methodology used. The range is wide because detection is inherently difficult — the best fake reviews are indistinguishable from real ones without transaction data.
Sources: FTC enforcement actions, Trustpilot Transparency Reports, academic research on review platform economics.
Feature comparison
Based on publicly available platform documentation and independent research. Nuance matters — see notes in each cell.
| Feature | VeriBureau | Trustpilot | Google Reviews |
|---|---|---|---|
| Proof of transaction required | Yes — cryptographic | No | No |
| Reviews tied to real transactions | Always | Optional (invite only) | Never |
| Business can edit reviews | Impossible | Can flag for removal | Can flag for removal |
| Business can delete reviews | Impossible | Via dispute process | Limited |
| Reviewer reputation system | Protocol-wide, weighted | None | None |
| Cryptographic audit chain | SHA-256 + Merkle tree | No | No |
| Independent verification | Anyone, without account | No | No |
| Industry-calibrated scoring | Yes | No | No |
| Pricing model | Free (founding period) | Freemium + paid features | Free (within Google ecosystem) |
| Revenue from reviewed businesses | Future: per-token | Yes — advertising + premium | No (ad revenue elsewhere) |
| REST API | Full, documented | Partial, paid | Limited |
This comparison reflects publicly documented features as of early 2026. Platform capabilities may change. We aim for accuracy, not advocacy.
The VeriBureau approach
There are two fundamentally different approaches to this problem. The first is detection: publish all reviews, then use AI, human moderators, and user reporting to identify and remove fakes after the fact. This is the dominant approach today. The second is prevention: require proof of a real transaction before a review can be published. This is the approach VeriBureau takes. A Proof Token — a cryptographic link between a business transaction and a review — must exist before any review enters the system. This does not eliminate all possible manipulation, but it raises the cost of fabrication by orders of magnitude.
Limitations and honest disclosure
No system eliminates fake reviews entirely. VeriBureau’s Proof Token is generated by the business, which means a business could theoretically create tokens for fictitious transactions. We mitigate this through pattern analysis, reviewer independence checks, and the public audit chain. We are transparent about this limitation because honesty about boundaries is more valuable than false claims of perfection.
Frequently asked
Is VeriBureau free?
Yes. During the founding period, all features are free with no limits. Future pricing will be per-token, not subscription — announced with advance notice.
Is VeriBureau immune to fake reviews?
No system is immune. VeriBureau raises the cost of fake reviews significantly by requiring cryptographic proof of transaction, but a business could theoretically generate tokens for fictitious transactions. We mitigate this through pattern analysis and the public audit chain, and we are transparent about this limitation.
How long does integration take?
Dashboard registration takes 2 minutes. API integration depends on your stack — most developers complete it in under an hour. No-code options (email invitations, QR codes) work immediately.
Form your own view
Examine how the Proof Token system works. Verify the audit chain yourself.