A Chrome Web Store listing that passes review

A submission that clears review first time instead of bouncing on permissions.

3h Involved Chrome

The Chrome Web Store review criteria are documented, so rejections are predictable. Nearly all of them come down to permissions.

01

Ship the narrowest permission set that works

Broad host permissions covering all URLs invite scrutiny. Request the minimum, and expand in a later version when you can justify it.

02

Justify every sensitive permission in the form

There is a per-permission justification field. It must describe the feature that uses it, and the feature must exist in the build you submit.

03

Prepare the listing assets exactly

1280x800 screenshots, a 440x280 tile, a 128px icon, and a privacy policy URL. The privacy policy is not optional if you touch user data.

04

Submit unobfuscated code

Minified is fine, obfuscated is not. Code a reviewer cannot read is rejected on that basis alone.

Watch out
  • Review usually takes a few days but can run to weeks, and new developers get more scrutiny. Contact developer support only past three weeks.
  • A permission you added for a feature you later removed will still be checked. Audit the manifest before every submission.