On this page
A Google Play rejection is not the end of the release. The way you respond decides how quickly the app comes back to the store. Rejections fall into two buckets: a review rejection, where something technical or metadata-related failed review, and a policy rejection, where reviewers decided the app breaks a Play policy. This guide walks through the appeal path for policy rejections, step by step, and explains when fixing the app beats arguing with the decision.
First, identify which kind of rejection you got
Open Play Console and go to your app's dashboard. Policy issues show up in the app's policy status area and on the App content page, and Google also emails the account owner. Review rejections usually come with a specific reason tied to the release, such as a broken build, a target API level that is too low, or incomplete declarations. Policy rejections cite a policy category, such as impersonation, deceptive behavior, dangerous permissions, or restricted content.
How to appeal, step by step
Fix the underlying problem first
Appeals that describe a change are far more persuasive than appeals that argue. If the app asks for a permission it does not need, remove the permission. If a store listing claim misled users, correct the copy. Your appeal should reference the exact change you made and where a reviewer can verify it.
Open the appeal from the issue itself
In Play Console, open the app dashboard, find the policy issue, and use the contact or appeal link attached to it. Starting from the issue keeps your appeal tied to the right app and the right decision, which avoids the delay of a generic support ticket.
Write a substantive appeal
State the decision you are appealing, explain what the app actually does, cite the policy you believe applies, and describe the changes you made if there are any. Three or four focused paragraphs beat a single sentence. Attach evidence: a short demo video, a link to the relevant functionality, or supporting documentation.
Respond to follow-up questions quickly
If a reviewer asks for more information, reply with exactly what was requested. New context usually resolves an appeal faster than re-arguing the original position.
What if the first appeal fails?
A failed appeal does not close the door. Some violations come with a warning and a remediation window before enforcement, while others let you fix the app and submit a fresh release. Repeated rejections on the same app escalate, so treat the second rejection as a signal to audit the whole app against policy rather than patching the single issue that was cited.
Policy appeals reward preparation over volume. AppsTestLab reviews the rejection against current Play policy, identifies what actually triggered it, and drafts the appeal with the evidence attached. That is why most rejections handled this way get a usable answer on the first response instead of the third.
Got a policy rejection?
AppsTestLab will analyze the rejection, identify the policy in question, and draft a substantive appeal you can submit from Play Console.
Talk to us on WhatsAppFrequently asked questions
How long does a Play Console appeal take?
Google does not publish a fixed timeline for appeals. Response times vary with the type of issue and current support volume, so make the first appeal complete rather than sending a short message and following up with context later.
Can I fix the app and resubmit instead of appealing?
Yes, and for many rejections that is the faster path. If the rejection names a concrete problem, fix it and submit a new release. Appeal the decision when you believe the app complies with policy and the reviewers misread it.
Does appealing keep my app visible on the Play Store?
An appeal does not automatically restore distribution. Until the issue is resolved, the affected release may stay unpublished or the app may remain unavailable to new users, so treat the appeal as a recovery path, not a hold.
Sources & references
Official Google documentationThese links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Get help doing this
