What Links Are Allowed in App Review Replies? (Google Play vs Apple)

On Google Play you can point a reviewer to a support address or a help/FAQ page (Google's own reply best-practices actually recommend it), but promotional, affiliate, or referral links are off-limits and can get the reply removed. On the App Store, Apple publishes almost nothing specific about links and tells you to keep responses free of marketing language, personal information, and spam, so the safe move there is to keep replies text-first with at most a plain pointer to your normal support channel.

That's the whole answer, and the nuance under it is what keeps a reply from getting flagged. The published guidance is thinner than most developers assume, and one of the strictest "no links" rules floating around actually belongs to a different Google product entirely. Below is what each store really allows, what gets a reply rejected, and how to reference help without tripping a spam filter, plus the space constraint we cover in [writing a 350-character review reply](/blog/write-a-350-character-review-reply).

Google Play's public guidance on developer replies is short. The Play Console best-practices tell you to keep the reply focused on the issues the user raised, avoid asking for a higher rating, and "include references to helpful resources such as a support address or FAQ page." That last line is the clearest green light you'll get: a support email and a link to your own help or FAQ page aren't just tolerated, they're the recommended pattern.

What Google does not want is a reply used as an ad. The Play content policies that govern reviews and replies prohibit promotional or commercial content, affiliate and referral links, coupons or game codes, and off-topic spam. So the line isn't "links vs no links," it's "helping this reviewer vs marketing to the thread." A link to your support portal helps the person who wrote the review; a link to a discount page, a referral program, or another of your apps is promotion, and that's the reply that gets pulled.

One clarification, because it trips people up: you'll find guidance online stating flatly that Google bans phone numbers, email addresses, and links in replies. That rule is real, but it belongs to the Google Workspace Marketplace, a separate developer surface, not the Google Play app store. Don't apply the Workspace rule to your Play replies; for Play apps, a support address and a help link are on the recommended list.

Replies are subject to the same content policies as reviews, and Google can remove one that crosses a line. The link-related triggers are consistent and easy to avoid once you know them:

Notice what's absent from that list: a support address and a link to your own help center. Those are the sanctioned exceptions because they serve the reviewer directly. The test is simple: if the link exists to help *this* person with *this* complaint, you're fine; if it exists to sell to everyone reading, you're not.

That reply is safe on either store: it references support without pasting a promotional URL, stays on-topic, doesn't beg for a rating change, and lands at 288 characters, inside Google Play's 350-character wall. It routes the reviewer to help by naming the path ("Settings › Help") instead of burning characters on a raw link.

Apple is quieter and, in effect, stricter. It doesn't publish a link-specific rule for review responses, but its guidance is to keep the reply respectful, concise, and free of personal information, marketing language, and spam. "No marketing language" is the operative phrase for links: a promotional or affiliate URL is marketing by definition, so it's out. A bare pointer to your support channel is generally reasonable, but Apple gives you far less explicit cover than Google's "support address or FAQ page" recommendation does.

There's also no officially published character limit on App Store replies. Community testing has suggested anywhere from a few thousand up to roughly ten thousand characters, and those numbers disagree, so treat "a few thousand" as a soft ceiling, not a hard fact, and never rely on a specific number. The extra room tempts you to paste links; resist it and keep the reply text-first. If you run both stores, the differences in limits, notifications, and tone are laid out in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies), and the per-store specifics live in our [reply rules for every app store](/blog/reply-rules-for-every-app-store).

Usually, no — even when it's allowed. A link in a reply carries three quiet costs: it burns characters you don't have on Play, it reads as marketing to the store's spam heuristics even when it's innocent, and it dead-ends if the URL changes. Naming the support path in plain words does the same job with none of the risk. Reserve an actual URL for the rare case where the destination is genuinely a self-serve fix, a help article that resolves the exact bug, and even then keep it to your own domain.

The bigger problem isn't which link to use; it's doing this across every review, in every language, without a reply sitting untouched for a week. [ReplyArgus](/features) watches your Apple App Store and Google Play reviews in one inbox and drafts each reply grounded in your past approved replies and store listing, so the support pointer is phrased your way, stays inside Play's 350-character cap automatically, and never smuggles in a promotional link. You approve by default and opt into rule-based auto-publish for the safe ones. Responding at all is what moves the needle: Google reported an average 0.7-star lift when developers reply (I/O 2019), and across 4.5 million reviews users who got a response were roughly six times more likely to raise their rating (Hassan et al.). More on that in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).

When a reply needs to route someone to support, this order stays clean on both stores:

Strip the noise and the rule is short: help the reviewer and you're fine; sell to the thread and you're not. Support addresses and your own help links are allowed, and on Google Play recommended, while promo, affiliate, and cross-app links get replies pulled. Apple wants the same restraint with less written down. [Start free with ReplyArgus](/signup), no card, and Argus drafts your first Apple App Store and Google Play replies in minutes, in the reviewer's own language, inside every store's limit, with the support pointer done right and no promotional link to get you flagged.