The review does not need to be fake for this to be a violation. The routing itself is the
Review gating is asking a customer how their visit went first, then routing the answer based on what they said: a happy customer gets sent straight to Google, and an unhappy one gets sent to a private form instead, or nowhere at all. It is common enough that plenty of feedback software still ships with this as a built-in feature, sold as a way to "protect your rating" rather than as a rule that carries any legal exposure.
The name describes the mechanism, not the intent. A business running this setup is usually not trying to publish fake praise; it is trying to avoid a bad rating showing up in public, one customer at a time, by never letting the unhappy answer reach Google in the first place.
Banned, under Google's own policy for how a business may request reviews. Google's rule specifically targets selecting who gets asked for a review based on how satisfied they appear to be, which is precisely what a satisfaction-gate does.
No. Every review that makes it through a satisfaction gate can be completely honest, written by a real customer, describing a real visit, and the practice is still banned. The rule is about the selection mechanism, choosing who gets asked based on their answer, not about whether any individual review is fake.
Because the question is the gate. The moment a form asks a customer to rate their experience and then decides, based on that rating, whether to show them the "leave a Google review" button or a different, private path, the business has selected who gets asked based on how satisfied they look. It does not matter that the question itself sounds neutral; the branching after it is what the rule targets.
No, they are separate. A fake review is content that misrepresents a customer's experience. Review gating is a routing practice that can operate on entirely genuine reviews. Federal regulation now addresses both, but as two distinct kinds of violation, which is why a business can be doing everything honestly at the review level and still be violating the rule at the routing level.
This distinction matters for anyone reading advice online that only talks about fake reviews. Advice that says "just make sure the reviews are real" misses this rule entirely, because the reviews being real was never the problem the rule is aimed at.
Yes. A form that asks for one to five stars first, then only forwards four and five star answers to the public review link while routing one to three star answers to an internal contact form, is the textbook version of this practice. The star question and the routing decision together are what makes it gating, not either piece alone.
No. Offering a customer a private way to complain is not the violation, and it is a genuinely useful option for a business to have. A complaint that reaches the owner directly, before it ever becomes a public review, can save a relationship a public back-and-forth cannot. The violation is deciding who sees that option, and who sees the public review option, based on how the customer already answered a satisfaction question. Offer both, to everyone, without the gate in front of them, and the private option is fine.
Asking every guest the identical way, with a Google review option and a private message option presented together, and letting the guest decide which one to use, with no branching logic based on any answer collected first. Nothing about the invitation may depend on how the visit is predicted to have gone.
By never asking the gating question at all. A card that presents a Google review and a private message to the owner, side by side, the moment it is tapped, has nothing to route, because there is no satisfaction question upstream deciding which option to show. Every guest who taps it sees the identical choice.
Federal rules on reviews and testimonials treat review gating as its own violation, carrying its own civil penalty exposure, separate from any penalty for a fake review itself. A feedback tool built around a satisfaction filter puts the business using it inside that exposure even if every review the tool produces is completely genuine, and it does not matter that the business bought the software rather than building the filter itself; the exposure sits with whoever is running the gate in front of customers, not with whoever wrote the code behind it, and switching vendors does not clear it if the new tool still asks the same satisfaction question first.
Turn off the branching. If the feedback tool asks a satisfaction question before deciding where to send someone, that step needs to go, not just the wording of the invitation after it. Switching the wording on the button while leaving the routing logic in place does not fix anything, because the violation lives in the decision the software makes after the question, not in what the button says.
Valtela runs $599 a year and is built with no satisfaction question anywhere in the guest flow; the full pricing is on pricing.
The discount and incentive side of review rules, including why a discount for a review is banned outright, is on discount for a review. The employee and owner side, including what happens if an insider account gets caught, is on reviews from employees. And the complete rundown of Google's own review policy, with a source for every rule, is on Google's review policy.
Every citation on this page comes from one of these pages. The link goes to the original source, not to our summary of it.
$599a year, plus $79 for each extra card. See the full price.