Where to find the reason
Play Console shows rejections in the inbox and on the Policy status page, with the policy name and often a screenshot. Google lists all policies in the Developer Policy Center.
The most common causes
- Metadata policy: keyword stuffing, misleading titles, "best" or "#1" claims.
- Data safety: the form doesn't match what your app or SDKs collect.
- Permissions: SMS, call log, background location or all-files access without approval.
- Target API level: updates blocked for targeting an old Android version.
- Closed testing: new personal accounts must test before production.
Rejected vs removed vs suspended
A rejection blocks a submission; your live version stays. A removal takes the app off Play until fixed. A suspension is a serious strike, and repeated suspensions can terminate the account. Treat removals and suspensions as urgent.
Fixing and resubmitting
Fix every instance the policy covers, not only the example Google showed. Then submit a new release or edit the listing. If you disagree, use the appeal option on the Policy status page; see Google Play policies explained.
Prevention
Re-check your Data safety form whenever you add an SDK, read Play's policy update emails, and keep target API current.
How to fix a Google Play rejection, step by step
Follow these steps in order. Each one is something we do on client work.
- Open the Policy status page. In Play Console, the Policy and programs area shows the exact policy, the affected release and any deadline. Screenshot it before you change anything.
- Classify it. Is it a rejected update, a removed app or a suspended app? The fix path and urgency differ for each.
- Map it to the policy text. Open the linked Play policy page and quote the sentence you broke. Most issues are metadata, permissions, Data safety or testing requirements.
- Fix the artefact, not just the words. If a permission is the problem, remove it from the manifest and every library; if it's metadata, rewrite the listing to the field limits.
- Bump the versionCode and resubmit. Upload a new bundle (versionCode can't exceed 2,100,000,000) and send the changes for review.
- Appeal only when you're right. If the decision looks like a mistake, use the appeal form and give evidence, not opinions.
Worked example (hypothetical)
This example is illustrative. The app is made up, and so are any numbers in it.
Imagine a budgeting app, PennyPlan, is rejected for metadata because its title reads "PennyPlan – #1 Budget App 💰". Google's metadata policy bans ranking claims and emojis in the title. We'd rename it to "PennyPlan: Budget & Expenses" (27 characters), move the strongest benefit into the 80-character short description, strip repeated keywords from the full description, and resubmit. No code change is needed, so this is usually the quickest kind of fix.
Google Play rules that trip most apps
These come from Play Console Help pages we checked on 26 October 2026.
| Rule | Requirement |
|---|---|
| App title | 30 characters or less; no ranking or price claims, no emojis |
| Descriptions | No repetitive or irrelevant keywords; no misleading claims like "best game ever" |
| Screenshots and video | Must reflect the app's actual experience |
| New personal accounts | Closed test with at least 12 testers opted in for at least 14 days before production |
| Icon | 512 × 512 px; no misleading symbols or ranking badges |
Google Play listing fields and their limits
Play Console enforces these limits for every language, full-width or half-width characters alike.
| Field | Limit | Policy notes |
|---|---|---|
| App name | 30 characters | No emojis, ALL CAPS (unless brand) or store-ranking claims |
| Short description | 80 characters | First text users see on the detail page |
| Full description | 4,000 characters | Repetitive or irrelevant keywords can lead to suspension |
| App icon | 512 × 512 px, 32-bit PNG, max 1,024 KB | No badges or text implying ranking |
| Feature graphic | 1,024 × 500 px, JPEG or 24-bit PNG | No alpha |
Common mistakes
- Resubmitting the same build. An unchanged artefact gets the same decision.
- Deleting and re-creating the app. Package names can't be reused, and it doesn't erase the policy history.
- Ignoring a deadline banner. Warnings with dates become removals if missed.
- Fixing the listing in one language only. Every translated listing must meet the same rules.
Checklist
Copy this list into your release notes or ticket and tick each item off before you ship.
- Policy status screenshot saved
- Policy sentence quoted
- Fix applied to code, manifest or listing
- Every language listing checked
- versionCode incremented
- Data safety form matches the new build
- Appeal drafted only if evidence supports it
Sources
- Google Play Developer Policy Center (accessed 26 October 2026)
- Google Play Console Help: Data safety section (accessed 26 October 2026)
- Google Play Console Help: Permissions and APIs that access sensitive information (accessed 26 October 2026)
- Google Play Console Help: Target API level requirements (accessed 26 October 2026)
- Play Console Help: Create and set up your app (accessed 26 October 2026)
- Play Console Help: Metadata policy (accessed 26 October 2026)
- Play Console Help: App testing requirements for new personal developer accounts (accessed 26 October 2026)
- Play Console Help: Add preview assets to showcase your app (accessed 26 October 2026)
Questions
How long does Google Play review take?
Often hours to a few days; Google says some reviews can take up to 7 days or longer.
Can I appeal a Google Play rejection?
Yes, from Policy status in Play Console.
Will my live app be removed?
A rejected update doesn't remove the live version, but a removal notice does.
Do SDKs count in the Data safety form?
Yes. You're responsible for data collected by third-party SDKs.
Can you fix it for me?
Yes: App Rejection Fix.
How long does Google Play review take after a fix?
It varies by app and account history; Play Console shows the review status. Plan for days, not hours, around launches.