AppReviewFix
Guideline library
Google Play — Trust & Safety

Misrepresentation — Store listing and ratings misrepresentation

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

This targets manipulation of your app's public reputation specifically — paying for reviews, offering in-app rewards for positive ratings, or using bots/review farms — as distinct from deceptive UI tricks elsewhere in the app.

Why apps actually get flagged

Most often caught when an app prompts users with an in-app reward ("get 100 coins for a 5-star review") tied directly to leaving a rating, which Google's review-quality systems detect at scale.

A real example

"We found that your app offers incentives in exchange for positive ratings or reviews, which violates the Misrepresentation policy."

The short version, in more detail

This policy is about manipulating an app's public reputation. It prohibits paying for reviews, offering in-app rewards for positive ratings and using bots or review farms. It is separate from deceptive interface patterns elsewhere in an app. An in-app prompt that offers coins for a five-star rating is a typical trigger, because review-quality systems can detect these at scale.

Why this rule exists

Ratings and reviews are how people judge an app before they install it. If they can be bought or steered, they stop being a reliable signal and users make worse decisions. Honest developers are disadvantaged when competitors inflate their scores. The policy aims to keep the review system a reflection of real user experience, which is the main reason people trust it.

What this guideline covers

  • Paid, incentivised or fake reviews.
  • Rewards tied to leaving a rating.
  • Bots and review farms.
  • Misleading information about an app's reputation.

What usually triggers this rejection

  • Offering in-app currency for a five-star rating.
  • Paying a service for positive reviews.
  • Using bots to post ratings.
  • Prompting only satisfied users to rate.
  • Fabricated testimonials in the listing.

How reviewers evaluate it

  • Detection systems look for unnatural review patterns.
  • Reviewers examine in-app prompts for ratings.
  • Reports from users and developers contribute.
  • Violations can lead to removal of reviews and enforcement.

Common misunderstandings

  • A reward for leaving a rating is not allowed even if the rating is honest.
  • Small incentives still count.
  • Asking for feedback is fine. Buying a particular score is not.

Common questions

Can I ask users to rate my app?

Yes, as long as it is not tied to a reward or steered toward positive scores.

Is it the same as the Ratings policy?

They overlap. This one focuses on the store listing and ratings reputation.

How are fake reviews found?

Through detection of patterns and reports.

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
2.3.3 — Screenshot accuracy2.3.4 — Preview requirements2.3.5 — Appropriate category selection2.3.6 — Honest age rating2.3.8 — Metadata appropriate for all audiences
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.