Review policy and rating crises
Expert: with sources and numbers. Plain: the same, without them, for beginners.
What both platforms prohibit around ratings, where the line falls and what to do when a rating collapses for outside reasons.
40-08 covers the mechanics: prompt APIs, responses, the rating reset. This page covers the two things that get people into trouble: what is prohibited, and what to do when the rating drops for reasons that have nothing to do with the app.
What Apple prohibits
A Apple’s opening statement, verbatim: “If you attempt to cheat the system (for example, by trying to trick the review process, steal user data, copy another developer’s work, manipulate ratings or App Store discovery) your apps will be removed from the store and you will be expelled from the Apple Developer Program.” (App Review Guidelines, verified 2026-09-19)
A And specifically: “If we find that you have attempted to manipulate reviews, inflate your chart rankings with paid, incentivized, filtered, or fake feedback, or engage with third-party services to do so on your behalf, we will take steps to preserve the integrity of the App Store, which may include expelling you from the Apple Developer Program.” Same source.
A Guideline 5.6.3, Discovery Fraud: “Manipulating any element of the App Store customer experience such as charts, search, reviews, or referrals to your app erodes customer trust and is not permitted.” Same source.
A Guideline 3.2.2(vi): apps must not require users to rate or review the app (or watch videos, download other apps, tap advertisements or enable tracking) in order to access functionality or content, or to receive monetary or other compensation, including gift cards and codes. Same source.
Read 3.2.2(vi) carefully: the prohibition is on conditioning access or reward on the rating. That is the bright line.
Note also the word “filtered” in the manipulation clause. It appears alongside paid and fake, and that has a direct consequence. See gating, below.
What Google prohibits
A “Developers must not attempt to manipulate the placement of any apps on Google Play. This includes, but is not limited to, inflating product ratings, reviews, or install counts by illegitimate means.” (Ratings, Reviews, and Installs policy, verified 2026-09-19)
A The same policy prohibits offering rewards in exchange for positive feedback, such as a discount tied to a high rating, paid or automated fake installs, and fake reviews posing as users, including reviews containing affiliate links, coupons or promotional material for other apps. Same source.
Where the line actually falls
Allowed: asking every user to rate, at a moment of your choosing. Asking in the app description. Responding to reviews. Fixing the thing people complain about and asking again after.
Prohibited: paying for reviews. Incentivising a rating with anything of value. Conditioning features or rewards on rating. Using a service that generates reviews. Filtering who gets asked based on how they will answer.
The gating question. “Gating” means asking users how they feel first, then routing only the happy ones to the store prompt and the unhappy ones to a support form.
C It is widely practised and widely described in practitioner material, including the Advanced ASO e-Book reviewed here, which flags it as controversial.
It is not explicitly named in either policy. But Apple’s manipulation clause lists “filtered” feedback alongside paid and fake, and gating is filtering by definition. This base does not recommend it. If your organisation does it, that should be a decision someone made deliberately with the clause in front of them, not a pattern that arrived with a third-party SDK.
A defensible alternative that achieves most of the same thing: pick the trigger better. A Apple’s own guidance is to request when users are likely to feel satisfied, after completing an action, level or task (Ratings and reviews, verified 2026-09-19). Prompting after a success is selecting a moment, not filtering a person.
When the rating collapses and the app did not change
Rating drops that have nothing to do with a release: an outage during a high-traffic moment, a controversial product decision, a pricing change, a real-world event that makes people angry at you, or coordinated review activity.
A live sports app is unusually exposed, a failure during a major match produces a concentrated burst of one-star reviews from people who are all upset about the same twenty minutes.
What to do, in order:
1. Establish whether it is real. Volume, timing, and whether the reviews describe a genuine problem. A burst of one-stars describing a real outage is feedback, not an attack.
2. Fix the thing, if there is a thing. Everything below is worthless if the cause is still live.
3. Respond to the current-version reviews. A Apple notifies the reviewer when you respond, and the reviewer can then update their review (Ratings and reviews, verified 2026-09-19). This is the only documented mechanism that turns an existing bad rating into a better one. Prioritise recent, low-star, current-version reviews.
4. Report reviews that are actually abusive or fraudulent to Apple or Google, rather than responding to them. Reporting is the sanctioned route; retaliating in a public response is not.
5. Do not reach for the rating reset first. A It resets the summary rating but not the written reviews, and Apple advises using it sparingly because few ratings may discourage downloads (Ratings and reviews). After a genuine relaunch that fixed the complaint, it is reasonable. As a way to escape a bad month, you lose the volume that made the rating credible and keep the text that explains why it was low.
6. Remember ratings are per-territory on iOS. A Same source. A crisis in one market does not follow you into another, and a market-specific problem shows up as a market-specific rating, which is also a diagnostic.
7. Write down what happened. Date, cause, depth, recovery time. The second time this happens, the useful thing is knowing how long the first one took to recover.
What goes wrong
Buying reviews. Expulsion from the Developer Program is the stated consequence, not a warning.
Incentivising a rating. Prohibited on both platforms, explicitly.
Gating because a tool made it easy. “Filtered” is named in Apple’s clause. Decide it deliberately or not at all.
Responding angrily to a review bomb. Public, permanent, and covered by the Developer Code of Conduct, which asks you to treat everyone with respect in responses to App Store reviews.
Resetting the rating to escape a bad month. Keeps the reviews, loses the volume.
Not responding to the reviews that can still change. The current-version one-stars are the only ones a response can move.
In short
Every fact on this page in one line, with its evidence tier, source and verification date, 5 A. Generated from the claim register, so it cannot drift from the page above.
The mechanics of asking, replying and resetting live on their own page. This page covers the two things that actually get shop owners into real trouble: what's banned outright, and what to do when your rating drops for reasons that have nothing to do with your shop at all.
What one centre bans outright
Its own opening statement is blunt: trying to trick its own review process, steal a shopper's data, copy another shop's work, or rig your rating or how you're found gets your shop removed entirely and you personally banned from operating there again.
More specifically: trying to manipulate comments, or inflate your own board position with paid, incentivised, filtered, or fake feedback, including working with an outside service to do it on your behalf, gets the centre actively stepping in, up to and including removing you permanently.
Rigging any part of the shopping experience (the busiest-shops board, the desk's own answers, the comment book, or referrals) is named directly as a violation of trust and is simply not permitted.
You must never require a shopper to rate or comment (or watch something, download something else, tap an advert, or agree to being tracked) in order to unlock something, or to receive money or any other reward, including gift cards or codes.
Read that carefully: the actual ban is on conditioning access or a reward on the rating itself. That's the real, bright line.
Also worth noting: the word "filtered" appears right alongside paid and fake feedback in the rigging clause. That has a direct, practical consequence. See the section on quietly screening people below.
What the other centre bans outright
Trying to manipulate where any shop sits at all is banned, including (but not limited to) inflating ratings, comments, or visit counts through illegitimate means.
The same rulebook also bans offering any reward in exchange for a positive rating, paying for or automating fake visits, and fake comments posing as real shoppers: including comments carrying links, discount codes, or promotion for some other shop entirely.
Where the real line actually sits
Allowed: asking every single shopper to rate you, at a moment you choose. Asking inside your own writing. Replying to comments. Fixing whatever people are complaining about, then asking again afterward.
Banned: paying for ratings. Offering anything of value in exchange for one. Conditioning a feature or a reward on rating you. Using an outside service that generates comments for you. Quietly screening who even gets asked, based on how you expect them to answer.
The screening question. This means quietly asking a customer privately how they feel first, then routing only the happy ones on to the actual public prompt, and sending unhappy ones to a private support form instead.
It's widely practised, and widely written about, including material that itself flags it as controversial.
Neither centre names it outright by that description. But one centre's own rigging clause lists filtered feedback right alongside paid and fake, and this practice is filtering, by definition. This guide does not recommend doing it. If your own organisation does it anyway, that should be a decision someone made deliberately, with that exact clause in front of them. Not a habit that simply arrived bundled inside some outside toolkit.
A genuinely defensible alternative that achieves most of the same goal: simply pick a better moment to ask everyone. The advice already covered elsewhere is to ask right when someone's likely to feel genuinely satisfied: right after finishing something, completing a task, or reaching a milestone. Asking after a genuine success is choosing a moment. Screening is filtering a person. The two look similar and are not the same thing at all.
When your rating collapses and your shop didn't actually change
Some drops have nothing to do with anything you shipped: an outage during your busiest possible moment, a controversial decision, a pricing change, some real-world event that's made people angry at you specifically, or coordinated, organised comment activity aimed at you.
A live sports shop is unusually exposed to this. A failure during a major event produces a concentrated burst of very low comments, all from people upset about the exact same short window of time.
What to actually do, roughly in order:
Work out whether it's genuine first. Look at the volume, the timing, and whether the comments actually describe a real problem. A burst of low comments describing a genuine outage is honest feedback, not an attack.
Fix the actual thing, if there is one. Everything that follows is worthless while the real cause is still live.
Reply to comments about the current version. The shopper gets told when you reply, and can then revise what they originally wrote. This is the only documented mechanism that actually turns an existing bad comment into a better one. Prioritise recent, low, current-version comments specifically.
Report anything that's genuinely abusive or fraudulent to the centre itself, rather than replying to it publicly yourself. Reporting is the sanctioned route; arguing back in public is not.
Don't reach for wiping your number clean first. It resets the visible number but not the written comments themselves, and the centre's own advice is to use it sparingly, because too few ratings can itself put people off. After a genuine relaunch that actually fixed the complaint, it's a reasonable move. As a way to simply escape one bad stretch, you lose the volume that made your number credible and keep every word explaining why it was low.
Remember ratings sit separately per country on the locked side. A crisis in one place doesn't follow you into another, and a country-specific problem shows up as a country-specific number, which is itself a useful diagnostic tool.
Write down what actually happened. The date, the cause, how deep it went, and how long recovery took. The next time this happens, the single most useful thing you can have is knowing exactly how long the first one took to recover from.
What tends to go wrong
Paying for ratings. Being removed permanently is the stated consequence here, not merely a warning.
Offering any reward for a rating. Explicitly banned on both sides.
Screening customers just because a tool made it easy. "Filtered" feedback is named directly in one centre's own rulebook. Decide it deliberately, or don't do it at all.
Replying angrily to a coordinated pile-on. Public, permanent, and covered by the same code of conduct that asks you to treat every single person with respect in a reply.
Wiping your number clean just to escape one bad stretch. Keeps every comment, loses all the volume.
Not replying to the comments that can still actually change. Recent, low, current-version comments are the only ones a reply can genuinely move.