PeakKR

how to reply to Google reviews

How to Reply to Google Reviews: 15 Real Examples

The short answer: reply to every Google review within 48 hours, thank the reviewer by name, reference something specific they actually said, and keep it under 80 words. For negative reviews, acknowledge the issue, avoid arguing in public, and move the conversation to a phone number or email in one sentence.

That's the whole method. The hard part isn't knowing what to write — it's writing 60 of them a month across 14 client accounts without every reply sounding like the same chatbot. This guide covers the templates, the examples, and the workflow underneath.

Does replying to Google reviews actually do anything?

Google's own Business Profile help docs tell you to respond, which is as close to a ranking signal statement as you'll get. But the honest answer is that the direct SEO lift is unproven and probably small.

The real returns are elsewhere:

So treat replies as a conversion-rate and reputation job that happens to live inside your local SEO deliverable — not as a ranking hack.

The four-part structure of a good reply

Every effective Google review response does the same four things in order:

  1. Name — "Thanks, Marcus." Costs nothing, instantly signals a human.
  2. Specific detail — reference the service, the technician, the dish, the date. This is the part templates kill.
  3. Value or correction — one line that tells a future reader something useful about the business.
  4. Light next step — "See you at the next service," or for negatives, a contact route.

Skip step two and you've written spam. Over-do step three and you've written an ad.

A note on keywords in replies

You can work the service and city into a reply naturally — "glad the emergency drain clearing in Rochdale sorted it" — and it's fine. What's not fine is stuffing: "Thank you for choosing ABC Plumbing, the best plumber in Rochdale for boiler repair, drain cleaning, and bathroom installation." Readers notice, and it reads as desperate. One service mention per reply, maximum. If you want to know whether local visibility is actually moving, track the map pack across a grid of points rather than hoping a review reply did something.

How to reply to 5-star reviews (examples)

Review: "Dave came out same day and fixed our boiler in under an hour. Explained everything. Brilliant."

Reply: "Thanks Sarah — I'll pass this to Dave, he'll be pleased. Same-day callouts are the thing we protect hardest in the schedule, so good to hear it landed. Give us a shout if the pressure drops again over winter."

Review with no text (just 5 stars):

Reply: "Thanks for the five stars, Michael. If there's anything you'd want us to do differently next time, we're always listening."

That's the right move on empty reviews — brief, no invented details, and a soft invitation. Never write "Thanks for the detailed feedback" on a review with zero words.

Review: "Second time using them. Great again."

Reply: "Two for two — thanks, Priya. Repeat customers are the only review metric we actually care about. See you next time."

How to reply to 4-star and 3-star reviews

These are the most undervalued replies in local SEO. A 3-star reviewer is persuadable, and a public reply that handles the gap is extremely credible to prospects.

Review (4 stars): "Good work on the install, but they were about 90 minutes later than the quoted window."

Reply: "Fair, Tom — 90 minutes late is 90 minutes late, and we don't love it either. The van ahead of yours ran long on a leak. We've started building a 45-minute buffer into afternoon slots because of exactly this. Glad the install itself held up."

Note what that does: admits the fault, explains without excusing, and shows a process change. That reply sells.

Review (3 stars): "Food was lovely but we waited 25 minutes for the bill on a quiet Tuesday."

Reply: "Thanks for being honest, Jen. Twenty-five minutes for a bill on a quiet night is a service failure, not a staffing one. I've moved bill requests to the front-of-house tablet so they don't sit in the kitchen queue. Next dessert's on us if you let us know you're coming."

How to reply to 1-star and 2-star reviews

The rule: never litigate in public. Your audience isn't the reviewer, it's the 400 people who will read this thread over the next two years.

Review: "Absolute cowboys. Charged £480 for a job quoted at £300 and the leak came back in a week."

Bad reply: "This is completely inaccurate. The quote was for the initial diagnosis only, as explained at the time, and the additional work was authorised by you in writing."

Good reply: "I'm sorry, Kevin — a return leak after a week isn't acceptable regardless of the pricing conversation, and I'd like to put both right. Can you call me directly on 0161 xxx xxxx? I'm Rachel, I own the business, and I'd rather sort this than debate it here."

The second version wins because it concedes the thing that matters (the leak), ignores the thing that doesn't (the he-said-she-said on price), and puts a named human with a direct line on the record.

Review: "Receptionist was incredibly rude on the phone."

Reply: "That's not the standard we hold, and I'm sorry you got it. I'd like to know which call so I can listen back and handle it properly — can you email the date and rough time to rachel@domain.com? Either way, thank you for telling us."

Review you believe is fake or from a competitor:

Reply: "We don't have a record of a customer by this name or a job matching this description, so I may be missing something. If we did work for you, please email us so we can look into it — we'd genuinely like to resolve it. We've also flagged this for review in case it was posted to the wrong business."

Report it in Google Business Profile at the same time, citing the specific policy — spam, conflict of interest, or off-topic. Realistically you'll win maybe a third to half of these, and the process takes 3-14 days, so the public reply matters.

What never to put in a review reply

The agency workflow that makes this sustainable

Writing one good reply is easy. Writing 300 a month across a client roster is an operations problem.

1. Set a tiered SLA

1-2 stars: respond within 24 hours, owner-approved. 3 stars: 48

Featured in this list? Grab your “Featured on PeakKR” badge and add it to your site — free.
Get your badge →

Frequently asked questions

Does replying to Google reviews help SEO?

There's no confirmed ranking boost from replies alone, but Google explicitly tells businesses to respond, and replies influence conversion — people read owner responses before calling. Indirectly, more replies tend to correlate with more reviews over time, and review quantity and recency are real local ranking factors.

How long should a Google review reply be?

Aim for 2-4 sentences, roughly 35-80 words. Short enough that it doesn't get truncated in the mobile Google Business Profile view, long enough to sound like a human wrote it. Negative reviews can run slightly longer if you need to correct a factual error.

How fast should you respond to a Google review?

Within 24-48 hours for negative reviews and within a week for positive ones. Negative reviews are what prospects read first, so a same-day reply limits the damage. Anything older than 30 days is still worth answering — but say nothing that implies you just noticed it.

Can you get a fake Google review removed?

Sometimes. Report it through the Google Business Profile review management tool and cite the specific policy violated — usually spam, conflict of interest, or off-topic. Expect a 3-14 day review and a roughly 30-50% success rate, so always post a calm public reply in the meantime in case it stays up.

Nick Quirk

Written by Nick Quirk

Founder of PeakKR

Nick Quirk is the founder of PeakKR, the agency workspace. He has spent decades running SEO and operations for marketing agencies, and writes about what holds up in real client work: technical audits, reporting, local campaigns, retainers and the systems behind them.

Run your agency on PeakKR

Client projects with phases, time tracking, technical SEO audits, client-ready reporting and AI briefs — the workspace this blog is written from.

Start free

Keep reading