Google Play ratings and reviews manipulation: incentivised installs, fake reviews and rating prompts done wrong

Google believes your ratings, reviews or install numbers were not earned. That covers paid review services, offering five stars in exchange for something, gating a feature behind a rating, and install-farm traffic you may have bought without realising what you were buying. It is enforced hard, and tends to produce suspensions rather than rejections.

How it is worded

A policy email, usually citing the policy by name and sometimes naming the mechanism:

"We detected an attempt to manipulate your app's placement on Google Play."

"We have detected invalid or fraudulent ratings, reviews, or install activity associated with your app."

Enforcement often arrives with the affected reviews already deleted and your rating already moved. Google removes what it judges invalid whether or not it acts against the app.

What it means

The policy's core sentence is broad on purpose:

"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, such as fraudulent or incentivized reviews and ratings, or incentivizing users to install other apps as the app's main functionality."

The listed violations are specific:

• Offering a discount or reward in exchange for a high rating.
• "Repeatedly submitting ratings posing as users to influence an app's placement on Google Play".
• "Submitting or encouraging users to submit reviews containing inappropriate content, including affiliates, coupons, game codes, email addresses, or links to websites or other apps".
• Using automated services to inflate installs or ratings.

What is allowed is stated just as plainly. You may "Prompt users to leave a rating in a clear, non-deceptive way". You may not use "deceptive pop-ups or force users to rate your app".

So the line is not "never ask". Ask honestly, do not pay for the answer, and accept whatever answer you get.

Why it happens

Only the first two of these are deliberate.

• You bought reviews or installs. Including from a service that called itself marketing, user acquisition, or "app store optimisation with guaranteed ranking". If a vendor promised installs at a fixed price with a ranking outcome, that was this.
• A growth campaign rewarded the rating, not the install. In-game currency for a five-star review, a coupon for feedback on Play, a prize draw entry for a rating. Rewarding the review is the violation even where the reward is trivial.
• Your prompt asks for stars conditionally. An in-app dialog asks "Are you enjoying the app?", then routes happy users to Play and unhappy users to a support form. That filters the sample, and it fails the non-deceptive test.
• The prompt is coercive. A rating request that cannot be dismissed, reappears on every launch, or blocks a feature.
• You told users what to write. Suggested text, a five-star graphic next to the button, or a request to mention a keyword. Reviews containing coupon codes come from developers asking for them.
• Employees, friends and family reviewed the app. Reviews from accounts connected to you are invalid, and a first-week cluster of five stars from one region and device model is visible.
• You used a review-swap group. Reciprocal reviewing among developers is the same violation with a friendlier name.
• You did not buy anything and were hit anyway. Install fraud is sometimes committed by an affiliate network in your chain, or by a competitor. This is the case where an appeal is genuinely worth making.

How to fix it

1. Stop every campaign that touches ratings, reviews or installs today. Pause the ad network, cancel the vendor, disable the reward. Do this before you write anything to Google, because the first question is whether the activity is still running.
2. Audit your acquisition sources. List every network, affiliate and partner sending installs. For each, check what they pay on and how they source traffic. Cut anything you cannot describe accurately, and record when you cut it.
3. Rip out conditional review routing. One prompt, no pre-qualification question, no branching. If you want private feedback, offer a support link alongside the rating request rather than in place of it.
4. Move to the In-App Review API. Google's own flow keeps the review inside your app, cannot be forced, and enforces its own frequency quota so you cannot over-ask. It removes most of the ways this policy gets broken by accident.
5. Remove every reward tied to a rating or review. Rewards tied to using the app are fine. Rewards tied to what a user says about it are not.
6. Take the ask out of your description and screenshots. No "please rate us five stars", no rating-count claims you cannot stand behind.
7. Check the in-app currency and referral mechanics. Incentivising users to install other apps as your main functionality is named in the policy. If your core loop is "install these to earn credits", the app itself is the violation.
8. Look at your other apps. Cross-promotion between your own titles is where this spreads.

Appeal, or fix and resubmit?

Know which action you received. A rejection means the release did not publish and your account standing is untouched. A removal takes the live version down. A suspension counts against your developer account, and repeated suspensions put the account itself at risk. Ratings manipulation is treated as fraud, so it reaches the harder end faster than most policies.

Appeal when the traffic was not yours. This is the one enforcement where a strong appeal is common, because install fraud is frequently done to a developer rather than by one. Give the reviewer facts: which networks you use, what you spend, the install and rating curve with dates, the point where the anomaly starts, and what you have shut off. If a partner was responsible, name them and give the date you terminated them.

Do not appeal if you paid for it. Even a small test with a review vendor two years ago is in the data Google is looking at, and you get one appeal per enforcement action.

If you are unsure what a vendor actually did, say so rather than guessing. "We contracted [vendor] for user acquisition in March, we were told traffic was incentivised installs from their own app, we terminated the contract on [date]" is a credible appeal. A confident denial that turns out to be wrong is not recoverable.

You cannot see what Google saw. There is no report showing which reviews were judged invalid or which installs were discounted. Play Console will show the rating change but not the reasoning, and any page claiming to know the detection threshold is guessing.

AppSubmit's review inbox pulls your Play and App Store reviews into one list so you can spot an unnatural cluster early. It will not write or solicit a review for you, and that is a deliberate omission rather than a missing feature.