| Practice | Status | Penalty |
|---|---|---|
| Review gating (filter by sentiment) | Banned (2018) | $51K FTC fine per violation |
| Ask happy customers only | Banned | Review removal + listing penalty |
| Pre-screen with NPS survey | Gray area | Risk of FTC action |
| Ask all customers equally | Compliant | None |
| Respond to all reviews with AI | Compliant | None |
A restaurant asks you to rate your experience on a screen after payment. You tap 5 stars. A Google review link appears. Your friend taps 3 stars. They get a private feedback form. Same restaurant, same moment — two completely different paths.
That's review gating. And it's one of the most common review collection mistakes in hospitality. It feels harmless — even logical. Why send unhappy guests to Google when you could handle their complaint privately? The problem: Google explicitly banned this in 2018. The FTC made it a fineable offense in October 2024. And yet, restaurants and review platforms still do it every day — sometimes without realizing it. This article breaks down what review gating is, why it's banned, how Google detects it, what happens when you're caught, and what to do instead.
What is review gating?
Review gating is the practice of pre-screening customer satisfaction before deciding who gets directed to leave a public Google review. Happy customers get sent to Google. Unhappy customers get redirected to a private feedback form, an internal survey, or simply nothing at all.
How review gating typically works
Customer scans a QR code, taps an NFC card, or receives a post-visit email
They're asked to rate their experience internally (1-5 stars, thumbs up/down, or a satisfaction question)
If positive (4-5 stars): they see a Google review link and are encouraged to post publicly
If negative (1-3 stars): they're redirected to a private feedback form — the Google link never appears
Review gating in the wild: why it's so common
Here's why review gating persists: it's often built directly into the post-payment flow. A guest pays via QR at the table. Right after payment, a satisfaction screen appears inside the same flow. The guest rates their experience. If they tap 5 stars, they're directed to Google. If they rate lower, the feedback stays internal.
The business sees a high volume of positive Google reviews and assumes everything is working. But what's actually happening is selective solicitation — only satisfied customers are being directed to Google. That's the definition of review gating, regardless of how polished the UX looks.
This pattern is common in QR-payment systems, post-visit email flows, and tablet-based feedback kiosks. The technology varies. The policy violation is the same.
Why is review gating banned by Google?
"Don't discourage or prohibit negative reviews or selectively solicit positive reviews from customers."
— Google Maps User Contributed Content Policy
Google banned review gating in April 2018 with a specific update to their content guidelines. The reason: review gating creates a misleading picture of a business. When only positive experiences reach Google, potential customers can't make informed decisions.
It violates selective solicitation rules
Directing only satisfied customers to Google is the definition of selectively soliciting positive reviews. It doesn't matter if you also collect negative feedback internally — if the Google link only appears for happy customers, you're gating.
It misrepresents actual customer experience
A restaurant with a 4.9 rating but a 30% internal complaint rate is misleading potential guests. Google's review system is designed to reflect reality, not a curated version of it.
It erodes trust across the entire ecosystem
When consumers can't trust Google reviews, they stop relying on them for decisions. That hurts every business — including restaurants collecting reviews honestly. And for restaurants in particular, this matters: a 0.1 difference in Google rating can measurably impact revenue.
Review gating and FTC regulations (2024 update)
In October 2024, the FTC finalized a rule that goes beyond Google's platform policy. The rule bans the suppression of negative reviews and the selective solicitation of positive ones. Penalties: up to $51,744 per violation.
Suppressing negative reviews is now a federal violation
The FTC explicitly prohibits businesses from hiding, blocking, or failing to publish negative reviews. If your system routes negative feedback away from public platforms, that qualifies.
Conditioning incentives on positive sentiment is illegal
Offering rewards, discounts, or benefits specifically for positive reviews — or only to customers who express satisfaction — violates both FTC rules and Google's own incentivized review policy.
The Fashion Nova precedent: $4.2M fine
Fashion Nova was fined $4.2 million by the FTC for blocking reviews below 4 stars from appearing on their website. Not a slap on the wrist — a multimillion-dollar enforcement action. The case proved the FTC is serious about review suppression.
Review gating examples: what counts as gating
Post-payment satisfaction screen: 5 stars opens Google, anything lower opens a feedback form
Classic gating. The path to Google is conditional on the rating. This is exactly what Google and the FTC prohibit.
Email survey with branching: "How was your visit?" Happy → Google link. Unhappy → "Sorry to hear, tell us more" (private form)
The branching logic is the gate. The review link only reaches customers who reported satisfaction.
NPS survey first, Google review link only sent to promoters (9-10 score)
Using NPS as a filter for who gets the review request. Even though you're collecting feedback from everyone, only promoters are solicited for public reviews.
Staff instructed to hand Google review cards only to tables that seem happy
Manual gating. The selectivity happens through human judgment instead of software, but the policy violation is identical.
QR code on receipt asks "Would you recommend us?" — Yes leads to Google, No leads to a complaint form
A recommendation question used as a filter before showing the review link. Same structure, different wording.
How Google detects review gating
Unnatural rating distribution
Real businesses have a mix of ratings. A restaurant with 500 reviews and a 4.95 average triggers algorithmic suspicion. Natural distribution includes 1, 2, and 3-star reviews — their absence is a signal.
Review velocity shifts
If a business suddenly goes from receiving mixed ratings to almost exclusively 5-star reviews — especially after adopting a new review tool — Google notices the pattern change.
Competitor and customer reports
Google's "Report a policy violation" tool lets anyone flag suspicious review practices. Competitors watch each other closely. One report can trigger an audit of your entire review history.
AI pattern analysis
Google's machine learning models are trained on millions of review profiles. They recognize what authentic review distribution looks like — and what manipulated profiles look like. Since 2023, these detection systems have improved significantly.
What happens when Google catches review gating
Why ReviewTactic flags review gating patterns
ReviewTactic was built with compliance at its core. The platform monitors your review collection patterns and alerts you if anything resembles gating — even if it's unintentional.
ReviewTactic analyzes your review distribution in real time. If the system detects an unusually high concentration of 5-star reviews or a suspicious absence of mixed ratings, it flags the pattern before Google does.
Every review prompt sent through ReviewTactic goes to every customer equally. No satisfaction filter. No branching logic. No gate. The review request is the same regardless of the customer's private feedback.
Instead of preventing negative reviews from appearing, ReviewTactic helps you respond to them professionally within hours. A thoughtful reply to a 2-star review builds more trust than a suspiciously perfect 5.0 rating.
Restaurants using ReviewTactic see review rates increase without any gating. The combination of equal prompting and fast professional responses creates authentic profiles that rank better in local search.
Review gating vs compliant review collection
In gating, the system decides who sees the Google link. In compliant collection, every guest sees the same prompt. That's the entire structural difference — and it's the one that determines whether you're compliant or violating policy.
What to do instead of review gating
The simplest compliant approach. Every guest who interacts with your system sees the same Google review link. No pre-screening, no branching logic, no satisfaction filter. This is what Google requires: unbiased solicitation.
A spin wheel, scratch card, or instant reward puts guests in a good mood. People who just won something are more likely to leave a review — and more likely to leave a positive one. You don't need to gate when the experience itself creates goodwill.
You can still collect private feedback — just don't use it as a filter for who sees the Google link. Collect feedback on one channel, prompt reviews on another. Keep the two flows independent.
Instead of preventing negative reviews, respond to them publicly. A thoughtful reply to a 2-star review builds more trust than a suspiciously perfect 5.0. Consumers know perfection isn't real — a mix of ratings with professional responses signals authenticity.
If you're worried about negative reviews, the problem isn't your review collection method. It's the experience causing the complaints. Fix the root issue — service speed, food consistency, wait times — and positive reviews follow naturally.