Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 36 ยท Publishing

Submitting to the Web Store and Passing Review

Register a developer account, upload your extension package, fill in the listing and privacy tabs, choose visibility, understand the review process and fix the most common rejection reasons.

You have a clean package. Now comes the part with forms and waiting. This lesson walks you through the Chrome Web Store developer dashboard in the order you will meet it, what reviewers check, and how to handle a rejection. The dashboard changes its layout from time to time, so treat the screen names as a guide and follow the current labels.

The dashboard needs a signed-in Google account, a payment and a human, so it cannot run inside this lesson. The interactive example is a readiness checklist you can use before you press the button.

One-time setup

  1. Open the Chrome Web Store Developer Dashboard and sign in with a Google account (use one the whole team can recover, not a personal account).
  2. Accept the developer agreement and pay the one-time registration fee (a small fee, five US dollars at the time of writing).
  3. Verify your contact email, and turn on 2-step verification: the store expects it for publishers.
  4. Optional: set up a group publisher so several people can manage extensions, and add your website as a verified domain.

Registering is once per account; you can then publish many extensions.

Upload the package

Click New item, choose your zip and upload. Chrome validates the manifest immediately and rejects broken packages with a clear message: for example "Invalid manifest" or "The version must be higher than the published one". Fix and upload again.

The dashboard then shows tabs for the item. You fill each in before Submit for review becomes active.

flowchart LR
    A["Upload zip"] --> B["Store listing"]
    B --> C["Privacy practices"]
    C --> D["Distribution"]
    D --> E["Submit for review"]
    E --> F{"Review"}
    F -- "Approved" --> G["Published"]
    F -- "Rejected" --> H["Fix and resubmit"]
    H --> E

The review loop repeats until the item is approved.

Store listing tab

Enter the description, category, language, icon and screenshots prepared in Preparing for the store. Add a support URL or contact email: users will use it.

Privacy practices tab

This is the tab that causes most delays. You provide:

  • the single purpose statement;
  • a justification for each permission and host permission, in one or two sentences;
  • whether you use remote code (answer no);
  • the data usage boxes for the categories you handle, and the certifications that you do not sell or transfer data for unrelated purposes and do not use it for credit or lending;
  • the privacy policy URL.

Be consistent: if the code reads browsing history but you ticked nothing for web history, reviewers will notice.

Distribution tab

  • Visibility: Public (everyone can find it), Unlisted (only people with the link) or Private (specific testers or your Google Workspace domain). Start with Unlisted or Private for a first test group.
  • Regions: all countries by default; restrict only if you must.
  • Pricing: the Web Store no longer supports paid extensions. Use your own account system, subscriptions or payment provider if you sell features.

Review

When you click Submit for review, Google runs automated checks and sometimes a manual review. Timelines vary: many items are approved within a day or two, but a first submission, a new broad permission or a sensitive category can take longer. You can choose deferred publishing, which approves the item but lets you press Publish when you are ready, so you can sync it with a launch.

Reviews look at:

  • single purpose and listing accuracy;
  • permission use versus justification;
  • remote code, obfuscation and policy violations;
  • user data handling and the privacy policy;
  • spam: duplicate extensions, keyword stuffing, fake reviews.
A submission readiness checklist

When a review fails

A rejection email names the violated policy, for example "Purple Potassium" (permissions not justified) or "Yellow Argon" (single purpose). Do not guess: read the linked policy section, fix the cause and reply through the dashboard if you disagree.

Common causes and fixes:

Reason Fix
Broad permission not needed Remove it or switch to activeTab/optional permissions
Listing does not match behaviour Rewrite the description and screenshots
Missing or weak privacy policy Publish a specific policy and link it
Obfuscated or remote code Ship readable bundled code; remove CDN scripts
Misleading name or keyword stuffing Use a plain name that matches the manifest
Broken functionality for the reviewer Provide a test account and steps

Resubmit after fixing, and keep the same item: repeated violations can lead to a suspension.

After approval

Check the live listing from another profile, install it from the store and test it. Add a link to the listing on your website. Reply to reviews and support emails: a responsive developer is rewarded with a better rating. Updating is the next topic: Updates, versioning and CI.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which visibility level suits a first test with a small group via a link?

    Unlisted items are installable by anyone with the link but are not searchable in the store.
  2. 2. Where do you justify each permission?

    The Privacy practices tab asks for a justification for every permission and a single-purpose description.
  3. 3. What is deferred publishing?

    It lets you line up the release with a launch after approval.
  4. 4. A rejection names a policy. What is the best next step?

    Duplicates and blind resubmissions make things worse. Fix the actual violation.

Summary

  • Register once, upload the zip, then complete Listing, Privacy practices and Distribution.
  • Justify permissions and data use honestly and consistently with the code.
  • Pick Unlisted or Private for first tests; use deferred publishing for launches.
  • Read rejection reasons, fix them, resubmit and keep the same item.

Next: Updates, Versioning, Localization and CI