App Store Review Response Guidelines: Apple vs Google Play, Side by Side

Apple and Google both allow exactly one public developer response per review, both let you edit it after you post, and both quietly forbid the same three things: personal data about the reviewer, promotional spam, and abuse. That's the shared floor. Past it, the two stores' review response guidelines split hard — on how long a reply can be, on whether the person who complained ever gets nudged to fix their star, and on what a link in the text even does.

Neither store publishes a single clean checklist, so here's the honest side-by-side: what each one lets you say in a response, what gets a reply pulled, and where a rule that sounds identical behaves completely differently in practice.

Start with the rules that don't change between stores — break one of these and the response can be removed on either platform, since a public developer reply is subject to each store's content policies. Three things are off-limits everywhere:

Here's where the two stores stop agreeing. Each line is one dimension of the response rules, Apple's behavior beside Google Play's. The character limit and the reviewer-notification loop are the two that most change how you write.

This one trips up support teams, and the honest answer is: you can type a URL, but it won't do what you want. On both stores a response is plain text — neither renders `…` as a tappable link, so the reader would have to copy it by hand. Inside Google Play's 350-character wall, a full support URL can eat a fifth of your reply for something nobody can click.

So the practical rule matches the personal-data rule: don't route people off-platform in the reply. If someone needs hands-on help, point them to in-app support as plain text ('reach us at Settings → Help') and keep the public reply on acknowledging the issue and naming the fix. Apple publishes no explicit 'no links' rule, but between plain-text rendering and the spam guidance, a reply full of URLs is a bad idea on both stores. If you do have a URL you think earns its place, [what links are allowed in a review reply](/blog/what-links-are-allowed) walks through the narrow cases where one is worth the characters. For the full store-by-store mechanics — APIs, notifications, what the reviewer sees — the companion reference is [reply rules for every app store](/blog/reply-rules-for-every-app-store).

One. Both stores give you a single response slot per review, not a conversation — but that response is editable. Update it later and the new text quietly replaces the old, which is handy when you promised a fix and it ships: come back and change 'we're on it' to 'fixed in 4.2.1.' Apple also lets you delete a response entirely from App Store Connect if you'd rather pull it than rewrite it.

The catch is notification timing. On Apple, updating your response can re-notify the reviewer — a feature, since a shipped-fix update gives them a fresh reason to raise their star. On Google Play, your reply arrives by email; editing it later doesn't guarantee a second one, so the first version is what most people read. Get the acknowledgement and the next step right the first time. The deeper differences between the two reply flows get the full treatment in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

That reply is compliance-clean on both stores: 194 characters (well inside Google's 350), no link, no personal data, no promotion, and it names the fix instead of arguing. It posts unchanged on Apple, where there's no cap, and on Google Play, where every character counts. This is the shape the research rewards — when Srisopha et al. (EASE 2021) ranked what makes a developer response actually move a rating, the strongest predictor was the length ratio between review and reply, ahead of politeness or speed. A tight, proportional answer beats a padded one.

Two of them, really. Google Play's 350-character wall forces a discipline — acknowledge, give the fix, offer one next step — that makes replies better, so writing to that cap and reusing the text on Apple is the sane default. And Apple's notify-and-update loop is why a reply is worth the effort at all: when Google introduced recency-weighted ratings at I/O 2019, it reported responding correlates with an average lift of 0.7 stars, and across 4.5 million reviews, users who got a response were roughly six times more likely to raise their rating (4.4% vs 0.7%, Hassan et al.). The rest of the guidelines are guardrails, not levers: stay inside them and the store leaves your replies alone; cross one and the reply can vanish. And if you're wondering whether an AI-drafted reply is even allowed here — it is, as long as a human owns the approval and the content follows the same rules; we cover exactly where that line sits in [is AI review reply against App Store policy](/blog/is-ai-review-reply-against-app-store-policy).

That's the map: one shared floor (no personal data, no spam, no abuse, no clickable links), one hard cap only Google publishes, and one notification loop only Apple wires into a one-tap rating change. [Start free with ReplyArgus](/signup) — no card — and Argus drafts your first Apple and Google Play replies in minutes, each one already inside the store's limit, clean of links and personal data, and written in the reviewer's own language.