Verified review

Review verification ties reviewer identity to transaction history. Amazon verifies by checking if the email account purchased the product. OpenTable verifies against reservation records. Yelp verifies against appointment data, ticket purchases, or delivery history. Google verifies through Gmail and purchase history where available, and flags reviews that come from old Google accounts tied to frequent check-ins at that location.

Verification is partial and platform-specific. Yelp shows a "Verified as a Business Customer" badge only if the system can tie the review to a transaction. Google shows a check mark for reviews on accounts with verified Gmail histories. Facebook relies on friend networks and historical activity. No platform has perfect verification, but all flag reviews lacking transaction ties as "unverified" to readers and, indirectly, to recommendation algorithms.

Readers trust verified reviews more than unverified ones. A review from an account with zero history, no profile picture, and no verified purchase is suspicious — it could be the owner, a competitor, or a fake. A review from an account with 50 other purchases, a profile picture, and a verified transaction is credible.

Search algorithms weight credibility the same way. Google's ranking algorithm and recommendation systems (including AI Overviews) prioritize verified reviews when surfacing business recommendations. A business with 200 unverified reviews rates lower than one with 50 verified reviews on the same average star rating. Verification signals that feedback comes from real customers, not vote manipulation.

Unverified reviews appear on most platforms but carry lower weight with readers and algorithms. Common reasons a review is unverified: the reviewer account has no transaction history, the email can't be tied to a purchase, or the account is new. Some reviews are unverified simply because the platform doesn't have transaction data (Google reviews from people who checked in but didn't transact).

Platforms show unverified status differently. Yelp explicitly badges verified vs unverified. Google flags accounts with weak history. OpenTable and Resy only show verification if the reservation is confirmed. Facebook doesn't badge unverified but deprioritizes them in recommendations. Accumulated unverified reviews hurt credibility more than they help — which is why some services sell fake reviews, and why fake reviews eventually tank businesses when platforms catch the pattern.

Verified reviews come naturally when you drive customers through trackable channels. If customers book via Resy or OpenTable, their reviews are automatically verifiable. If they buy via Amazon, verification is automatic. If they schedule via Acuity or Calendly, appointment-based verification works.

For service businesses without obvious transaction trails (consultants, contractors, one-off appointments), verified reviews come from Yelp and Google when the business sends appointment reminders that customers click through, or from transactional emails (receipt, confirmation) that the platform can tie to the review account. The pattern is simple: capture email at booking, transaction, or service delivery — and that email becomes the anchor for verification downstream.

Monitoring verification rates across platforms used to require manual audits. Now, agents run the Multi-Platform Reviews API to fetch review metadata including verification status, flags for each platform, and sentiment. An agent connected to this data can compute a cross-platform verification ratio, flag accounts with suspicious activity (many unverified reviews in a short window), and route detected fake-review patterns to moderation.

Verification monitoring is moving from quarterly business-health audits to continuous automated detection, feeding into reputation dashboards that surface verification status, account quality, and recommendation weight alongside review count and star rating.