How to respond to a bad Google review (with examples)

Most advice about answering negative reviews starts from the wrong premise: that you are writing to the unhappy customer, and the goal is to win them back. Sometimes that happens. It is not the job.

The reviewer already had their experience and already told the internet about it. The people who matter are the ones reading the review three weeks from now, on a phone, comparing you against two competitors with similar star ratings. They are actively looking for it — 96% of consumers seek out negative reviews specifically, because the one-star reviews are where they expect to find out what a business is really like.

What they find under the complaint is your reply, and they read it as a preview of how they would be treated if something went wrong for them. That is the whole audience. Write for them.

The measurable difference is not subtle: 88% of consumers say they would use a business that responds to all its reviews, against 47% for a business that responds to none. And 56% say a business's handling of a review changed their opinion of that business — in either direction.

What a good reply has to do

Four things, in about eighty words.

Acknowledge the specific thing. Not "we're sorry you had a negative experience." The specific thing: the wait, the instructor, the invoice, the room temperature. A generic apology tells the reader you did not read the review, which confirms the complaint rather than answering it.

Take the temperature down, not the position. Warm, unhurried, no defensiveness. This is compatible with disagreeing — it is not compatible with sounding stung.

Show that something is different now, or that you want to understand it better. A reader forgives almost any single bad experience. What they will not forgive is a business that seems unaware.

Move it off the platform. A name, a direct email, an offer to make it right. This does two jobs at once: it gives the reviewer a real path, and it shows every other reader that a human is reachable here.

What it should not do is relitigate. The moment your reply is longer than the review, you have lost — the reader stops evaluating the complaint and starts evaluating you.

Example one: the complaint you can actually fix

★★ "First time here. Nobody greeted me, the instructor didn't know my name, and $32 for a drop-in class is steep for that kind of welcome. I travel a lot and visit studios everywhere — this one felt cliquey."

A weak reply:

"We're so sorry to hear about your experience! We strive to provide excellent service to all our customers and we're disappointed we fell short. Please reach out to us so we can make it right."

Nothing in that is wrong, and nothing in it is real. It would fit under any complaint at any business in any industry — which is exactly what the reader notices. It also leaves the price claim standing, which is a problem, because the price was wrong.

A better reply:

"Dana — sorry we didn't make you feel welcome on your first visit. That's on us, not on you, and I'd rather hear it than not. One correction: a drop-in is $22, not $32 — if you were charged $32 something went wrong at the desk and I want to fix it. Come back next time you're in town and the class is on me. Ask for Erin at the front desk, she'll be expecting you."

Roughly the same length as the weak one. The difference is that every sentence in it could only have been written about this review.

Three things it does deliberately. It corrects the price without arguing about the feeling — the factual error gets fixed in one sentence, the emotional claim gets conceded in full. It names a person, which converts an abstract invitation into something a nervous first-timer can actually do. And it owns the specific failure without a general confession; "we didn't make you feel welcome" is answerable, where "we failed to deliver excellence" is not.

Example two: when the reviewer got the facts wrong

The correction is the hardest move in review replies and the most commonly botched. Two rules make it survivable.

Correct facts, never feelings. Prices, hours, policies, whether a refund was issued, whether they were charged twice — those are checkable and you should fix them, because the reader is going to act on them. How welcome someone felt is not a fact you have standing to dispute, even when you are sure they are wrong.

Put the correction after the acknowledgment, not before it. The same sentence in the other order reads as a rebuttal.

★ "They charged me twice and refused to refund it. Avoid."

"That sounds awful and I'd be furious too. I've looked into it — we show one charge on the 14th and a pre-authorization hold that dropped off three days later, which your bank may still be displaying. If you're seeing two actual charges, send me the statement line at hello@[business].com and I'll refund it today. Either way I want to see what you're seeing."

The reader does not need to know who is right. They need to see that the business checked, engaged with specifics, and offered a resolution before establishing fault. That is enough.

Example three: the four-star review with a complaint in it

This is the one almost everybody skips, and it is the most common review a healthy business gets.

★★★★ "Love this place, the team is great. Only thing — the 6pm class is always packed and it's hard to find a spot. Otherwise no complaints!"

The instinct is to reply the way you reply to five stars: thank them warmly, move on. That is a small, real mistake. The reader scanning your page sees one person raise a concrete issue and a business that thanked them for the compliment and ignored the issue. A four-star review with a complaint is an unhappy review wearing a polite hat.

"Thank you Marcus! And the 6pm crowding is fair — it's our busiest hour by a wide margin. We've added a second Tuesday evening class to pull some of that pressure off; if you ever find the room full, the front desk can hold a spot for you. Glad you're here."

One clause of acknowledgment, one thing that changed, one practical option. It costs fifteen words and it is the difference between a page that reads as managed and a page that reads as monitored.

A caution on that reply, though: it works because the second Tuesday class is real. The most dangerous sentence available to you in a review reply is a commitment you have not actually made — "we're working on the space issue during peak times" is a public promise on a page that ranks for your business name, and nobody signed off on it. Never let a reply invent one, and if you are using a tool to draft replies, understand that this is the failure mode it is least able to catch on its own.

The reviews you should not answer publicly

Some complaints do not have a good public reply, and posting one anyway makes things worse:

• Anything involving injury, a medical detail, or an accusation against a named staff member. Never discuss a specific person's conduct, a customer's health, or a safety incident on a public page. "I'd like to talk about this directly — please email me at [address]" is the complete reply.
• A demand for a refund or a legal threat. Acknowledge briefly, take it offline, and get whoever handles that involved before you write anything else.
• A review that is clearly not your customer, or that violates Google's content policy. Report it and consider a short factual note only if it stays up: "We have no record of a booking under this name — if we've made a mistake, please contact us." Do not argue with it.

And a note on timing: 34% of consumers expect a reply within two to three days and 87% within two weeks. Speed matters less than it feels like it does in the hour after a bad review lands. Writing the reply while you are still angry is far more expensive than writing it tomorrow.

The thing nobody expects

There is good evidence that answering complaints changes the complaints you get.

Two researchers examined tens of thousands of hotel reviews on TripAdvisor before and after management began responding, and published the result in Marketing Science. Businesses that started replying saw ratings rise by 0.12 stars and review volume grow 12%. The mechanism was not that customers got happier. It was that marginally dissatisfied customers became less willing to post an exaggerated complaint once they knew someone was reading. As one of the authors put it, it is like someone is looking over your shoulder as you write.

The trade is worth understanding: fewer trivial complaints, but the ones that remain are longer and more substantive. You get a better page and harder feedback. Both are useful.

Roughly one review in three gets a reply on that platform. The bar is genuinely that low, which is the good news.

Worth knowing what this does and doesn't buy you in search, though: owner responses are a real but small direct ranking factor, and the larger effect runs through review volume and recency. We pulled the numbers apart here.

We build managed review-response systems that write in a specific business's voice rather than a generic one, with complaints routed to a person instead of a model. Here's how that works.