Review Gating: What Google Actually Prohibits (and What's Still Allowed)

Review gating — screening customers by sentiment and sending only the happy ones to Google — violates Google's review policies and now carries FTC exposure. Here's where the line actually sits, which common request flows cross it, and how to run a compliant program that still grows your rating.

Review gating is the most widely deployed compliance violation in local marketing. It ships as a default feature in review software, it gets recommended in agency playbooks, and most business owners running a gated flow have no idea they are doing anything Google prohibits. The practice feels reasonable — check whether the customer is happy before pointing them at your public profile — which is exactly why it spread. But Google’s review policies prohibit it, the FTC addressed the broader practice of review suppression in a 2024 rule that carries civil penalty authority, and the gated profiles themselves tend to underperform honest ones with buyers. This guide draws the actual line: what gating is, what the policies really say, which common flows cross it, which ones don’t, and how to run a review program that grows your rating without the exposure.

— Chris Brannan, Local SEO Consultant, Gilbert AZ

What Review Gating Is

Review gating is pre-screening customers by sentiment and routing only the satisfied ones to a public review platform. The canonical flow: after a job, the customer gets a message asking some version of “How did we do?” A thumbs-up or a high rating triggers a second message with a direct Google review link. A thumbs-down or a low rating routes the customer to a private feedback form — and the Google link never appears.

The mechanism matters more than the wording. Gating is not defined by asking a satisfaction question; it is defined by the routing — the fact that the customer’s answer determines whether they are given the opportunity to review you publicly. A business running this flow is not collecting reviews. It is collecting positive reviews and intercepting negative ones, which produces a public profile that systematically misrepresents what customers actually experienced.

That distinction — question versus routing — is the key to every gray zone in this guide, so it is worth holding onto before getting into the policy text.

What Google’s Policy Actually Prohibits

Google’s review policies — the content rules covering contributions to Maps and Business Profiles — prohibit soliciting reviews selectively and prohibit discouraging or preventing negative reviews. In plain terms: a business may not ask only the customers it expects to be positive, and may not build a process designed to keep unhappy customers away from the public review form. Google groups these practices with fake engagement and deceptive content, because the effect is the same — a rating that no longer reflects genuine customer experience.

Two things are worth being precise about. First, the policy targets the business’s conduct, not the reviews’ authenticity. Every review on a gated profile can be a real customer describing a real job, and the profile still violates policy, because the selection process is deceptive even when the individual reviews are not. This is a different problem from fabricated reviews, which have their own removal pathways covered in the fake review removal guide.

Second, the policy is enforced at the profile level, not just the review level. Google can remove reviews it associates with a prohibited practice, and profiles flagged for violations can face restrictions beyond individual removals. A business that spends two years building 200 reviews through a gated flow is carrying concentrated risk: the asset it built is the thing enforcement targets.

The FTC Made This a Federal Issue in 2024

For US businesses, the platform policy is no longer the only exposure. In 2024, the FTC finalized a rule addressing fake reviews and testimonials, and among the practices it covers is review suppression — including misrepresenting that the reviews a business displays represent all or most of the reviews it received. The rule carries civil penalty authority, which means violations can result in financial penalties, not just an order to stop.

The FTC’s endorsement guidance has also warned for years that soliciting reviews only from customers likely to be positive can be a deceptive practice, because the resulting review display misleads consumers about the range of actual experiences. Whether any individual small business becomes an enforcement target is a probability question; that the practice sits inside conduct a federal regulator has explicitly addressed, with penalty authority attached, is not. A review program is marketing infrastructure a business runs for years — building it on a practice that is prohibited by the platform and addressed by a regulator is a bad trade for a marginally higher star rating.

The Gray Zones, Handled Honestly

Most businesses are not trying to cheat. They are running flows a vendor configured, and the line between compliant and gated runs straight through the middle of standard industry practice. Here is where it actually sits.

Internal feedback surveys: allowed

A post-job survey that asks how the service went — for operational use, service recovery, technician coaching — is fine. Google’s policy does not prohibit asking customers about their experience. It prohibits using the answer to decide who gets the public review opportunity. A survey whose results feed your operations dashboard, with review requests going to everyone independently, has no gating problem at all.

Asking every customer: allowed, and better

Sending the same review request with the same Google link to every customer is fully compliant — and it is the stronger strategy on the merits, not just the safe one. Volume compounds: a business asking 100% of customers will out-accumulate a business asking a filtered 60% every month, and review velocity is one of the most heavily weighted controllable inputs in local rankings. The mechanics of timing, request copy, and velocity benchmarks are covered in the complete review generation guide — all of them work identically in an ask-everyone flow.

”How did we do?” pre-asks that route by answer: gating

This is the flow most businesses are actually running, and it is the one to be honest about. A two-step sequence where step one asks a satisfaction question and step two — the message containing the Google link — goes only to customers who answered positively is review gating. It does not matter that the question sounds like a survey, that the negative responders get a “private feedback” option, or that the software calls it something friendlier. The routing is the violation. If a customer’s answer to the pre-ask determines whether they ever see the review link, the flow selectively solicits positive reviews and suppresses negative ones, which is precisely what the policy prohibits.

This includes the widely recommended “satisfaction-first” sequence in its common configuration. The satisfaction check itself is not the problem — withholding the review link based on the response is.

Platform “feedback first” flows: configuration decides

Podium, Birdeye, NiceJob, and their competitors have all historically offered some version of a feedback-first flow, and the industry has moved — unevenly — away from hard gating as Google’s policy position became explicit. The compliant configuration exists in every major platform; whether your account uses it is a settings question worth checking today.

The compliant version looks like this: every customer receives the review request with the direct Google link, full stop. A satisfaction or feedback question may run alongside it or before it, but the review link does not depend on the answer. Some platforms implement this as a combined screen — a feedback prompt and the public review option presented together, both paths available to everyone. That passes, because no one is prevented from reviewing. What fails is any branch where a negative response terminates the flow before the review link appears. If you are evaluating these tools, the Podium vs Birdeye vs NiceJob comparison covers the platforms themselves; whichever one you run, audit the request sequence and confirm the link goes to everyone.

Why Gating Backfires Even If Nobody Catches You

Set enforcement aside entirely and gating is still a losing strategy, for three reasons that show up in the profile itself.

Uniform perfection reads as fake. Buyers have learned what real review profiles look like, and a 5.0 across 150 reviews is not it. A profile at 4.7 with a handful of critical reviews and professional owner responses signals a real business with real customers; a spotless wall of five-star ratings signals a filter. The gated profile wins the ratings comparison and loses the trust comparison — and trust is what converts.

Filtered volume grows slower. Every customer the gate diverts is a review that never existed. Month over month, the business asking everyone accumulates faster than the business asking a screened subset, and in competitive map-pack markets, that velocity difference compounds into a positional difference. Gating trades ranking fuel for cosmetic rating polish.

Handled negatives convert. A critical review answered quickly, specifically, and without defensiveness is one of the strongest conversion assets a profile can display, because prospective customers read the exchange as evidence of how the business behaves when something goes wrong. The gate suppresses exactly the content that lets you demonstrate that — and pushes the unhappy customer, whose feedback you intercepted, toward channels you do not control.

What a Compliant Review Program Looks Like

Operationally, compliance is simple, and it costs nothing that matters.

Ask everyone. Every completed job triggers a review request. No sentiment filter, no routing logic, no screened subset.

Same link, every time. One direct Google review link in every request. The link’s presence never depends on a survey answer, a rating, or a technician’s judgment about how the job went.

Keep the survey, cut the gate. If satisfaction data drives your operations, keep collecting it — in parallel, not as a checkpoint. A customer who reports a problem should trigger a service-recovery call and still have the review link. Sometimes the recovery itself becomes the review.

Respond to everything. A 100% response rate, positive and negative, within 48 hours. The response layer is where a compliant profile builds the trust advantage a gated profile can never show.

Audit your software. Open your review platform’s request sequence and trace the negative-response path. If it dead-ends before the Google link, reconfigure it. This is a fifteen-minute check that removes your largest policy exposure.

The timing frameworks, request copy, and velocity benchmarks that make this program productive are covered in the review generation guide — none of them require a gate to work.

Detection and Consequences

Google does not publish its enforcement methods, but the consequence structure is visible: reviews associated with policy violations get removed, and profiles can face restrictions beyond individual removals. Gated profiles also leave a statistical signature — near-uniform ratings, positive-only streaks at volumes where organic negative reviews are inevitable — that automated systems are well suited to flag. A business betting on gating is betting that pattern stays invisible indefinitely, while the review count it is building concentrates more value into the thing enforcement would target.

Tool-side enforcement is the second exposure. Review platforms have removed or reconfigured gating features before, under policy pressure, and a flow that is quietly reconfigured by a vendor update can strand a business’s entire request pipeline. And in the US, the FTC’s 2024 rule sits above all of it — enforcement against small local businesses may be improbable on any given day, but the rule exists, penalties attach to it, and “improbable” is not a compliance posture.

The cleanup path, if you have been gating: turn off the routing today, keep the volume you have, and let unfiltered collection normalize the profile going forward. Google’s enforcement targets the practice; a business that stops gating and asks everyone is moving in the direction every incentive now points.

Key Takeaway

Review gating is prohibited by Google’s review policies, addressed by an FTC rule with civil penalty authority, and — independent of both — a weaker growth strategy than the compliant alternative. The line is routing, not asking: satisfaction surveys are allowed, asking every customer is allowed, and any flow where a customer’s answer determines whether they see the review link is gating. The compliant program is one sentence long — ask everyone, same link, respond to everything — and it produces faster review velocity and a more credible profile than the filtered version it replaces.

If you are not sure whether your current flow gates — or how your review profile actually compares to the competitors holding your map pack — my $197 SEO audit reads your review profile the way Google and your buyers do: velocity, rating distribution, response coverage, and the patterns that signal a filtered profile, benchmarked against the businesses you are actually competing with.

FAQ

Common questions on this topic.

Is review gating illegal?

Can I ask only happy customers for reviews?

Are customer satisfaction surveys considered review gating?

Does Google detect and remove gated reviews?

What is the FTC rule on fake reviews and review suppression?

Start here

Want the next post in your inbox ?

One email a month. New writing, real engagement updates, no marketing fluff.