Google Play misleading Claims policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps with inaccurate feature, affiliation, category, or capability claims.
Calling an app a prank doesn’t make an impossible feature claim acceptable. Google expects the title, screenshots, description, and app itself to describe functionality that actually exists.
What to check
List the claims in your marketing and demonstrate each one in the submitted build. A guide about antivirus software isn’t itself an antivirus scanner. Check claims of government affiliation, official status, and authorization too.
Review the selected category and rating. Also inspect localized listings: an accurate English description doesn’t fix an exaggerated translation.
How to address the rejection
Remove claims you can’t substantiate and replace misleading screenshots with the actual experience. If the feature is possible but missing from the submitted build, implement and test it before describing it as available.
For an affiliation claim, provide the relevant authorization or remove the claim and associated branding. In your response, point to the changed listing fields and the feature reviewers can now verify. Avoid replacing a precise false promise with another vague promise that still implies the same capability.
Messages this guide can help with
Misleading Claims; Misleading Claims policy violation; Misleading Claims rejection; Misleading Claims denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Misleading Claims Checked 22 September 2026