Review request scriptsReview Request Scriptsbad reviewsrestaurant reputation
    By Rinkle AgarwalApril 16, 20266 min read

    How to Respond to Bad Google Reviews for Your Restaurant

    Bad Google reviews happen. The key is responding in a way that shows future diners you care, take action, and stay professional.

    Editorial illustration for the review request scripts article: How to Respond to Bad Google Reviews for Your Restaurant

    A bad Google review feels personal, especially in hospitality. The first instinct is to defend the restaurant, explain why the customer was wrong, or worse, ignore it and hope it slides down the page. All three instincts are wrong. The response you write to a bad review is not really for the unhappy diner. It is for every future prospect who reads that review on their phone two weeks from now while deciding whether to book. Get the response right and the bad review can actually become a trust signal. Get it wrong and the review compounds the damage.

    Why the response matters more than the review itself

    A new customer scrolling your Google profile reads roughly seven to ten reviews before deciding whether to book. They specifically look for negative reviews, because perfect five-star profiles read as suspicious. What they actually want to see is whether the restaurant handled criticism well. A four-point-six rating with a thoughtful, non-defensive owner response under the worst review converts much better than a four-point-nine rating where the owner argued with the only critic. The math is unintuitive but consistent: how you respond to bad reviews changes how new customers read the rest of your profile.

    This means the response has to be written for the future reader, not the original reviewer. The reviewer has already left. The response is a public artefact that lives on the profile alongside the original review, sometimes for years. Treat it like signage in your restaurant: visible, branded, considered.

    The four-step response structure that works

    Almost every effective bad-review response follows the same four-step structure, in this order. Skipping any of the four steps usually weakens the response.

    1. Acknowledge the specific experience the customer had, in your own words. Not "thank you for the feedback," which sounds robotic. Something like "thanks for taking the time to write this, we read every review carefully."
    2. Address the specific issue they raised, not a generic apology. If they complained about slow service, mention service. If they mentioned cold food, mention the food issue. Specificity proves you read the review.
    3. Take responsibility without making excuses. "That is not the experience we want any guest to have" lands far better than "we were short-staffed that night." Even when the excuse is true, putting it in the public response sounds defensive.
    4. Invite an offline follow up with a real contact method. "Please reach out to us at [email or phone] so we can make it right" moves the substantive conversation off Google, where you cannot say much without escalating.

    This whole response is usually four to six sentences. Anything longer reads as defensive over-explanation. Anything shorter reads as a brushoff.

    An example that uses all four steps

    "Thanks for taking the time to share this. We are genuinely sorry the food arrived cold and that you waited longer than expected. That is not the experience we want any guest to have, and we have already gone through what happened with the kitchen team. We would really appreciate the chance to make it right. Please reach out to us at hello@example.com or call us at [phone] and ask for [manager name]."

    Notice what is happening: the response acknowledges, addresses both specific issues (cold food and wait time), takes responsibility without blaming the kitchen, and provides a real contact path. It does not argue. It does not ask the reviewer to update their review. It does not offer compensation publicly. The future reader sees a restaurant that handled a hard moment with care.

    What not to do, even when the review is unfair

    • Do not accuse the customer of lying or call the review fake in public. Even when it is, public accusations make the restaurant look worse, not the reviewer.
    • Do not argue the facts point by point. "We have CCTV footage that shows..." responses are universal red flags to future readers, regardless of what the footage shows.
    • Do not copy-paste the same apology under multiple reviews. Future readers scroll multiple bad reviews looking for patterns; identical responses are exactly the pattern they spot.
    • Do not ignore bad reviews for more than a couple of days. Silence reads as not caring, and Google's local pack ranking tends to favour profiles with active owner engagement.
    • Do not offer comps or refunds publicly in the response. It attracts bad-faith reviewers angling for the same offer and borders on Google's prohibition against incentivised reviews.
    • Do not let staff respond unsupervised. The most damaging restaurant review responses almost always come from someone who got emotional, replied too fast, or used a personal voice that did not match the brand.

    How to handle the genuinely fake or policy-violating review

    Some bad reviews are legitimate criticism of a real visit. Others are fake (someone who never came in, a competitor, a mistaken identity, an account with no other activity). For the genuinely fake category, do not engage publicly until Google rules on the report. Engaging publicly with a fake reviewer often gives the review more visibility and almost always pulls you into an argument that costs you credibility with future readers.

    Instead, document everything you can (no record of the visit, account is new, content is clearly not yours) and report the review through your Google Business Profile under the inappropriate content option. Google's review content policy covers fake reviews, conflicts of interest, hate speech, illegal content, and off-topic posts. Reviews that fit those categories get removed when reported, though it can take days to weeks. Reviews that are simply critical of your food or service do not qualify and reporting them wastes time better spent on writing a good public response.

    Giving unhappy diners a real way to be heard

    The other half of handling bad reviews is making sure diners who had a rough visit have a real way to reach the team in addition to the Google review path. The unhappy diner who never had an easy channel to raise concerns directly is more likely to feel ignored by the time they sit down to write a review. The right pattern is to offer every guest the same prompt. Show the Google review path regardless of how the visit felt, and make it just as easy for the guest to send the manager a private note alongside the public option. That is fully compliant with Google's review policies and the FTC's rules on consumer reviews, and it gives the team a much better chance to follow up on issues directly.

    Done well, this means more complaints arrive in a form the restaurant can actually act on, often before the public review gets written at all, while every diner still has the public option in front of them. The diner who chose to share private feedback often follows up publicly later in a more measured tone once the team has had a chance to make things right. The diner who only wanted to post on Google still has that path. Both routes stay open, both serve the restaurant well, and the team gets a much fuller picture of the guest experience.

    Response cadence and ownership

    Aim to respond within 24 to 48 hours. Faster is better; replies that show up two months later look defensive and detached even when the content is good. Concentrate response authority in one or two trained owners or managers; do not let staff respond unsupervised, and do not let multiple people respond to the same review. The most consistent restaurants run a simple rule: any response goes through the owner before posting, even if the manager drafted it.

    Kaisah offers every guest the Google review path and makes it just as easy to share private feedback with the team alongside it. That gives restaurants a real chance to follow up on concerns while keeping every voice on the public record if the guest chooses to share it. Compare plans at kaisah.com/pricing.
    Share: X LinkedIn Email

    Keep building this topic cluster

    If this topic is relevant to your workflow, these are the next pages worth visiting.

    FAQ

    Quick answers for the most common questions around this topic.

    How quickly should I respond to a bad Google review?

    Within twenty four to forty eight hours is the practical bar, and faster is better. A calm, specific response that arrives quickly often catches the customer before they have decided to escalate further or share the experience elsewhere. Replies that show up two months later look defensive and detached, even when the content is good. The longer the silence, the more it reads to other prospects as the restaurant not caring.

    Should I ever ask Google to remove a bad review?

    Only if the review actually violates Google's content policy, which covers fake reviews, conflicts of interest, hate speech, illegal content, or off topic posts. A review that is critical of your food or service does not qualify, even if you disagree strongly with the assessment. Reporting reviews that do not meet the criteria almost never works and wastes time you could spend writing a good public response.

    Should I offer compensation publicly in the review response?

    It is generally a bad idea. Public offers of comps or refunds attract bad faith reviewers angling for the same offer and can border on Google's prohibition against incentivising reviews. The right move is to acknowledge the issue publicly, invite the customer to reach out by email or phone, and then handle any compensation privately. The public response is for future readers. The private follow up is for the actual customer.

    What if the bad review is from someone who never visited?

    Document everything you can (no record of the visit, account is brand new, content is clearly not yours) and report the review through your Google Business Profile under the inappropriate content option. Do not engage publicly until Google rules on the report. Engaging publicly with a fake reviewer can sometimes give the review more visibility, and it almost always pulls you into an argument that costs you credibility with future readers.

    Should every team member be allowed to respond to reviews?

    No. Review responses are a public reputation asset and should go through one or two trained owners or managers. The most damaging review responses almost always come from someone who got emotional, responded too fast, or replied in a personal voice that does not match the brand. A small approval workflow, even just a quick check by the owner before posting, prevents most regrettable replies.

    Read next

    More Kaisah articles on review request scripts and nearby review-conversion topics.