Is It Review Gating? 12 Ways of Asking for Google Reviews, Checked Against Google's Rules
Review gating means asking only satisfied customers for Google reviews, or discouraging unhappy ones from posting. Google's policy doesn't allow it.
Most review gating is accidental: a survey that only shows the Google link after a high score, or a staff target that pushes teams to ask only happy tables.
Rewards for reviews are also against Google's rules, even for honest reviews, as are staff quotas and requests for specific content.
You can still catch complaints early. Offer a private channel to everyone, and the Google link to everyone too.
Google guidance reviewed: 6 November 2026.
Few businesses set out to break Google’s rules. They set up a QR code, a thank-you message or a short survey, and only later learn that the way it was built counts as review gating. Our guide to review gating and Google’s policy explains the rule. This article takes the practical angle: 12 things businesses actually do to get reviews, and whether each one is allowed.
Google’s rule on review gating in one paragraph
Google’s content policy says businesses must not “discourage or prohibit negative reviews, or selectively solicit positive reviews from customers.” It also says businesses shouldn’t require or pressure customers to review while on the premises, shouldn’t request specific content, and shouldn’t ask staff to collect a set number of reviews or reviews with specific content. Offering any incentive in exchange for a review isn’t allowed. Asking customers for genuine reviews is fine.
The test is simple: does every customer get the same chance to post, with nothing to gain and nothing steering them toward a rating?
12 review request practices and the verdict
Practice | Verdict | Why |
|---|---|---|
QR code on the table, receipt or delivery bag that opens your Google review page | Allowed | Every customer sees it and nothing is offered |
Thank-you SMS or WhatsApp with the review link, sent to all customers | Allowed | The same message goes to everyone |
Survey first, Google link only for 4 or 5 stars | Against the policy | Only satisfied customers are invited to post |
Survey first, Google link offered to everyone after they answer | Allowed | Everyone gets the link, whatever their score |
“Happy? Review us on Google. Not happy? Tell us here.” | Risky | It steers unhappy customers away from Google |
Discount, free item or prize draw for leaving a review | Against the policy | Any incentive in exchange for a review |
Staff bonus or target based on the number of reviews | Against the policy | Google names staff review quotas directly |
Staff asking customers to mention them by name | Against the policy | It requests specific content |
A tablet or staff phone handed to customers at the counter | Risky | It can amount to pressure on the premises |
Asking only regulars or VIP customers | Against the policy | It selects customers likely to post positive reviews |
Asking employees, friends or family to review | Against the policy | It’s a conflict of interest |
Offering something to a customer who changes a negative review | Against the policy | It’s an incentive to revise or remove a review |
Below are the safe versions of the practices that cause the most trouble.
The survey-then-review flow
This is the most common form of accidental gating, and it often comes built into review request tools. The customer rates the visit, and the next screen depends on the score: four or five stars sends them to Google, three or fewer sends them to a private form.
The fix is to keep the survey and remove the fork. Show the Google option to everyone after they answer, and offer a private note to everyone too. Unhappy customers still have a direct line to the team, and you’re no longer choosing who gets to post in public. Our guide to automated feedback surveys covers the timing and triggers.
Sira’s Survey Management is built this way. After answering, every guest is invited to share on Google, and any guest can choose to tell the branch privately. A private note opens a ticket for that branch’s manager, who can reply to the guest from inside Sira.
“Tell us first” messages
Signs and messages that say “If something wasn’t right, tell us before you post a review” sit in a grey area. Inviting feedback is good. Wording that asks customers to hold off on Google, or that only puts the Google link next to the positive option, discourages negative reviews.
Safer wording gives both options the same weight: “Tell us about your visit. You can share it with our team, on Google, or both.” The same applies in Arabic. Keep the two options side by side, with the same size and prominence.
Rewards for reviews, including small ones
Across the Gulf, a free dessert, coffee or delivery in return for a review is a common promotion. Google’s policy makes no exception for small rewards, or for rewards given whatever the rating. If customers get something in exchange for posting, those reviews can be removed and the profile can be restricted. Our guide to Google review restrictions explains what that looks like.
If you run a loyalty program, keep it completely separate from Google reviews. Points, stamps and offers should never depend on posting a review or on what the review says.
Staff targets and scripts
Review counts per branch are tempting as a performance measure. Google’s policy names this practice specifically: asking staff to collect a certain number of reviews, or reviews with specific content, isn’t allowed. A target also pushes staff to ask only the tables that look happy, which turns into gating.
Measure the request instead of the result: how many receipts carried the QR code, whether the thank-you message went out, and how fast the branch responds to feedback. Sira’s AI Ticketing tracks response times per branch, which says more about service than a review count does.
How to check your current setup
Go through every place where you ask for reviews and answer three questions.
Question | If the answer is yes |
|---|---|
Does anyone see the Google link only after a good rating? | Show it to everyone |
Does anyone get anything for posting a review? | Remove the reward |
Is anyone told how many reviews to collect or what to say? | Remove the target or the script |
Check printed material in each branch, delivery bag inserts, survey tools, WhatsApp templates and anything an agency runs for you. If you find gating that has been running for a while, the review gating guide covers how to stop it safely.
Frequently asked questions
What is review gating?
Review gating is asking only satisfied customers to leave a Google review, or discouraging unhappy customers from posting one. It usually happens through a survey that only sends high scorers to Google. Google's policy doesn't allow it.
Is it review gating to send a survey before asking for a Google review?
Not on its own. It becomes gating when the Google link depends on the answer. If every customer who answers is offered the Google link, whatever their score, the survey is fine.
Can I offer a discount to customers who leave an honest review?
No. Google's policy doesn't allow payment, discounts, free goods or services in exchange for any review, honest or not and whatever the rating. Reviews posted because of a reward can be removed.
Can I ask customers to mention a staff member's name in their review?
No. Google says businesses shouldn't ask for specific content in reviews, and shouldn't ask staff to collect reviews with specific content. You can still recognize staff using feedback customers give without being asked.
Is a Google review QR code in the branch allowed?
Yes. Google suggests placing a review QR code in your store or on receipts. Keep it visible to every customer, don't offer anything for scanning it, and don't pressure people to post while they're at the counter.
Does review gating apply to delivery apps like Keeta or HungerStation?
Delivery apps collect ratings inside their own apps after an order, and each sets its own rules for businesses. Google's policy covers Google reviews. The same principle works everywhere: ask everyone, reward no one, and don't filter by how satisfied a customer seems.
