How to reply to Google reviews: the complete guide

If you want the short answer: reply to every review that contains something a future customer could learn from, keep the reply under about four sentences, address the specific thing the reviewer described, and sign it so it is clear who is answering. You do not have to reply to everything. You do have to reply to anything a stranger reading the page would find worrying, because the reply is the half of that exchange you control.

This guide is the whole workflow: who is allowed to reply, the exact clicks, the structure of a good reply, what never to write, what to do when a review breaks Google's own rules, and how to keep the queue empty without losing an afternoon every week. Where we point at a Google rule we link the page we read and say when we read it.

Why replying is worth the time, and what it does not do

A reply does four practical things. It puts your side of a specific complaint next to that complaint, for as long as you leave it up. It shows the next reader that somebody is paying attention. It gives your team a place to record what was actually fixed. And it turns a vague bad feeling about a review into a dated, specific record you can act on.

What it does not do: it does not change the star rating, it does not remove the review, and it does not push the review down the page. Anyone selling you a reply as removal is selling something Google's own documentation does not offer. Google's help pages describe replying, editing a reply and deleting a reply - those are the three levers you have over your own words, and there is no fourth. The Manage customer reviews page sets out exactly those three actions.

That matters because a lot of review advice quietly rests on the hope that a good reply makes a bad review go away. It does not. The reply is for the reader, not the algorithm.

Who can reply to a Google review

You need access to the Business Profile. Owners and managers can both respond to reviews, and the difference matters when you hand this job to staff or to an agency. Google's page on owners and managers says additional owners and managers can edit info, respond to reviews and manage posts. What a manager cannot do is add or remove other users. So if you want an office manager, a receptionist or an agency to keep the reply queue empty, manager access is enough - and it is the safer default, because it does not let them lock you out of your own listing.

Practical consequence: if you are paying someone to draft replies, give them manager access and keep owner access yourself. Nobody needs your password, and Google's own documentation points out you can manage a profile without sharing one.

One more access fact people trip over: replies attach to a specific listing. If you run two locations, each profile has its own reviews and its own replies. A multi-location operator has to be explicit about which listing a reply belongs to before anything is written, or a reply ends up under the wrong address, which is worse than no reply.

How to reply, step by step

On the web: open your Business Profile, select Read reviews, find the review, select Reply, type your reply, select Reply again. That is the whole flow on Google's Manage customer reviews page, read 27 October 2026. To change the wording afterwards, select Edit under your reply; to remove it, select Delete. The same page documents both, which is worth knowing before you spend twenty minutes agonising over a sentence - an owner reply is editable and deletable, unlike the review itself.

In the mobile interfaces the same actions exist. The habit worth building is to work the list top-down: pick a fixed day, start at the oldest review with no reply, and stop when you reach the newest one you have answered. Whether your interface offers a filter for that or not, the routine is what empties the queue.

At scale, Google's Business Profile APIs expose reviews and replies programmatically. The review data page shows replies being created and deleted against a review. That is for developers and for tools, and it is the mechanism any tool you buy is using underneath. If a vendor says they are posting to Google for you, that page is the honest version of what they mean.

For multi-location businesses the real question is not how to reply but who owns which listing and who approves what. Decide that before the queue grows, not after.

Get the facts before you write

The most common way a reply goes wrong is that it was written from memory. Before you type, spend sixty seconds finding out what the record says: the booking, the ticket, the table, the invoice, whichever system holds it. A reply written from the record can be specific. A reply written from memory hedges - and in our experience hedging is what readers tend to read as guilt.

Two things to settle before writing. First, was this person a customer - because your reply will change completely depending on the answer, and 'we cannot find your booking' must never be the first sentence. Second, did anything actually change as a result of this complaint - because if it did, that is the single most reassuring sentence available to you, and if it did not, you must not imply it did.

If you cannot establish either fact, the right reply is short and asks for a way to identify the visit, in a channel that is not public. That is not a weaker reply. It is the only truthful one.

What a good reply is made of

Three layers, in this order: acknowledge the specific thing, say what happens next, sign off. Everything else is decoration.

Acknowledge the specific thing. Not 'thanks for your feedback' - name the thing. 'You came in for a brake job on the 12th and the noise came back.' A reply that could have been written before anybody read the review is worse than no reply, because it proves nobody read it.

Say what happens next, in the past or future tense, truthfully. 'We have booked you in to look again' if that is true. 'We have changed how we check that job' if that is true. If nothing has changed yet, say what you are doing and by when, or say you would like to understand more and invite them to contact you. What you must not do is promise an outcome you have not checked you can deliver, in public, where your promise is now a quotation.

Sign off as the business, not as a person who might leave in six weeks. 'Sam, service manager' is good: it tells readers a human is accountable. But do not name staff who were not named in the review, and never put a personal mobile number in a public reply.

Length: aim for 40 to 70 words. Long enough to name the thing and say what you did; short enough that a stranger actually reads it. In our reading, a reply longer than the review tends to read as defensive, even when every word of it is reasonable.

Replying by star rating

One table, eight situations. The rule behind all of them: reply to anything a stranger reading the page would find worrying, and treat the rest as optional.

Two of those rows carry the weight. A three-star is usually a real customer describing a real friction with an honest middle rating - it is the review that tells you what to fix, which is why it gets a question rather than a defence. And the middle of a one-star is where owners lose money: that reviewer is not looking for a public conversation, so a short factual reply that offers a route in beats the four-paragraph explanation of what really happened.

A worked example

This is a composite, assembled from patterns we see repeatedly rather than a real customer - we do not use real reviews without permission.

The review: 'Took my car in for a service, they told me it needed new front pads. Two weeks later it is squealing again. Three hundred pounds and I have to go back. Not impressed.'

A weak reply, and why: 'Hi, thanks for your feedback, we are sorry you feel that way, please contact us to discuss. - The team.' It never names the brake job. 'Feel that way' implies the customer is the problem. And it asks them to do work - start an email - without saying what will happen when they do.

A strong reply: 'Thanks for flagging this, and sorry - a squeal two weeks after new pads is not what we want. We would like the car back on the ramp to check the pads and the discs, at no charge, and we will show you what we find. Please call the number on this listing and ask for the service desk. Dan, service manager.'

Why it works: it names the symptom and the timeframe. It says exactly what will happen and that it is free. It gives one route in. It is signed by a person with a role. It runs to about 65 words. And note what it does not do - it does not admit anything was done wrong, because nobody knows that yet, and it does not need to in order to be a good reply. That distinction is the most useful thing you can teach whoever writes these: you can be accountable for the next step without conceding the previous one.

What never to write

Anything that trades a benefit for a review change. Google's prohibited and restricted content policy names offering payment, discounts, free goods or services in exchange for posting a review, or for revising or removing a negative one. A reply saying 'we will refund you if you take the review down' is a written record of the exact thing the policy forbids, published by you.

A demand for proof in public. 'We have no record of you' in a public reply reads as an accusation, and if the reviewer was a customer under a different name you have now insulted them twice.

Medical, legal or financial detail about a named or identifiable person. For clinics especially: never confirm or deny that someone was a patient, never describe treatment, and never imply a diagnosis in a reply. The safe clinic reply talks about what the practice does about the kind of experience described, not about what happened to that person. Hotel replies have the same problem in a different coat - no room numbers, no dates of stay, no names.

An argument about the facts with the reviewer. You will not win it, the next reader does not care who is right, and it is the most common way a reply makes a rating problem worse.

A template so generic it could sit under anyone's review. This is exactly where machine-written replies fail with no human in the loop, and it is why the useful shape of any tool here is draft-then-approve, never auto-post.

When the review breaks Google's rules

Reporting is a separate tool from replying, with a different standard. Google's page on reporting inappropriate reviews is explicit: you can report any review, but only reviews that violate policy are eligible for removal, and you should not report a review just because you disagree with it or dislike it. Read that line again before your next report, because most owners we speak to have reported at least one review purely because it was painful to read.

What arguably qualifies: content that is not a genuine experience at the business, offers of incentive, competitor sabotage, and the categories in the prohibited and restricted content policy such as hate speech, personal information and off-topic content. What does not qualify: a one-star describing something that genuinely happened, badly, in the customer's view.

The cost of over-reporting is not only wasted time. Google's overview of Business Profile policies warns that where contributions to a profile are consistently unhelpful, off-topic or in breach of policy, Google may limit or suspend user-generated content for that profile. An owner who reports everything is gambling with the profile, not just with the review.

Practical sequence for a rule-breaking review: screenshot it, report it once, note the date, then decide whether to reply. If it is still up a week later, reply as though it were legitimate - short, factual, no allegation - because from the reader's side it now is.

Keeping the queue empty

The failure mode is never ignorance of how to reply. It is that nobody looks. A workable weekly routine, one person, around thirty minutes:

• [ ] Open Business Profile and work down the reviews that have no reply yet.
• [ ] Reply to 1-3 star reviews first, oldest first, because the delay is part of the message.
• [ ] Then 4-star.
• [ ] Then batch the 5-star ones, one or two lines each.
• [ ] Report anything that breaks policy, once, with the date noted.
• [ ] Write one line on what the week's worst review said and what you actually changed - that last line is the only part that improves the business rather than the page.

Three rules that keep it sustainable. Never let the person who writes the replies also be the only person who approves them; a reply written in temper is obvious to everyone except its author. Set a service standard you can actually hit - first response within two working days, say - and treat missing it as the alarm, because the only deadline that means anything here is one you set yourself. And keep the record: a dated note of what a review said and what you did is worth more at renewal time than any dashboard.

For agencies and multi-location operators the same routine runs per listing, and the honest problem is that it multiplies. Twenty listings is twenty queues and twenty chances for a review to sit unanswered for a month. The fix is a single weekly session across all listings, one named owner per listing and one reviewer who reads everything before it goes up. If you are running this for clients, our page for agencies covers how listings and approvals work, and the free audit gives you a rated sample reply and the public reviews we can see for one location, so you can judge whether it is worth your time.

Where Ratingly fits

Ratingly drafts a reply to each new review as it arrives, in your voice. You approve, edit or skip each one. Nothing goes up without a person putting it up: we do not post replies automatically, and we would not want to, because the value of the reply is that a human checked the facts about what actually happened. We have read-only access to your Google reviews, so the reply is paste-ready: you copy it into the profile's reply box. On Yelp we monitor and draft, but posting stays manual.

That is a deliberate limit rather than a gap. A draft you paste is a draft you have read. What we remove is the blank page and the weekly decision about whether opening the dashboard is worth it at all. The how it works page has the sixty-second version.

How this differs from our other two guides

Three guides, three jobs, and they are meant to be read in a particular order. This one is the workflow and the rules: who may reply, the clicks, the anatomy of a reply, the policy edges, the weekly routine. How to reply to a 2-star review is phrasing for the moderate complaint - the handful of sentences that cover most of the awkward middle. How to reply to a 1-star review is the decision before the wording: when the right reply is three sentences or none, and how to move an allegation offline without looking evasive. Start here; go to the other two when you are stuck on one specific review.

Sources, and the dates we checked them

Read on 27 October 2026, from Google's public help pages: Manage customer reviews (reply, edit, delete); Manage your Business Profile owners and managers (who can respond, and what a manager cannot do); Report inappropriate reviews (the reporting standard); Prohibited and restricted content (incentives and fake content); Overview of Business Profile policies (profile-level restrictions); and Work with review data (the API creating and deleting replies).

Platform rules change. If you are reading this long after October 2026, check those pages yourself before acting on a specific case - and if a review is heading towards a legal or regulatory question, take advice on it rather than treating a help page as one.