Most review responses are either too generic to help or too defensive to be believed. Here's what a good reply looks like — with real examples from one-star to five-star — and the five phrases you should never write.
If you've ever looked at a competitor's Google listing and read their responses to reviews, you've probably noticed one of two things: either they don't respond at all, or every response sounds like it was written by legal counsel reviewing a PR statement.
"Thank you for your feedback. We are committed to providing excellent service and will take your comments under consideration." That tells the next prospective customer exactly nothing. It doesn't acknowledge what happened, it doesn't signal that a real person read the review, and it doesn't give anyone a reason to feel differently about the business.
The good news is that writing a genuinely useful review response is not complicated. It just requires treating the reviewer like an actual person rather than a liability to be managed. Here's what that looks like across every rating level — and the common mistakes that undermine responses that are otherwise well-intentioned.
Before getting to examples by star rating, it's worth understanding what every good response has in common. There are four moving parts, and they apply whether you're responding to praise or a complaint:
Name something from the review. Not "your experience" — the actual thing they mentioned. "Your comment about the wait on Friday" or "your kind words about Maria on our team." This proves you read it.
For negatives: what happened, briefly, and what changed. For positives: one detail that reinforces why that thing they noticed matters to you. Not a paragraph — one sentence.
For negatives: invite them to contact you directly (offline, not in the reply thread). For positives: a genuine invitation back, or a simple "we look forward to seeing you again." Forward-looking, brief.
Three to five sentences is the target for negatives. Two to three for positives. Longer almost always reads worse. Every sentence you add after the necessary ones erodes the credibility of the necessary ones.
"The goal of a review response is not to convince the reviewer. They've already left. The goal is to show every prospective customer who reads it how you treat people."
These show up in most business review responses. Each one makes the reply read worse than if you'd said nothing, even if the rest of the response is good.
The honest answer: not necessarily every single one, but every one that matters.
Always respond to: every 1-star and 2-star review, every 3-star review that contains a specific complaint, and any review — regardless of rating — that raises a public concern others might have (food safety, pricing disputes, accessibility).
Respond selectively to: 4-star and 5-star reviews. If someone writes three sentences and names something specific, a response is worthwhile. If someone writes "Great!" with no other detail, a response isn't necessary — and a generic "thank you for the five stars!" response is worse than none at all.
The rule of thumb: if the review gives you something to respond to, respond. If it doesn't, you don't need to manufacture something.
Individual responses are manageable when you're getting five reviews a month. When you're getting fifty — across Google, Yelp, and Facebook — the math changes. At that volume, most business owners default to one of two positions: they respond to nothing (too many) or they respond to everything with the same three-sentence template (copy-paste visible from a mile away).
Neither helps the reputation. The template approach is arguably worse than silence because it actively signals to prospective customers that nobody is actually reading the reviews.
The middle path is triage: know which reviews need a real response, immediately, before they've sat for three days. That requires knowing a review exists, which requires monitoring across every platform you're active on — not checking each one manually every morning.
GleamIQ's alert rules notify you within hours of any review matching criteria you set — 1-star rating, specific keywords like "wait" or "wrong order," or sentiment below a threshold — across every connected platform simultaneously. You get one notification; you reply while it's still relevant. Set up alerts →
Some reviews are unfair. Some are factually wrong. Some appear to be from competitors or disgruntled ex-employees. The experience of reading a false accusation in a public forum is genuinely unpleasant, and the instinct to correct the record is understandable.
The problem is that defending yourself in a review response almost never reads the way you intend it to. Even a factually accurate correction, delivered calmly and politely, reads to prospective customers as a business that argues with its reviewers. That's a harder perception to shake than whatever the reviewer originally said.
The practical rule: write the response you want to write. Then wait an hour. Re-read it. Anything that sounds like it's defending you rather than addressing the reviewer's experience — cut it. What's left is usually better.
"The prospective customer reading your response has no idea who's right. They're watching how you handle it. Composure is more credible than being correct."
For reviews that are clearly fraudulent — wrong business, provably false claims, coordinated attacks — the response strategy is different: respond once, calmly, note the factual discrepancy without arguing, then flag the review through the platform's process. Don't engage repeatedly. Don't let the thread become a debate.
A review response is a short piece of writing with an unusual property: the primary reader isn't the person it's addressed to. It's the next person who searches for your business and reads through a handful of reviews to decide whether to visit. Write it for them.
GleamIQ monitors your reviews across every platform and alerts you the moment one matches your criteria. Respond while the experience is fresh — not days later when it's already shaped someone's opinion of you.
Start monitoring reviews — $99.99/moHow do I respond to a Google review?
Log in to Google Business Profile, go to Reviews, and click Reply next to the review. Acknowledge something specific from the review, add one line of genuine context, and keep it under five sentences. For negative reviews, take the resolution offline — invite them to contact you directly rather than negotiating in the public thread.
Should I respond to positive Google reviews?
Selectively, yes. Every negative review (1-3 stars with a specific complaint) needs a response. Positive reviews benefit from a response when the reviewer said something specific you can reference — a generic "thanks for the five stars!" adds nothing and can read as automated. Focus your energy on the reviews that have something to respond to.
How long should a Google review response be?
For negative reviews: 3-5 sentences. For positive reviews: 2-3 sentences. Longer almost always reads worse. Every sentence past what's necessary makes the response look over-explained and defensive, even if every word is reasonable.
What should I not say in a Google review response?
Never say "we're sorry you feel that way" — it's a deflection, not an apology. Never use generic openers like "our team strives to provide excellent service." Never offer a refund or comp publicly. Never argue with the reviewer even if they're wrong. Write the response, wait an hour, re-read: anything that sounds defensive rather than helpful — cut it.
Do Google review responses help SEO?
Indirectly, yes. Responding to reviews tends to drive more review volume (people see engagement and are more likely to leave their own), and higher review volume is a real local ranking signal. More importantly, response rate and response quality affect how prospective customers convert from search to visit — which is ultimately what matters.