How to Respond to Google Play Reviews

How Google Play Replies Actually Work

A developer replies through the Play Console (or the Developer API, for teams replying at scale). The reply is capped at 350 characters — a hard limit confirmed in Google's own documentation, and meaningfully tighter than a customer-review platform like Google Business Profile. The first reply triggers a push and email notification to the reviewer, and reviewers can update their rating after reading a reply — Play Console tracks this explicitly, which makes a well-written reply a genuine rating-recovery lever, not just a courtesy.

How to Respond to a Negative Google Play Review

App reviews are usually about something specific and fixable — a crash, a bug, a confusing screen, a billing issue. Reference it directly and, if it's genuinely fixed, say so and point to the version: "Fixed in v2.4 — please update and let us know if it persists" does more in fewer characters than a generic apology, and it's the reply most likely to bring the reviewer back to update their rating.

Google Play Review Response Examples

How to Respond to Positive Google Play Reviews

Short and genuine works well within 350 characters — thank the user and, where relevant, mention what's coming next. It doesn't need to be long to feel real.

Google Play 5-Star Review Response Examples

Google Play Review Response Templates

Because of the 350-character limit, keep a template close to how it'll actually be posted rather than something meant to be expanded.

How Long Should a Google Play Response Be?

As close to the 350-character limit as you need, and no longer than that — it's a hard cap, not a guideline. A specific, actionable reply (what's fixed, what version, what to do next) fits comfortably; a generic apology wastes characters better spent on something useful.

What Should You Never Say in a Google Play Response?

Never claim a bug is fixed if it isn't — reviewers who update after a reply and find the same bug are more frustrated than before. Never ask for personal information in a public reply. Never solicit a rating change directly; let a genuinely useful reply do that on its own.

What If Responding Isn't Enough?

A good reply can genuinely move a reviewer to update their rating — that's Google Play's own documented mechanic. But it doesn't retroactively change ratings from users who never come back to read it. If the underlying problem is a damaged rating across many reviews, that's a review-volume question worth solving alongside good responses.