Owner playbook · 2026-05-08
How long should a Google review reply be?
Short version: most owners write reply length backwards. Long template-y replies for short 5-stars, two-sentence dismissals for detailed 1-stars. The fix is intuitive once you see the table.
The rule of thumb (with the data)
Reviewers are talking to you. Future readers are reading the thread. Your reply length should match what each audience needs:
| Review type | Optimal reply | Why |
|---|---|---|
| 5★ short ("Great!") | 10-25 words | Don't over-thank; sounds desperate |
| 5★ detailed (paragraph) | 25-60 words | Mirror their effort; reference one specific thing |
| 4★ ("Good but…") | 30-70 words | Acknowledge "but" honestly; specific fix |
| 3★ (mixed/lukewarm) | 40-80 words | Hardest one — thoughtful response signals care |
| 2★ (legitimate complaint) | 50-90 words | Concrete apology + concrete remedy |
| 1★ legitimate | 60-120 words | Name the failure; offer email path off-platform |
| 1★ vague drive-by | 25-50 words | Ask for details; don't accuse publicly |
The pattern: negative reviews need more words than positive ones, and detailed reviews need more words than short ones. Most owners do the opposite.
Why short replies for short 5-stars
The over-replied version that backfires:
Future readers see this and think "this owner is hungry." It's long, generic, and reads as marketing copy. Worse, the next 10 reviews probably get the same template.
The version that lands:
First-name. Brief. Warm. The next reviewer sees an actual person replied, not a marketing department.
Why long replies for legitimate 1-stars
The dismissive too-short version:
Reads like a brush-off. The reviewer feels unseen. Future readers see a hotel that doesn't engage with real complaints.
The version that earns trust:
Acknowledged the specific failure. Owner-signed. Concrete remedy offered. Future readers see professionalism instead of corporate deflection.
The 30-word floor for any reply
Even the shortest 5-star reply should clear about 8-10 words — long enough to show it isn't a bot. Anything under 5 words ("Thanks!" alone) reads as automated. Even a tiny bit of personalization tips it back to human:
- "Thanks Mark — glad you came." (6 words, but personal)
- "Thanks!" (1 word — looks scripted)
The 200-word ceiling
Above 200 words you're writing a press release, not a review reply. The reader scans the first two sentences and bounces. Long replies almost always have one of these problems:
- Multiple paragraphs of generic apology before the actual remedy
- Defending the property against the complaint ("however, our policy is...")
- Self-promotion bolted on ("We're proud to be a top-rated property in...")
If you're past 150 words, cut. Specifically: cut everything that isn't (1) a specific acknowledgment, (2) ownership of what went wrong, or (3) a concrete next step.
Sanity check before you publish
Read your draft out loud. If it sounds like a corporate press release, it is. Rewrite as if you're talking to one person, not every potential customer who'll ever read it.
Or: paste your draft into our free Reply Roaster. It scores 0-100 against defensive-cliché patterns and tells you exactly which words to cut. No signup.
Stop second-guessing reply length
ReviewHub drafts replies at the right length for each review type — automatically. You approve, we post.
Get a free audit →Related posts: Why your Google reviews need owner replies · 5 Bangkok hospitality review mistakes