How to reply to Google reviews

How do you reply to a Google review on Google itself?

You must verify your business before you can reply to reviews. If the Read reviews option is missing, verification is the first thing to check. After that the job takes under a minute.

1. Go to your Business Profile.
2. Select Read reviews.
3. Next to the review, select Reply.
4. Type your reply in the box.
5. Select Reply.

Those steps come from Google's own help page, Manage customer reviews. Google says replies usually take up to 10 minutes to review, but a review can sometimes take up to 30 days. The reply shows under the review as coming from the business, not from your own name, and the reviewer can still change their review afterward.

Google's developer documentation also caps a reply at 4,096 bytes. You will not hit that by accident. A good reply is a few sentences.

What should a reply to a Google review include?

Look, most owners overthink this. A good reply does four things and then stops.

• Thank them for what they said. "Thanks for the kind words" fits any review. "Glad the furnace was running before the cold snap" fits one.
• Mention one detail from the review. It shows a person read it, and it gives the next searcher a reason to believe you.
• Own the problem, if there was one. Say what went wrong in one sentence, with no excuses.
• Point to the next step. For a happy customer that is nothing. For an unhappy one it is a phone call, and you give the number only if your rules allow it.

Keep it to two to four sentences. And vary your openings. If every reply starts with "Thank you for your review", readers notice. So does OpenGMB: R6.duplicate stops a reply identical to one of the location's recent published replies, and R6.opening warns when the first sentence matches one.

Write the way you would talk to the customer at the counter. A name is fine if the reviewer used one. Sign off as the business.

What do good replies look like for 5-star, 3-star and 1-star reviews?

These are written for a made-up plumbing company. No real customer is behind them. Change the details to match your own job, and do not paste them as they are.

A 5-star review

A 3-star review

A 1-star review

Are there extra rules for healthcare and legal businesses?

Yes, and they matter more than tone. In healthcare, confirming that a reviewer was your patient can be a privacy problem even when the reviewer posted publicly. In law, a reply can imply a client relationship or promise results.

Healthcare: never confirm someone is a patient

Do not write "thank you for visiting us" or "glad you are feeling better", and say nothing about an appointment, treatment or recovery. Do not name a provider, a date or a condition. H1 stops wording that confirms or implies a care relationship.

For a 1 to 3 star review, the healthcare pack also asks for one fixed line: "To protect everyone's privacy we can't discuss details here, but we'd like to hear from you." H4.privacy-line stops a low-star reply that leaves it out.

Legal: no guarantees, no case facts

Do not write "thanks for choosing us as your attorney" or "your case". Do not mention a settlement, a verdict or a dollar figure, and do not promise results. The legal pack has LE1.relationship, LE2.case-facts and LE3.guarantee, plus LE4.testimonial. The pack is marked in our code as pending counsel review, so treat it as a safety net and not as legal advice.

None of this replaces your own compliance officer or attorney. I would not skip that conversation.

What mistakes get a reply rejected or cause harm?

The common ones are small and easy to avoid.

• A link. U7.url stops it. Your website is already on your profile.
• An email address. U7.email stops it, and it invites spam to the inbox you just printed in public.
• A hashtag. U7.hashtag stops it. A review reply is not a social post.
• An offer or discount. U7.offer stops promotions. A coupon under a 1-star review looks like a bribe.
• The same reply everywhere. R6.duplicate and R6.opening catch it, and readers catch it faster.
• Arguing the facts in public. You may be right. It still looks bad to the next reader.

OpenGMB checks these before a reply can be approved, and the rule id shows next to the text that tripped it. A blocking rule has to be fixed before the reply can go out. A warning can be approved once a person acknowledges it. Workspaces can change a rule's severity, so these are the defaults. Google Business Profile guardrails and approvals lists every rule pack.

How often and how fast should you reply?

I do not have a trustworthy number for the ideal response time, so I will not make one up. Here is what holds up without one.

• Reply to every review you can, including the 5-star ones. A short thanks counts.
• Reply to the low ratings first. An unhappy customer who sees nothing for weeks assumes you do not care.
• Pick a weekly slot and keep it. Fifteen minutes on Monday morning beats a big cleanup every quarter.
• Do not rush a hard one. A slow, calm reply beats a quick one you regret.

The one timing fact we can cite is on Google's side. Google says replies usually take up to 10 minutes to review, but a review can sometimes take up to 30 days. So do not panic if a reply is not visible yet.

New reviews sync into OpenGMB every 2 hours, and replies you make directly on Google are picked up too. That keeps a weekly slot easy: open the inbox and the unreplied reviews are on top.

How do you do this with OpenGMB?

OpenGMB puts every review from every location in one inbox. You write the reply or edit a draft, rules check it, and the approval rules you set decide who can send it. This is the same job as above, with the checks built in. For the full inbox, see Google review management.

Use the opengmb MCP server. Call reviews_list_unreplied for every active
location, newest first.

For each review, write a reply of two to four sentences. Thank the reviewer
for a detail they mentioned. Do not include a link, an email address, a
hashtag or an offer. Vary how each reply opens.

Save each one as a draft with reviewReplies_createDraft. Do not publish
anything. Then list the drafts so I can review them.

Sources: Google Business Profile Help, Manage customer reviews (read 2026-10-24). Google for Developers, Reviews reference (read 2026-10-12). Rule ids come from the OpenGMB guardrail packs.