Most advice on how to get more Google reviews would, if followed literally, get a restaurant’s reviews stripped and a warning notice slapped on its profile. “Offer a free dessert for a five-star review” is still printed on table tents across the country, and it is a straightforward policy violation that Google now actively enforces against.
This is a guide to the version that works and stays within the rules: where the line actually sits, what you can legitimately do, and the asking points that produce reviews without pressuring anyone.
Key takeaways
- Never incentivise. Offering anything in exchange for a review is fake engagement under Google’s policy and prohibited outright.
- Never selectively solicit. Asking only the happy customers is specifically named as prohibited behaviour.
- Never set staff quotas. Requiring employees to generate a certain number of reviews is a violation.
- Don’t pressure anyone on the premises or ask for specific content in the review.
- What you can do: ask everyone, ask once, make it easy, and ask at the right moment.
- Velocity beats volume. A steady stream reads as an operating business; a burst reads as a campaign and gets filtered.
Get Free Consultation
Read more about our Restaurant Marketing Solutions!
Where the line actually sits
Worth reading the policy rather than the folklore, because most restaurants are breaking it by accident.
Google’s Maps user-generated content policy on prohibited and restricted content is specific. Under fake and misleading content, it prohibits merchants from discouraging or prohibiting negative reviews, or selectively soliciting positive reviews from customers. It states that when soliciting reviews, merchants should not require or pressure users to leave ratings or write reviews while on the premises, nor request that specific content be included. It also names merchants requesting that staff solicit a certain number of reviews as a violation.
Offering incentives — free or discounted goods or services — in exchange for reviews falls under fake engagement and is prohibited.
Four things follow from that, and they rule out most of what restaurants actually do:
No incentives. Not a free dessert, not a discount, not entry into a draw.
No filtering. You cannot ask only the people who seemed happy. “Selectively solicit positive reviews” is the exact phrase.
No staff quotas. Telling servers to bring in ten reviews a week is a violation on its face, and it also produces exactly the burst pattern that triggers filtering.
No scripting. Don’t ask people to mention a dish, a server, or a keyword. The request has to be for a review, not for particular content.
What’s allowed and what isn’t
| Tactic | Allowed? | Why |
|---|---|---|
| Asking every guest for a review | Yes | Universal asking is fine. Selective asking isn’t |
| A QR code on the receipt linking to your review page | Yes | Makes it easy without pressuring anyone |
| A follow-up email or text after a visit | Yes | Provided it’s sent to everyone and doesn’t specify sentiment |
| Signage saying “we’d appreciate your feedback on Google” | Yes | Neutral, non-pressuring, non-specific |
| “Leave us a 5-star review” | No | Requesting specific content |
| “Free dessert if you review us” | No | Incentivised review — fake engagement |
| Entry into a prize draw for reviewing | No | Still an incentive |
| Asking only guests who seemed happy | No | Selective solicitation, named explicitly |
| A tablet at the host stand for reviews before leaving | No | Pressuring users on the premises |
| Staff targets for number of reviews | No | Specifically prohibited |
| Asking guests to mention a dish or server by name | No | Requesting specific content |
| Discouraging an unhappy guest from reviewing | No | Prohibited, and also an FTC issue |
| Staff reviewing their own restaurant | No | Conflict of interest, and undisclosed insider reviews |
The compliant pattern, if you want it in one sentence: ask everyone, once, for a review — not for a good one — and make it easy to leave.
The asking points that actually work
Knowing how to get more Google reviews legitimately comes down to where in the guest experience you make the ask.
On the receipt or the check presenter
A QR code linking directly to your Google review page. Low friction, universal, no pressure. The single highest-return mechanism available, and the one most restaurants either don’t have or point at the wrong URL.
Set it up properly: use the direct review link from your Google Business Profile rather than your general listing, so the review box opens immediately rather than making someone navigate to it.
A follow-up message
An email or SMS a day or two after the visit, sent to everyone on the list rather than a selected segment. This catches people who had a good experience but weren’t thinking about their phone at the table.
Keep it short, ask for a review without specifying sentiment, and include the direct link.
Verbally, at the right moment
Staff can ask. The constraint is that it has to be universal and unpressured — not while standing over the table waiting, not only to the guests who said something nice, and not with a number attached.
The moment that works is the natural one: as the check is dropped, framed as an aside rather than a request for a favour.
At the point of a genuine compliment
If a guest says the meal was excellent, responding with “that’s really good to hear — if you’ve got a minute, a review helps us a lot” is fine. What makes it compliant is that you’d say it to everyone regardless of what they said. What makes it non-compliant is if it’s the only time you ask.
That’s a subtle distinction and it’s worth training explicitly, because the instinct to only ask happy people is strong and the policy names it directly.
Making it easy
Most reviews that don’t get written fail at friction rather than willingness.
| Friction point | Fix |
|---|---|
| Guest doesn’t know where to go | Direct review link, not your homepage or general listing |
| Too many taps on a phone | QR code straight to the review box |
| Forgot by the time they got home | Follow-up message a day later |
| Not signed into Google | Can’t fix this one — it’s why you ask everyone, since only some can act |
| Doesn’t know what to say | Don’t script it. Shorter reviews still count |
| Multiple locations, wrong profile | Location-specific QR codes. Group-level links send reviews to the wrong listing |
That last row causes real problems at multi-location groups and it’s invisible until someone notices reviews landing at the wrong address. Every location needs its own link.
Velocity, not volume
One review a day for a month beats thirty reviews on a Tuesday.
A steady stream reads to Google’s systems as an operating business. A burst reads as a campaign, and burst patterns are exactly what the filtering is built to catch — which is how restaurants end up with reviews disappearing days after a push.
Practical implication: build asking into service as a habit, not a campaign. A QR code on every check and a follow-up message on every visit produces a steady trickle indefinitely. A staff push before a big weekend produces a spike, a filter, and nothing to show for it.
It also matters for multi-location groups that reviews accrue at each site rather than concentrating at the flagship. Per-location reporting is the only way to see that; group averages hide it entirely.
Multi-location groups have a harder version of this
Everything above gets more complicated across several sites, and the failure modes are specific.
Reviews land at the wrong location. A single group-level QR code or a link on a brand-wide email sends everyone to one profile. The flagship accumulates reviews it didn’t earn and the newer sites look empty. Every location needs its own link, its own QR code, and its own follow-up segment.
Asking becomes inconsistent. One GM builds it into service, another forgets, and six months later the review counts across the group look like a map of who cared. The fix is a documented process owned at group level rather than left to each site.
Quotas creep in. When a group starts comparing locations on review count, the pressure to hit a number lands on staff — which is exactly the prohibited behaviour. Compare velocity and response rate instead, and never set per-person targets.
Reporting hides the problem. A group average of 4.4 can be four strong sites and one at 3.8. Report per location with a roll-up on top, never the other way round.
One further point for groups: a brand-new location starts with no reviews and competes against established ones in the same local results. That gap closes with time and a working process, not with a push — and a push at a new location is the single most likely thing to trigger filtering, because a burst at a profile with no history is the clearest possible signal.
What to do about the reviews you already have
Getting more is half of it. The other half is response, and response rate is visible to everyone scrolling your profile.
Respond to everything within 48 hours, positive and negative. Never argue the facts publicly. Take the substance offline to a named person. Our guide to restaurant review response covers the structure, templates for the situations that recur, and the FTC rule that governs review generation in the US — which sits alongside Google’s policy and applies independently of it.
Reviews also feed local ranking. Count, velocity and rating all sit within the prominence signals Google weighs, which is covered in our guide to ranking higher on Google Maps.
What happens if you break the rules
Worth stating plainly, because the downside isn’t theoretical.
Google removes policy-violating reviews, and when it detects a pattern it can block new reviews on a profile and display a public warning notice to users. That notice is visible to everyone considering your restaurant, and it’s considerably worse for your reputation than a middling rating would have been.
The reviews you bought or incentivised disappear. The ones you earned legitimately stay. There’s no version of this where the shortcut compounds.
Build a compliant review programme that runs itself
Primi Digital runs reputation and local SEO programmes for restaurant and hospitality groups — compliant review generation, response at scale, Google Business Profile management, and per-location reporting.
If your review process was built before the current policy language, or it depends on staff remembering to ask, it’s worth auditing. We’ll tell you what’s working, what’s quietly a violation, and what a steady, policy-safe stream actually looks like for your locations. Get in touch.
Frequently asked questions
How do you get more Google reviews for a restaurant?
Ask everyone, once, with no incentive and no specified sentiment, and make it as easy as possible to act on. A QR code on the check linking to your direct Google review page, plus a follow-up message a day or two later, covers most of it. Build it into service as a habit rather than running it as a campaign.
Can restaurants offer a discount for Google reviews?
No. Offering free or discounted goods or services in exchange for a review is fake engagement under Google’s policy and prohibited. It’s also a violation of the FTC’s Consumer Review Rule in the US, which carries civil penalties per violation.
Can I ask only my happy customers for reviews?
No. Google’s policy specifically prohibits selectively soliciting positive reviews. The ask has to go to everyone regardless of how their visit appeared to go.
Can I give staff review targets?
No. Google’s policy names merchants requesting that staff solicit a certain number of reviews as a violation. It also produces burst patterns that get filtered, so it fails on practical grounds as well as policy ones.
Can I ask customers to mention a specific dish or server?
No. Requesting that specific content be included in a review is prohibited. Ask for a review, not for particular content.
Why did my reviews disappear?
Usually either a burst pattern that triggered filtering, or detected policy violations. Google removes policy-violating reviews, and where it finds a pattern it may block new reviews and display a public warning on the profile.
How many Google reviews does a restaurant need?
There’s no threshold. What matters more is velocity relative to nearby competitors, recency, response rate, and whether reviews mention the things you want to be known for — which happens naturally when you ask broadly rather than scripting.