To appeal a Chrome Web Store warning or takedown, open the item in the Developer Dashboard and use the Appeal button on its detail page. Account suspensions are appealed from the account page. Google's policies allow one appeal per violation decision, so make the first one complete. Fixing and resubmitting is often faster.
First, work out which action you received
The review process documentation separates these cases:
- Rejection of a new submission. You get an email naming the violated policy. The live listing is unchanged.
- Warning on a published item. Typically 7 to 30 days to submit a fixed version before takedown.
- Takedown. Removed from the store and search. Usually reversible by submitting a compliant version.
- Malware or extreme violation. Removed without notice, with details not disclosed and possible permanent suspension.
The right response differs. A warning is a deadline. A takedown is a fix and resubmit. A malware action needs a very different conversation.
Fix, resubmit or appeal
| Situation | Usual best step |
|---|---|
| You agree with the finding | Fix it and submit a new version |
| Reviewer misread your code or permission use | Appeal with specifics |
| The email is unclear | Use the support form and request detail |
| Account suspended | Appeal from the account page |
Takedowns are usually reversible by submitting a compliant version, which means a correct fix often beats a long dispute. Appeal when you believe the decision is wrong, not as a delay tactic.
How to write an appeal that can succeed
- Quote the policy named in the email.
- Point to the exact permission, file or behaviour in question.
- Explain why each permission is needed for the single purpose, in two sentences each.
- State what you changed, with version number, if you made any change.
- Keep the tone factual. The policies warn that frivolous appeals or misuse may forfeit future appeal rights.
Write for a reviewer who has a long queue. Short, specific and evidence based wins over long and emotional.
Common causes worth checking before you appeal
The developer program policies list rules that reviewers apply often:
- Requesting broader permissions than the feature needs, or for future features that do not exist yet.
- Loading or running remote logic. Under Manifest V3, full functionality must be discernible from the submitted code.
- Missing or inaccurate privacy policy where user data is handled.
- Misleading listing text, or install flows that bundle other offers.
- Impersonation or misleading store status claims.
Check these against your last diff before you write a word.
Support and timing
Other issues go through the One Stop Support contact form. Requests get an ID by email, replies may take up to three days, and escalated issues may take longer than seven days. Do not wait until day 29 of a 30 day warning window to start.
Attempts to circumvent enforcement, such as creating a new account to republish, can lead to termination of the developer account and related accounts, according to the policies.
What this means for people who rely on extensions
If an extension your team uses gets a takedown, its users keep it installed for a while. Chrome disables it only after several weeks of no resolution. Monitor the extensions you approved and subscribe to publisher notices where available.
Quick check
How many appeals do I get?
The program policies say a violation decision can be appealed once.
Does a takedown always mean malware?
No. Most takedowns follow policy violations and can be reversed with a compliant version. Malware actions are handled under separate procedures.
Where do I appeal an account suspension?
From the Appeal button on the account page, according to the review process documentation.
Sources
Last reviewed: 19 October 2026.
