Review gating

Review gating is the practice of asking customers to rate their experience privately first, then routing only the ones who indicate satisfaction toward a public review request while quietly steering unhappy customers away from ever reaching the review platform. It usually shows up as a two-step feedback form: a private rating question up front, and a public review link that only appears after a positive answer.

How it actually works

A typical gated flow asks "how was your experience?" with a simple scale. Anyone who answers positively gets forwarded to Google, a WhatsApp review link, or another public platform. Anyone who answers negatively gets a private feedback form instead, or nothing at all — no path to the public review page. The mechanism is simple to build, which is exactly why it spread as a growth-hack tactic among agencies and SaaS review-management tools despite being against the policies of every major review platform it targets.

Why it violates Google's policy

Google's review policy is explicit that businesses may not selectively solicit reviews based on the customer's likely sentiment, and gating is the textbook version of that violation — it doesn't ask everyone, it filters who even gets asked. The policy exists because a gated review stream is not an honest sample of customer experience; it's a curated one, engineered to show only the good outcomes while suppressing the bad ones before they ever become visible. Google treats this as review manipulation, and manipulation findings can affect a much wider set of trust signals than the specific reviews involved.

Google Reviews are meant to represent an unfiltered account of customer experience, discussed further under Google Reviews →; gating directly defeats that purpose by design, not by accident.

The consequences

Detected gating can lead to review removal, a warning, or in more serious or repeated cases contribute toward a listing suspension → if it's flagged alongside other policy issues during an automated or manual review. Beyond the direct enforcement risk, gating quietly distorts a business's own understanding of its service — a company that only sees its happy customers loses the early-warning signal genuinely poor experiences are supposed to provide, discussed further under review sentiment →. The business ends up with an inflated, unrepresentative rating and no visibility into the pattern of complaints that rating is hiding.

Review gating vs legitimate review requests

Asking every customer for a review, with no pre-filter on sentiment, is not gating — it's exactly what Google's policy expects, and it's the basis of healthy review velocity →. The distinction is whether the request path differs based on predicted sentiment. A single feedback question asked of everyone, followed by the same public review link for everyone regardless of the answer, is compliant. A feedback question that only unlocks the public link for positive answers is gating, even if the wording never explicitly discourages unhappy customers from leaving a review.

Some businesses run a private feedback survey after service, unrelated to any review request, purely to catch service issues early — that's a legitimate operational practice as long as it isn't wired to control who receives the public review invitation.

Common mistakes

The most frequent version isn't a deliberate policy violation at all — it's a review-management software tool set up by a well-meaning vendor with gating built in as a default feature, adopted by a business owner who never realised the private-first flow was against policy. A second is assuming gating is safe because it "just" asks a question before the review, without recognising that the filtering step itself, regardless of how softly worded, is what the policy targets. A third is confusing gating with reasonable timing — asking for a review a day after service rather than mid-service isn't gating, it's just sensible sequencing, and shouldn't be conflated with sentiment-based filtering.

India-specific note

Several third-party review-collection tools marketed heavily to Indian small businesses through WhatsApp-based workflows still ship gating as a default or easily-toggled setting, often described in the vendor's own marketing as a way to "protect your rating." A business adopting one of these tools off the shelf can end up gating without ever making an explicit decision to — the checklist worth running is whether every customer who's asked for feedback ends up seeing the same public review link, regardless of what they answered first.

FAQ

Is asking happy customers specifically for a review always review gating? Not necessarily. Gating specifically means filtering who gets a path to the public review request based on a prior sentiment check. Simply asking for reviews after a good interaction, without a filtering step that blocks unhappy customers from the same public link, isn't the violation itself.

Can review gating get a Google Business Profile suspended? It can contribute to enforcement action, particularly if flagged alongside other policy issues, though Google's specific escalation path from a single gating detection to a full suspension isn't publicly documented in detail.

How is review gating different from simply asking customers for feedback? A private feedback question is fine on its own. It becomes gating only when the outcome of that private question determines whether the customer is then shown the public review request.

Is there a compliant way to catch service problems before they become public reviews? Yes — running a private feedback loop that's entirely separate from the public review request, asked of everyone with no bearing on whether the review link appears, catches the same operational signal without violating policy.

Related terms: Google reviews → · Review velocity → · Review sentiment → · Review signals → · Listing suspension → · Reputation management → · Local ranking factors →

How Angryturtle handles this: GBP management services → builds review-request workflows that ask every customer the same way, with no sentiment-based filtering, keeping review collection both compliant and an honest reflection of actual service quality.