Review Gating Explained: Google's Policy and How to Stay Compliant
What review gating is, why Google penalizes it, and what to do instead.
TL;DR
Review gating means filtering customers before asking them to leave a public review, typically by only sending happy ones to Google.
Google prohibits review gating under its content policy. Reviews collected this way can be removed and repeated violations can lead to profile suspension.
Compliant review solicitation asks every customer for a review without filtering by sentiment. The result is a slightly lower average rating but a credible and durable review profile.
What is review gating?
Review gating is the practice of screening customers privately before asking them to post a public review, usually by surfacing only positive feedback to review platforms. Google's review policy explicitly prohibits this practice, and any reviews collected through a gated process are subject to removal. The compliant alternative is to ask every customer, without filtering.
The most common form of gating looks like this. A customer finishes a meal. They get a text or email asking how their experience was. If they select a smiley face or a four or five-star rating, they are sent to Google to post a review. If they select anything lower, they are sent to a private feedback form that never reaches Google.
Why Google prohibits review gating
Google's review policy states that reviews should reflect the genuine experience of the people posting them, as they happened. Systematically filtering customers by sentiment before asking for a review distorts that picture.
The penalties for violations include the removal of individual reviews identified as gated, repeated policy violation notices sent to the business profile owner, and in persistent cases, the suspension of the Google Business Profile itself.
What counts as gating and what does not
The line between gating and reasonable review solicitation is narrower than most restaurant operators realize. The table below covers common scenarios.
Scenario | Compliant? |
|---|---|
Sending every customer the same review request without filtering | Yes |
Asking happy customers to review on Google, unhappy customers to email you privately | No |
Automatically routing NPS promoters to Google and detractors to a support form | No |
Asking every customer for feedback, then giving them a choice of where to share it | Gray area. Compliant only if the choice is neutral and presented identically to all customers |
Asking staff to request reviews only from visibly happy diners | No. This is manual gating |
Running an NPS survey first, then asking every respondent to also leave a Google review | Yes, if every respondent gets the same ask regardless of NPS score |
Offering a discount for any review, positive or negative | No. Incentivizing reviews is a separate policy violation |
Common mistakes restaurants make
Even when operators know review gating is prohibited, the pattern often appears accidentally in how review software is configured.
NPS-triggered review requests: Sending customers an NPS survey first, then sending a Google review request only to promoters.
In-app star ratings that split the funnel: If the rating is 4-5 stars, asking for a Google review. If lower, opening a private feedback form.
Staff training that asks only for positive reviews: Asking only satisfied customers at the table to leave a review.
How to collect reviews compliantly
Compliant review solicitation follows a simple principle. Ask every customer, treat every response identically, and let the distribution of ratings settle where it settles. The practical implementation has three steps.
Define a review request trigger that fires for every customer (e.g., post-visit SMS).
Send the same message to every customer, linking directly to Google Business Profile.
Run separate internal feedback channels (like an NPS survey) in parallel, not as a filter.
How Sira's review workflow stays compliant
Sira's review request workflow sends a single, identical message to every customer who completed a visit or a delivery order. The message routes to Google without any sentiment filter. Sira's root cause detection module connects review sentiment back to operational data so operators can see which issues are dragging the average down and address the cause.
What to do if you have been gating and want to stop
Switch off the gating mechanism immediately. Reset the review request flow to ensure every customer gets an identical message. Expect the rating to settle in three to six months. Focus energy on the experience itself during the transition.
Warning signs your current tool is gating
The tool asks customers to rate the experience before deciding where to route them.
Public review requests are only sent to customers who scored above a threshold.
Negative feedback is sent to a private form, while positive feedback triggers a public link.
Frequently asked questions
What is the difference between review gating and review screening?
They are the same thing. Google treats it as gating if only positive customers are sent to Google.
Is it okay to ask customers for feedback before asking for a review?
Yes, as long as every customer who gives feedback also gets the same ask for a public review.
Will my average rating drop if I stop gating?
In the short term, yes. Once you stop gating, the rating will settle at its actual level (often a drop of 0.2 to 0.5 stars).