AppReviewFix
Guideline library
Google Play — Store Listing

Ratings & Reviews — User ratings, reviews, and installs

Official source: Google Play Developer Program PoliciesTopic overview: The review process, app quality and enforcement
What this guideline means

This covers the review/rating ecosystem itself — fake reviews, review-bombing coordination, bot-generated ratings, and asking users to leave a specific star rating in exchange for anything of value.

Why apps actually get flagged

Frequently triggered by an in-app prompt that explicitly steers users toward leaving a 5-star review only if they're happy (and silently redirects unhappy users to a feedback form instead), which Google treats as manipulating the public rating.

A real example

"Your app's rating prompt selectively filters user sentiment before directing users to the Play Store, which violates the User Ratings, Reviews, and Installs policy."

The short version, in more detail

This policy covers the review and rating ecosystem as a whole: fake reviews, coordinated review-bombing, bot-generated ratings and asking users to give a specific star rating in exchange for anything of value. A well-known trigger is a prompt that asks users if they are happy, sends happy users to the store and quietly redirects unhappy ones to a private feedback form.

Why this rule exists

A rating is only useful if it reflects the range of real experience. Filtering who can leave a review or paying for a specific score hides problems and misleads people about quality. At the other end, coordinated attacks can unfairly damage honest apps. By addressing both inflation and abuse, the policy seeks to keep ratings representative, which benefits users and developers who earn their scores.

What this guideline covers

  • Fake, paid or automated reviews.
  • Coordinated attacks on ratings.
  • Incentives linked to ratings and installs.
  • In-app rating prompts and how they are designed.

What usually triggers this rejection

  • Directing only satisfied users to the store while sending others elsewhere.
  • Rewards for leaving a high rating.
  • Bot or farm-generated reviews.
  • Organised campaigns to lower a competitor's score.
  • Fake installs used to boost ranking.

How reviewers evaluate it

  • Systems look for unnatural patterns in ratings and installs.
  • Reviewers examine the logic behind rating prompts.
  • Reports from users and developers are investigated.
  • Violations can lead to removal of ratings and policy action.

Common misunderstandings

  • Review gating is not allowed even when it sounds like customer service.
  • Asking for feedback is fine. Controlling who rates is not.
  • Negative reviews cannot be removed just because they are unfavourable.

Common questions

Can I use an in-app rating prompt?

Yes, if it is shown to users generally and not filtered by sentiment.

Are incentivised installs part of this?

They are covered together with ratings and promotion rules.

What if I am the target of review-bombing?

Google provides ways to report abuse of the review system.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current Google Play Developer Policy Center for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
1.5 — Developer informationStrikes System — Policy strikes and enforcement escalationAccount Integrity — Developer account integrityApp Promotion — App promotion and incentivized installsMisrepresentation — Store listing and ratings misrepresentation
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.