Google Reviews
How Long Should a Google Review Reply Be?
Somewhere between a curt "thanks!" and a five-paragraph essay is the length that actually works. A practical guide to sizing a reply to the review it's answering — and why word count matters far less than what's in it.
Updated 13 August 2026 · 5 min read
There's no ideal word count — there's an ideal fit
Business owners searching for a length rule are usually hoping for a number: fifty words, three sentences, one paragraph. There isn't one, because the right length depends entirely on what the review actually says. A five-star review that reads "Great service, will be back!" doesn't need six sentences in reply — matching its brevity looks natural, not lazy. A detailed, multi-point complaint deserves more than a one-liner, because a short reply to a long, specific grievance reads as dismissive.
The useful question isn't "how long should this be" — it's "does this reply actually address what the reviewer said." Length that follows from that answer is almost always the right length.
Why shorter usually wins for routine reviews
Most reviews a business receives are short, positive, and unremarkable in the best way — a happy customer saying thanks in a sentence or two. A reply of similar length, personalised with something specific from their visit, reads warmly and gets read in full by everyone who scrolls past it. A long, effusive reply to a short review can actually undercut the impression: it reads as performative, or as a template stretched to fill space regardless of what the review said.
For everyday five-star reviews, two or three sentences is usually plenty: a genuine thank you, one specific detail that shows you actually read it, and — if it fits naturally — a light invitation to come back.
When a longer reply earns its length
A longer reply is justified when the review itself is longer or more complicated — several distinct issues in one post, a serious complaint, or a situation where future customers reading the exchange need enough context to trust it was handled properly. In these cases, brevity can look like you skimmed the review rather than engaged with it.
A useful test: if you can't address the actual substance of what the reviewer raised in two sentences without leaving something important unanswered, the reply is allowed to run longer. What it shouldn't do is pad — repeating the same apology in different words, or re-explaining a policy the reviewer didn't ask about.
A rough sizing guide, by review type
As a starting point, not a rule:
- Short, positive, generic ("Great job, thanks!") — one to two sentences. Thank them, add one specific detail if you can.
- Positive with specific detail (names a service, a staff member, a result) — two to three sentences, matching that specificity back.
- Negative, single clear issue — three to four sentences: acknowledge, apologise for the experience, say what you're doing about it, invite them offline.
- Negative, multiple issues or a serious complaint — four to six sentences, enough to show you've read and understood each point, still moving toward a private follow-up.
- No comment, star rating only — a short, friendly line is enough; there's nothing specific to respond to.
The trap of a reply that's long because it's defensive
The length problem worth actively watching for isn't padding — it's a reply that's grown long because it's arguing. A business defending itself point-by-point against a negative review, relitigating a quote, or explaining every mitigating circumstance in detail tends to write long replies for the wrong reason. Length driven by defensiveness reads worse the longer it runs, because every extra sentence is another chance to sound like you're contesting the reviewer rather than addressing them.
If a reply is getting long, it's worth checking why: is it long because there's genuinely more to acknowledge, or long because you're trying to win an argument in public? The second is better handled with a shorter, calmer reply and the detail moved to a private conversation.