TL;DR
The fastest legal way to get more Google reviews for a restaurant in 2026: create your direct review link, put it behind a QR code on the bill and the table, train staff on a ten-word verbal ask, and send it to every guest, with no sentiment filter. Restaurants that run this consistently land in the 8–15% response band — for a restaurant serving 1,200 covers a month, that's 15–40 new reviews without a single euro spent on tooling. What you must NOT do in the EU: filter unhappy guests away from the link (review gating), pay or discount for reviews without disclosure, or buy reviews — all three are now enforced consumer-law violations, not just Google policy breaches. August and September are the highest-leverage months of the year to start: peak-season guest volume converts into the fresh-review velocity that decides your autumn Maps ranking.
Why peak season is the highest-leverage window
Google's local ranking discounts review age aggressively — reviews from the last 90 days carry most of the review-signal weight (the full math is in Review Velocity Now Beats Review Count). That has a seasonal consequence most restaurant owners miss:
The reviews you collect in August are the ranking you have in October.
A seaside restaurant in Valencia or the Algarve serves 3–5x its normal covers in August. Every one of those guests is a potential review — and tourist guests are more likely to review than regulars, because reviewing is part of how travellers process a trip. If your collection system is live during the wave, you bank 60–90 days of ranking signal. If it isn't, the wave passes and your profile looks exactly like it did in May — while the competitor across the street enters autumn with 40 fresh reviews.
The window works everywhere the season peaks: coastal Spain and Portugal in August, Paris and Prague through the summer tourist flow, London year-round with an August spike.
Step 0: your direct review link (two minutes, do it today)
Everything below depends on one URL: the link that opens the Google review form directly, with the stars ready to tap — not your Business Profile, not Google Maps, not a search result.
- Open your Google Business Profile dashboard (or search your business name on Google while logged in as the owner).
- Find "Ask for reviews" — Google gives you a short link of the form
g.page/r/…/review. - Test it in an incognito window on a phone. It must open the review form in one tap.
Every extra tap between the guest and the star row costs you roughly half your conversions. A guest who has to find your restaurant on Maps, scroll past photos, and locate the review button mostly gives up.
The seven collection systems, ranked by conversion per effort
| # | System | Typical response rate | Effort | Cost |
|---|---|---|---|---|
| 1 | QR code on the bill folder / receipt | 5–10% of covers | One print run | ~€0 |
| 2 | Staff verbal ask + QR on the table | 10–20% when asked personally | Training, ongoing | €0 |
| 3 | Post-visit SMS or email (reservation systems) | 8–15% of messages | Setup once | SMS fees |
| 4 | QR tent card / sticker at the exit and till | 2–5% of covers | One print run | ~€0 |
| 5 | Wi-Fi portal follow-up page | 3–6% of logins | Setup once | €0 |
| 6 | Response loop (reply to every review) | Indirect — lifts all other rates | 15 min/day or AI | €0–low |
| 7 | Delivery-bag insert card with QR | 1–3% of orders | One print run | ~€0 |
Three notes that separate restaurants that get results from restaurants that print a QR code and wait:
The verbal ask is the multiplier, not an alternative. A QR code alone converts a few percent. The same QR code after the server says one sentence converts several times better. The script that works is short, personal, and conditional on nothing: "If you have thirty seconds, a Google review really helps a small place like ours — the code's on the bill." No "if you enjoyed it" (that drifts into gating territory), no begging, no star-count mention — asking for "a 5-star review" violates Google's policy; asking for a review doesn't.
The bill is the moment. The guest is seated, phone in hand, experience complete, waiting for the card terminal anyway. Every other placement (door, till, bag) catches guests in motion. That's why system #1 and #2 top the table: they intercept the one idle minute of the visit.
SMS and email have a legal precondition in the EU. You can only message guests who gave you their number or email with a lawful basis — a reservation platform opt-in, a loyalty signup, an explicit consent checkbox. Germany is the strictest (opt-in effectively mandatory under UWG §7); Spain, France and most of the EU allow a "soft opt-in" for existing customers with an easy opt-out. If you're not sure what you have consent for, lead with QR + verbal ask — they need no personal data at all.
What is illegal in the EU in 2026 (not just "against policy")
Since the EU Omnibus Directive (2019/2161) was transposed into national consumer law, three common review tactics moved from "Google might penalize this" to "a consumer-protection authority can fine you." We covered the enforcement wave in detail in Fake Reviews Are Now a Legal Liability in the EU — the restaurant-relevant summary:
1. Review gating. Asking "how was your visit?" first and showing the Google link only to happy guests is a misleading commercial practice — it manufactures a rating that doesn't reflect real customer experience. It's also explicitly against Google's own rules ("don't discourage or prohibit negative reviews, don't selectively solicit positive ones"). If your review tool has a sentiment pre-screen, turn it off.
2. Undisclosed incentives. "Free dessert for a review" without disclosure is an unfair practice under the amended UCPD — and Google prohibits incentivized reviews even with disclosure. There is no compliant version of paying for Google reviews. Spend the dessert budget on service recovery instead.
3. Bought or fake reviews. Submitting or commissioning fake reviews is banned outright, with fines that national authorities have actually started issuing. If an agency offers you "20 guaranteed 5-star reviews," they are selling you a legal liability with your name on it.
The good news: the compliant playbook above outperforms the banned one anyway. Honest 4.6 with fresh velocity beats engineered 4.9 with a suspension risk.
The tourist multiplier: reviews in six languages are an asset
Peak-season reviews arrive in the guests' languages — German, French, Dutch, Polish, English. Owners sometimes treat this as a nuisance. It's the opposite:
- Multilingual reviews rank you for multilingual searches. A German review mentioning "Paella" helps you appear when German tourists search from their hotel.
- Responses in the reviewer's language double as marketing copy. The next German guest reads that exchange and sees a place that will understand them.
- Response speed still matters more than response polish. A same-day reply in decent German beats a perfect one next week — the 5-minute response rule applies in every language.
Practically: either block 15 minutes a day and use a translator, or use an AI response tool that detects the review language automatically (our free generator handles 16 languages). Whichever you choose, respond to every review during the season — including a short, professional reply to negative ones (templates here). Guests decide where to eat by reading how you handle the 1-star, not by counting the 5-stars.
The velocity math for a restaurant
Target: 5–8 new reviews per month minimum, forever — that's the floor at which Google treats a profile as active. Peak-season target for a restaurant that wants to move up the local pack: 3–5 per week.
Worked example, 1,200 covers/month:
- Ask 60% of tables verbally + QR on every bill → ~900 asks
- 8–15% response band → 70–135 reviews per month in theory
- Reality with imperfect execution: divide by 3 → 25–45 reviews per month
Even the pessimistic bottom of that range is 5x the velocity floor and more than most competitors collect in a quarter. The constraint is never guest supply — it's whether the ask happens at every table, every shift, including the Saturday rush.
The 30-day peak-season plan
Week 1 — infrastructure. Get the direct link. Print QR codes (bill folders first, tent cards second). Put the review link in your reservation-confirmation template if you have a lawful basis to message.
Week 2 — staff. One pre-shift briefing: the ten-word script, when to say it (with the bill), and what never to say (no star counts, no filtering, no incentives). Make it a standard step of closing a table, like offering dessert.
Week 3 — response loop. Reply to every new review within 24 hours, in the reviewer's language. Clear the backlog of unanswered reviews from the last 90 days — Google shows response behaviour prominently, and unanswered negatives suppress conversion of every guest who reads them.
Week 4 — measure and fix. Count the month's new reviews. Under 10? The verbal ask isn't happening — observe a dinner shift and find out why. Getting reviews but all in one language? Your tourist guests aren't being asked. Getting 1-star responses faster than you can react? Set up alerting so the reply happens the same day.
Then keep running it. Velocity is a permanent operating habit, not a campaign.
FAQ
Can I ask every guest, even ones who complained? Yes — and legally you should treat all guests the same. A complaint handled well before the guest leaves often becomes the most credible positive review on your profile. What you can't do is route unhappy guests away from the public link.
Can I offer a discount for leaving a review? No. Google prohibits incentivized reviews entirely, and undisclosed incentives violate EU consumer law. This applies to free desserts, loyalty points, and Wi-Fi passwords conditional on a review.
Do Google reviews from tourists in other languages count the same? Yes. Rating, recency and text quality count regardless of language — and they additionally help you surface in searches made in those languages.
How fast will more reviews improve my ranking? Review signals feed into local ranking on a rolling basis; a sustained velocity change typically becomes visible in Maps positions within 4–8 weeks. That's exactly why the August wave decides the autumn ranking.
Is it worth paying a platform just to collect reviews? Not just to collect — a QR code is free. Platforms earn their fee on the parts that consume owner time: monitoring every new review across platforms, responding in the guest's language, and alerting you to negatives fast. If that's the bottleneck, a restaurant review-management tool starts at a fraction of what enterprise suites charge.
The restaurants winning local search in 2026 aren't the ones with the oldest profile or the cleverest tooling. They're the ones where asking for a review is as routine as offering dessert — every table, every shift, every language, all season long.
New blog posts. No spam.
Get the next reputation playbook delivered when it drops.
