Guide
How to Reply to Google Play Reviews (Console & API)
Step-by-step: answering Play Store reviews in the Play Console, the 350-character limit, what you can and can’t reply to, and how developers automate replies through the official Google Play Developer API.
Quick answer: Play Console → your app → Ratings and reviews → Reviews → Reply. Replies are capped at 350 characters, the reviewer is notified, and they can update their star rating after reading your answer. Developers with more than a handful of reviews automate the same flow through the official Google Play Developer API.
Replying in the Play Console, step by step
- Open your app in the Play Console. Sign in at play.google.com/console with an account that has the “Reply to reviews” permission and select the app.
- Go to Ratings and reviews → Reviews. The left-hand menu lists every user review. Filter by star rating, language, or app version to find the ones that need an answer first.
- Select a review and write your reply. Click Reply under the review. You have 350 characters — address the specific problem, skip the boilerplate greeting, and point detailed troubleshooting to your support email.
- Submit. The reply is published under the review on your public store listing, and Google notifies the reviewer that you responded.
- Watch for the rating update. The reviewer can revise their review and star rating after reading your reply — this is where responding pays off, especially on recent negative reviews.
The rules worth knowing before you type
- 350 characters, hard limit. Longer replies are rejected, not trimmed. See our guide to the Google Play reply character limit for how to write under it without sounding curt.
- One reply per review, editable any time. You can’t thread a conversation — if the issue needs back-and-forth, move it to your support email and update the reply once it’s resolved.
- Only reviews with text can be answered. Star-only ratings have no reply button, in the Console or the API.
- Stay inside Google’s comment policies. No incentives for changing a rating, no asking for personal data in public, and keep it civil even when the review isn’t — the reply is permanent public record on your listing.
What actually makes a reply work
Google’s own Play Console page notes that users who update their rating after a developer response raise it substantially on average — we’ve collected the published numbers here. The replies that earn updates share a pattern:
- They answer the specific complaint, not a generic “thanks for your feedback”.
- They’re written in the reviewer’s language.
- They arrive fast, while the reviewer still has the app installed and still cares.
- They follow up: when the bug is fixed, the reply gets edited to say so — often the moment a 1-star becomes a 4-star.
If you’d rather not write each one from scratch, start from our free review reply templates — every one already fits the 350-character limit.
Replying at scale: the official API
Everything above is also available programmatically. The Google Play Developer API exposes reviews.list and reviews.reply — the same operations the Console UI performs — authenticated with a service account you create in your own Google Cloud project and grant the “Reply to reviews” permission in the Play Console.
Two API quirks matter in practice. First, the API only returns roughly the last seven days of reviews, so any tool that polls infrequently will miss reviews entirely. Second, it returns only reviews with text — consistent with the no-reply rule for star-only ratings.
This is exactly the plumbing StoreReplies runs for you: it polls through the official API every 15–60 minutes, drafts a reply to every new review in the reviewer’s language, and publishes through reviews.reply when you approve — from an inbox instead of the Console, with your credential stored in Google Cloud Secret Manager. The Google Play page covers the details.