Reviews

How to reply to negative Google reviews (without making it worse)

A step-by-step framework for replying to bad reviews — plus five real example responses for the hardest scenarios small businesses face. Written for owners and office managers who have an hour and a 1-star review, not lawyers.

April 21, 2026 8 min read Updated for 2026

Getting a negative Google review feels personal because it is personal. You built the business. Someone is telling the world — and, more specifically, the next hundred people searching for you — that you're not good at it. The instinct is either to unload on them publicly or to pretend the review doesn't exist. Both instincts are wrong. This post walks through what actually works.

Before we get into the framework, two things worth knowing:

With that out of the way — here's how to do this well.

The five-part reply framework

Good responses to negative reviews do the same five things, in roughly the same order. Miss any one of them and the reply falls flat. Use all five and even a bad review becomes a quiet asset.

01

Open with their name (or a thank-you)

Address the reviewer by the name they left. It signals you read the review as a person, not a PR exercise. If no name is attached, "Thank you for the feedback" works. Do not open with "We apologize" — that's the second sentence, not the first.

02

Acknowledge the specific complaint

Name the actual thing they said happened. "Sorry for the inconvenience" doesn't work — it reads as corporate and it signals you didn't actually read the review. "I'm sorry your dishwasher wasn't reconnected after we finished the job" reads as human and specific.

03

Take proportionate responsibility

If you made a mistake, say so. If the review is unfair or the facts are wrong, you don't have to accept blame — but you also don't have to litigate it publicly. "We hold ourselves to a high standard and this didn't meet it" works for real mistakes. "We have a different recollection of what happened, and we'd welcome the chance to discuss it" works for contested ones.

04

Offer a concrete next step

Give them somewhere to go. A direct phone number, an email, a manager's name. "Please reach me at 555-0123 or manager@business.com" moves the conversation off Google and shows every future reader that you want to resolve issues. Don't link to a generic contact form.

05

Close with a line for the next reader

One short sentence that signals your standards. "We take feedback like this seriously and use it to improve." "This isn't the experience we aim for and we're sorry it was yours." Nothing defensive. Nothing that invites further argument. Just one sentence that lands.

Your reply is not a conversation with the reviewer. It's a billboard for the next hundred people searching for your business.

Five worked examples

Here are five of the hardest scenarios small businesses actually face, with the response that usually makes it worse and the response that works. Every business should adapt the wording to their own voice — these are templates, not scripts.

Example 1 — Service went wrong

The customer had a real bad experience

★☆☆☆☆
Sarah M.

"Paid $450 for an HVAC tune-up and the tech left without turning my system back on. I came home to a 58° house with my baby. Called the office three times, never got a callback. Will never use them again."

Reply that makes it worse

"We apologize for any inconvenience. Please contact our office during business hours to discuss your concerns."

Reply that works

"Sarah — this is exactly the kind of thing that shouldn't happen, and I'm sorry it happened to you. A technician leaving without confirming the system restart, and then three unreturned calls, is a real failure on our end. I'd like to make this right personally. Please reach me directly at 555-0123 — I'll be available today and will call you back within the hour if you leave a message. Thank you for bringing it up; we need to hear this to fix it."

Why it works: Uses her name. Names the two specific failures (no restart, no callbacks). Takes full responsibility. Gives a direct phone number and a promise. Closes with gratitude, not defense.

Example 2 — Customer was wrong (politely)

The facts don't match the review

★★☆☆☆
James T.

"Went in for a quick oil change and they tried to sell me $1,200 of repairs I didn't need. Shady."

Reply that makes it worse

"This is absolutely not true. We have photos of your worn brake pads and our technician followed standard procedure. Customers like you are the reason small businesses struggle."

Reply that works

"James, thanks for the feedback — I'm sorry you left feeling pressured. To be clear about our process: our technicians flag anything they see during the multi-point inspection, but the decision is always yours, and nothing is added to the bill without your say-so. I'd genuinely like to walk you through what we found if you're open to it. My name is David; I'm the service manager and you can reach me at 555-0123 or david@shopname.com. If after that conversation you still feel the recommendation wasn't warranted, I'll make it right."

Why it works: Doesn't call the customer a liar (even if they are). Clarifies the process without being defensive. Names a specific person. Offers to resolve even if the customer is partially wrong. Future readers see a business that stands by its work without picking fights.

Example 3 — Restaurant / food service

The party-of-six-on-a-Friday review

★☆☆☆☆
Anna K.

"Waited 45 minutes for our food on a Friday night. The server was overwhelmed. Food was mediocre when it finally arrived. Won't be back."

Reply that makes it worse

"We were extremely busy that night. Thank you for your patience."

Reply that works

"Anna — 45 minutes is too long, full stop, and I'm sorry that was your first impression of us. Friday nights are our busiest and we sometimes fall behind when we shouldn't; that's on us to staff and prep for, not on you to tolerate. If you'd give us another chance, I'd love to have you back as my guests — please email me directly at marco@restaurantname.com and I'll set it up. Thank you for the honest feedback; this is the kind of thing we actually need to hear."

Why it works: Uses her name. Doesn't blame "how busy we were" — acknowledges that Friday staffing is the owner's responsibility. Offers a concrete make-good. Signals "owner reads reviews" which lands well for future diners.

Example 4 — The fake or competitor review

The reviewer was never a customer

★☆☆☆☆
R. Jones

"Worst service in town. Rude staff. Wouldn't recommend to my worst enemy."

Reply that makes it worse

"This is a fake review from a competitor. We've reported it to Google. Shame on you for trying to damage a small business."

Reply that works

"Hi — we don't have a record of serving a customer by this name, and we'd very much like to understand what happened if you did visit us. Could you email hello@businessname.com with the approximate date of your visit? If we made a mistake, we want to fix it. If this was posted in error or for the wrong business, we'd appreciate the chance to clarify."

Why it works: Doesn't accuse the reviewer publicly (which often backfires, even when you're right). Invites clarification. Signals to future readers that the review might not be legitimate without you having to say so. Separately, flag the review through Google Business Profile — see the section below.

Example 5 — The vague one-star with no detail

"★ Terrible" with no other text

★☆☆☆☆
No review text

(No review text was left.)

Reply that makes it worse

"Why are you rating us so low without any explanation? Please contact us or remove this review."

Reply that works

"Hi — we noticed this one-star rating but there's no review attached. We'd genuinely like to understand what went wrong so we can make it right. If you'd be willing to share a few details, please email hello@businessname.com or call us at 555-0123. Thank you."

Why it works: Doesn't demand the review be removed (which reads as controlling). Invites context. To future readers, it signals a business that cares enough to ask. Ratings without review text are often mis-clicks or misdirected frustration — a calm reply sometimes earns an edit or retraction.

Let AI draft these replies in your voice.

velociPost watches your review and comment feeds, drafts on-brand replies, and posts them only after you approve.

Join the waitlist

When the review involves something serious

Not legal advice

Some review scenarios can tip into legal territory — and the wrong public reply can make that worse. The guidance below is general and is not a substitute for an attorney.

If a review raises any of the scenarios in this section, do not post a detailed public reply until you've consulted someone qualified.

Healthcare, dental, or anything HIPAA-adjacent

US healthcare providers are subject to strict patient privacy rules. Even acknowledging that a reviewer was a patient can be a HIPAA violation. If you run a medical, dental, therapy, or similar practice, your response should never confirm or deny the person was a patient. A safe template: "We take all feedback seriously. Privacy regulations prevent us from discussing specific patients publicly. Please contact our office at 555-0123 if you'd like to speak privately." Consult your compliance counsel for your specific situation.

Defamation, threats, or false statements of fact

If a review contains statements that are factually false and damaging — not opinions ("I didn't like the food"), but claims of fact ("they gave me food poisoning") that are provably untrue — you may have legal recourse. Do not attempt to argue this publicly. Document the review, consult an attorney, and use Google's formal review removal process. Public legal threats in a review response rarely end well and are frequently screenshotted and shared.

Safety incidents or alleged injury

If a reviewer alleges injury, a safety incident, or similar, do not respond publicly beyond the most minimal possible acknowledgment. Anything you write can be used as evidence. Consult your insurance carrier and legal counsel before posting. A response like "Please contact our office directly at 555-0123" is appropriate; anything more detailed should go through your lawyer.

Staff accused by name

If an employee is named negatively, never defend or throw them under the bus publicly. Your reply should stay general: "We take all concerns about our team seriously and investigate them internally." Handle the substance privately with the reviewer and the employee. This is both good HR and good optics.

When not to reply at all

A few scenarios where not replying is better than replying badly:

How to flag a review for removal

Google will remove reviews that violate its policies — but "policy violation" is narrower than "I don't like it." Reviews that usually qualify:

  1. Spam or fake content — reviews from people who were clearly never customers, or obviously paid/automated.
  2. Off-topic content — political rants, personal grievances unrelated to your business.
  3. Conflicts of interest — reviews from competitors, former employees with an axe to grind, or your own staff.
  4. Hate speech, harassment, or threats — content that's abusive rather than critical.
  5. Personal information — reviews that name employees by full name, include contact info, or dox individuals.

To flag: find the review in your Google Business Profile dashboard, click the three-dot menu, and select "Report review." Submit with a clear, factual note about which policy you believe it violates. Google's response time varies from days to weeks. Having multiple legitimate reviews and a history of responding professionally to negative ones helps your overall credibility when flags are evaluated.

A review simply being negative is not a policy violation. Google will leave those up, and trying to remove them is a waste of time. Focus instead on earning more positive reviews to balance the ratio — the long-term play that actually moves the dial.

The quiet habit that makes all of this easier

The single best defense against the damage a bad review can do is volume. A 1-star review out of 20 total reviews is devastating. A 1-star review out of 200 is barely visible. Every week you're not asking your happy customers for reviews, you're letting the unhappy ones weigh proportionally more than they should.

Build asking for reviews into your close-of-business workflow: an email after a job is done, a QR code on the receipt, a short SMS a day later. You don't need a platform for this — a Google review link works from any device. Three review asks a week, for a year, is how small businesses quietly end up with the 4.9-star badges on their Google Business Profile.

Replying well to the bad ones is half the job. Making sure they're outnumbered is the other half.

Bottom line

Reply to every negative review. Use the five-part framework: name, specific acknowledgment, proportionate responsibility, concrete next step, one closing line for the next reader. Keep emotion out of it. Move anything serious off Google and into a phone call, email, or — if the situation warrants — your lawyer. Flag the ones that violate policy. Ignore the ones that don't. And spend more energy earning new positive reviews than fighting the old negative ones. That's the whole playbook.

Common questions

Should I reply to every negative Google review?

Yes — with three exceptions. Don't reply when you're angry, when the review is years old, or when it's part of an obvious coordinated pile-on. Every other negative review deserves a reply, because future customers read the reply as much as they read the review itself.

How long do I have to respond to a Google review?

There's no time limit, but faster is better. Replying within 24–48 hours signals attentiveness; replying weeks later can look reactive or performative. That said, it's better to reply late than never — an acknowledgment at week three is still worth more than silence.

Can I get a bad Google review removed?

Only if it violates Google's policies — spam, fake content, off-topic rants, harassment, personal information, or obvious conflicts of interest. A review that's merely negative won't be removed. Flag through Google Business Profile's "Report review" option and include a specific policy citation.

Should I offer a refund or discount in my public reply?

No. Take that offer off Google and into a private channel (phone or email). Publicly offering refunds creates incentive for future reviewers to leave negative reviews in hopes of getting one, and it can set a precedent you don't want to follow.

What if the reviewer writes back after my reply?

Respond once more at most, still calmly, and move the conversation to private channels. Public back-and-forth never ends well for the business — every reply from you is another timestamp showing the dispute dragged on.

Do replies to Google reviews help SEO?

Indirectly, yes. Replies signal to Google that the business is active, and review activity (volume, rating, responses) is a factor in local pack ranking. More importantly, they signal to prospective customers — which is the ranking that actually matters.

Can I delete a response I already posted?

Yes. In Google Business Profile, go to Reviews, find the review with your response, and edit or delete your reply. If you posted something you regret, fix it — a short, considered reply is always better than a hot one you're stuck with.

Should I use AI to draft my replies?

Used well, yes. AI can handle the framework reliably — the five-part structure, the tone, the professional language. The business owner should still review and often edit every reply before it posts, especially on serious reviews. A tool that drafts but requires human approval — like velociPost's engagement inbox — saves time without taking humans out of the loop where they're needed most.

Reply to every review, at the right time.

velociPost watches your Google Business Profile, Facebook, and Instagram, drafts on-brand replies to comments and reviews, and posts them after you approve. Join the waitlist — first 200 customers get the founder's rate, locked forever.

No spam. Unsubscribe anytime.

You're in — welcome. Check your inbox.

Something went wrong. Please try again.