A diner reading reviews is doing two things at once: judging your food and judging your character. The food rating is visible in the stars. The character rating is visible in the responses.
What you'll be able to do by the end
- Write a 3-template review-response system (good / mixed / bad).
- Identify 10 regulars you'll personally ask for first-week reviews.
- Set up the L16 recurring 'reviews triage' cadence (bi-weekly, 10 min).
Plain language version — the fast read
Write three short reply templates: one for good reviews, one for mixed reviews, one for bad reviews. Pick ten regulars you'll personally ask to leave a review the first week. Reviews compound — start now.
Why the first ten matter so much
Google ranks GBPs partly by review velocity — new reviews coming in regularly signal an active business. The first ten reviews establish your baseline; everything after compounds. A restaurant with three reviews and a 5-star average is invisible. A restaurant with twelve reviews and a 4.3-star average is the one diners actually choose, because twelve reviews with thoughtful responses tell a clearer story than three perfect-but-mysterious stars.
The lesson here isn't to chase stars. It's to ship a system that converts the first month of diners into reviewers, and a response habit that turns even bad reviews into trust signals.
How to ask — without sounding like a chain restaurant
The standard "Please leave us a review on Google!" sign at the host stand gets ignored. Three things work better, in this order.
- Ask one specific person, on the way out. "If you had a good time tonight, would you mind leaving us a review? It really helps us." Specific, asked once, after the meal. Not on a sign — by a host or server who watched you eat.
- QR code on the check, not on the table. The check is the moment of decision; the table is the moment of food. A QR linking directly to your GBP review form (not your generic GBP page) means one tap and three sentences instead of six taps.
- Email follow-up only if you already have email. If you take reservations through OpenTable or Tock, you have their email. A simple "Thanks for coming, here's the review link" sent the morning after works — but only sent once, no resend, no nudge.
What doesn't work: incentives (offering a free dessert for a review violates Google's terms and gets you suspended), every-table table tents (diners ignore them), automated text messages (the wrong tone for restaurants).
The response template — drafted before the first review lands
You will get a bad review in your first month. Probably in your first week. The diner will be wrong about something, or right about something you can't easily fix, or just having a bad night. The response you write matters more than the review itself, because that response is what every future diner will read when judging your character.
Three response styles to a hypothetical "Food was OK but service was slow, took 45 minutes for our entrees" review. Read all three before drafting yours.
The three-part structure works for almost any bad review: name the failure, own it, offer a specific repair. Write your version below — using your own voice, your own name, your own neighborhood. You'll edit it for each real review, but having the shape ready means you respond within 24 hours instead of letting it sit for a week while you stew.
Respond within 24 hours. Google's response timing is itself a ranking signal — fast responses indicate an active business. More important: a 24-hour response to a bad review reads as care; a one-week response reads as panic.
First-week trust signals on the home page
Until you have ten reviews to display, the home page needs other trust signals. The L14 generator includes three by default, all of which require zero work from you because they already live in your context:
- Your name and address visible in the footer. A real address, not a P.O. box, signals "real restaurant" to diners and crawlers both. (From Lesson 1.)
- Your phone number, tappable on mobile. A phone someone answers is the strongest trust signal there is. (From Lesson 10.)
- Your hours, on every page. Stale hours = no one minding the shop. Current hours = open for business. (From Lesson 10.)
Once you have your first three reviews on GBP, the generator can pull them into a "What people say" section on the home page. Until then, the absence is fine — diners reading a new restaurant's site don't expect 100 reviews, but they do expect to feel that someone is home.
What this changes downstream
Lesson 14 (the generator) reads your response template and saves it as a context field — when you set up your GBP responses workflow, you reach for it. Lesson 16 (rhythm) folds review-response into the bi-weekly cadence, alongside GBP posts and hours checks. The generator's first-week-trust footer ships automatically once your name + phone + hours are present.
You have a response ready before you need it.
A drafted response template using the name-own-repair structure, saved in your browser. The first bad review is 24 hours away from a thoughtful response, not a week of stewing. The first-week trust signals (name, phone, hours) ship automatically with the generator.
The character signal is the response, not the review. You wrote the character signal in advance.
Lesson 15 (deploy) and Lesson 16 (rhythm) follow in upcoming releases.