Write a long, careful reply to a tough review, hit submit, and get an error saying it's too long. Or worse: post it, feel good about it, and never notice that Google folded most of it behind a small "More" link nobody taps. A reply that's the right length gets read; one that isn't gets rejected outright or ignored behind a fold, and fixing both problems just takes knowing where the real limits actually sit.
The quick answer
Google's reply box stops accepting new text at right around 4,000 characters, a limit nobody publishes officially but that shows up the moment you cross it. That hard cap almost never matters, because the limit that actually decides whether anyone reads your reply is much shorter: on both the Maps app and desktop, a reply longer than a few lines collapses behind a "More" link. The practical target for most replies is 20 to 90 words depending on what you're responding to, with the actual point landing before that fold, not after it.
Google's actual character limit
Google doesn't publish an official maximum for owner replies anywhere in its Business Profile help center. The number comes from owners hitting it, not from a spec sheet, which is why it shows up in community forum threads and SEO testing rather than in any support article.
A second figure, 4,096 characters, shows up in a handful of explainer roundups, but nobody has reproduced it with an actual test. Treat 4,000 as the real ceiling and anything above it as noise. Either way, a reply anywhere near that length has already gone wrong for reasons that have nothing to do with the character counter.
The limit that actually matters
The character cap is a wall you'll basically never hit. The limit that decides whether a customer actually reads your reply is Google's own display, not its character counter. On the Google Maps app and on a Business Profile listing in Search, a reply longer than a few lines gets truncated behind a small "More" link, and most people scanning a business's reviews never tap it.
How long a reply should be, by review type
Length should scale with what you're actually responding to, not with how strongly you feel about it. Matching the reply's weight to the review's weight is what keeps it from reading as either dismissive or defensive.
- 5-star, no real complaint (20 to 40 words): Thank them by name, reference one specific detail from their review, done. Anything longer starts to read as automated.
- Star rating only, no text (15 to 25 words): There's nothing specific to react to, so keep it short and generic-but-warm. A longer reply here reads strange when you have nothing from the reviewer to respond to.
- 3-star or a fixable complaint (60 to 90 words): Acknowledge the specific issue, skip the defensiveness, say what you're doing about it. This is the length band where owners most often write too little (dismissive) or too much (defensive).
- Serious complaint or a factual dispute (up to roughly 130 words, resolution first): The one case where more length is warranted, but the shape matters more than the count. State what actually happened or what you're doing about it in the first sentence, then add supporting detail after it, since the fold cuts off the same way regardless of how important the reply is.
A two-check rule before you post
Rather than counting words while you type, run every draft past two quick checks before you hit submit.
- The fold check: read only the first sentence on its own. If it doesn't already say thank you, acknowledge the issue, or state the fix, move that part to the front. Assume most readers never see anything after it.
- The type check: match the word count to the review type above. A three-paragraph reply under a two-line review reads as overcompensating no matter how well it's written.
“The reviewer wrote three lines. Your reply doesn't need to out-talk them to prove you care.”
Three ready-to-adjust templates
Start from the length band that matches your situation, then swap in the specifics.
Thanks so much, [Name]! Really glad the [specific detail, e.g. install crew] worked out for you, comments like this make our week. Hope to see you again soon.
[Name], thank you for the honest feedback, and I'm sorry the [specific issue] wasn't up to what we aim for. That's on us, not you. We've [specific fix or step being taken], and I'd like the chance to make this right. Please reach out directly at [contact] so we can sort it out.
[Name], we looked into this, and [state the actual resolution or correction in one sentence first]. [Add the specific detail or correction next, for example an appointment or records discrepancy], and [what you're doing about it going forward]. We take reviews like this seriously, and we'd welcome the chance to talk it through directly at [contact] if anything here doesn't match what you experienced.
Too long, or want to change it later?
If a reply gets rejected as too long, trim from the middle, not the opening line, since the opening is the part that shows before the fold and is worth keeping intact. Cut supporting detail and repeated apologies first.
It also helps to remember replies aren't permanent the moment they post. Owner replies can be edited or deleted after the fact, the same way the original review can be, so getting the wording flawless on the first try matters less than getting the length and the opening sentence right. For reviews that are hard to word for reasons beyond length, a fake review, a one-star with no comment at all, or one that needs a careful factual correction, see how to respond to fake reviews and what to do with a no-comment 1-star.
If getting the length and tone right every time feels like one more thing to track on top of actually running the business, that's the exact gap Google review automation is built to close: replies come out already sized to the review, a two-line thank-you or a longer one on something that needs care, and anything genuinely sensitive waits for a one-tap OK instead of posting on its own. Try it free on a real review in the reply generator, browse the full template library for more starting points, or check current pricing.