The store, read closely

Chrome Web Store Review Process: Why Extensions Get Rejected and How to Stay Out of the Resubmission Loop

The rejection email arrives with two words and a link: Purple Potassium. It sounds like a cocktail. It means the extension asked for a permission it never used, and the fix takes ten minutes once you know where Google hides the explanation.

November 17, 2026 · 10 min read

acmeleadsaver.com · store submission history
A fictional lead capture extension, two submissions
Rejected once for a permission nobody used
  1. Submission 1: Acme Lead Saver sent for review
  2. Rejected: Purple Potassium, excessive permissions
  3. Manifest declares "tabs"; no code calls it
  4. Removed "tabs"; justified storage and one host
  5. Test login added on the Test instructions tab
  6. Submission 2: sent for review
  7. Approved: up to 30 days to publish
Illustrative: a sample submission log for a fictional lead capture extension

The short answer

Every Chrome Web Store submission, new item or update, goes through Google's mix of automated and manual review. As of November 2026, Google says most reviews finish within a few days but can take up to a few weeks, and broad host permissions or hard-to-read code can slow them. Most rejections trace to a short list: unused permissions, missing listing details, remote code, or more than one purpose.

On this page
  1. Before anyone reviews anything: the account, the fee and the second factor
  2. Inside the queue: what Google says happens after you press Submit
  3. Purple Potassium and the rest of the periodic table of rejections
  4. One job, stated in a sentence a reviewer believes
  5. Permission justifications a reviewer can verify in thirty seconds
  6. A pre-flight list that ends the resubmission loop
  7. Handing the submission, and the paperwork, to us

Before anyone reviews anything: the account, the fee and the second factor

Google collects a toll at the gate. Chrome's developer registration page says you must register as a Chrome Web Store developer and pay "a one-time registration fee," without printing the amount. The number lives on Chrome's What's new page, whose April 30, 2026 entry mentions "the $5 registration fee" in passing, as of November 2026. Five dollars is the cheapest line in any extension budget. The expensive part is what the account is tied to.

The same registration page warns that once the account exists, "you cannot change its email address." Google's two-step verification policy requires 2-Step Verification on every developer account before publishing or updating anything. And the publishing guide says a brand-new publisher starts "limited to a maximum of two published extensions," as of November 2026. So three decisions come before a line of code: which company inbox owns the account, who holds the second factor, and whose name sits on the listing.

Inside the queue: what Google says happens after you press Submit

Google's review process page describes a blend of manual and automated systems and says every submission goes through the same one "regardless of the tenure of the developer or number of active users." Large publishers get no side door. The page names what draws a closer look: new developers, new extensions, "dangerous permission requests" and "significant code changes." A first extension from a first account therefore starts with two marks against it that it did nothing to earn.

Review timing and rules from Chrome's review process and publishing pages, as of November 2026
What Google's docs sayWhat it means for a launch plan
Typical review"For most extensions, review is completed within a few days, but it can take up to a few weeks."Plan around a range, never a date
Slower reviewsBroad host permissions, sensitive execution permissions, a lot of code or hard-to-review codeEvery permission you drop removes a reason to wait
Stuck in reviewPending "more than three weeks": contact developer supportThe point where asking is reasonable
Approved, not yet live"up to 30 days to publish," then the submission reverts to a draftAn approved build left on the shelf goes back in line
UpdatesNew items and updates face "the same review process"A one-line fix waits in the same queue as a new product
After approvalItems are reviewed periodically; minor violations typically get "7 to 30 days" to fixApproval is a status, not a lifetime pass

There is one narrow fast lane. Chrome's skip-review documentation lets certain Declarative Net Request rule updates go live without review, usually "within a few minutes." It covers rule changes for blocking-style extensions, not a new feature in your CRM tool. Everything else waits its turn, and nobody, including us, can tell you in advance how long that turn will be.

Layered colored-paper scene of three blank browser windows on a paper conveyor belt, one lifted toward a round blank rubber stamp, soft shadows
Every submission, new or updated, passes through the same review line.

Purple Potassium and the rest of the periodic table of rejections

Google gives each violation a two-word name, "a color and an element," according to its troubleshooting page. The names are memorable and the emails are short, which is how a founder ends up searching a phrase that sounds like a paint swatch at eleven at night. These are the codes that most often concern a custom business extension, with where we would look first.

Rejection codes from Google's troubleshooting page, as of November 2026, with our first places to look
CodeGoogle's labelWhere we would look firstFix before resubmitting
Purple PotassiumExcessive permissionsA permission declared in the manifest and never called, often left over from a prototypeDelete it, or make sure the feature that needs it ships in this build
Yellow MagnesiumFunctionality not workingA file the manifest names that is missing from the package, or a sign-in the reviewer could not completeRebuild the package from a clean folder and supply test credentials
Yellow ZincMissing or insufficient metadataA placeholder icon, no screenshot, a one-line descriptionFill every listing field for a reader who has never heard of you
Blue ArgonRemotely hosted codeA script tag pointing at a CDN or your own serverBundle the script inside the package
Red Magnesium, Red Copper, Red Lithium, Red ArgonSingle purposeTwo unrelated jobs sharing one extensionSplit them, or cut the second job
Purple Lithium, Purple Nickel, Purple CopperUser data: disclosure policy, prominent disclosure, secure transmissionNo disclosure, a buried disclosure, or data sent without secure transportWrite the disclosure from what the code actually sends
Yellow ArgonKeyword stuffingA description written for search engines instead of peopleRewrite it in plain sentences

Google's own examples are blunt. For Blue Argon it cites "a <script> tag that points to a resource" outside the package. For Yellow Potassium, the minimum functionality code, its example is a package that "contained no files other than a manifest," which suggests someone, somewhere, shipped exactly that. Data is a separate matter: Chrome's remote code explainer says JSON and CSS do not count as remotely hosted code. Your server can send numbers all day. It cannot send instructions. The Manifest V3 guide explains why.

One job, stated in a sentence a reviewer believes

Google's Extension Quality Guidelines require "a single purpose that is narrow and easy to understand" and say clearly separate features belong in separate extensions. One example of a violation on that page: an extension that displays product ratings and reviews "but also injects ads into web pages." The rule also catches honest scope creep. The lead capture tool that blocks ads on the side. The AI sidebar that also replaces the new tab page because someone in marketing liked the idea.

We wrote our own GatorCrawl Keywords extension to the rule. Its manifest description reads: "Search volume, CPC, keyword difficulty and 12-month trends on Google, plus volumes for related searches and People also ask." That is 124 characters, under the 132-character limit Chrome's manifest reference sets for descriptions as of November 2026, and it names one job. The right-click lookup on other pages is that same job reached a second way. Our build write-up takes it apart piece by piece.

If you cannot say what the extension does in one breath, neither can the reviewer.

Permission justifications a reviewer can verify in thirty seconds

The dashboard's Privacy tab is where you "declare your extension's single purpose" and describe how it handles user data, per the publishing guide. Google's privacy practices documentation gives every permission its own justification field and warns that requesting broader permissions than necessary "may cause your extension to be rejected." It adds that the disclosures are shown to Chrome users. Each justification has two readers: a reviewer looking for a reason to say no and a customer looking for a reason to say yes.

Here is how GatorCrawl's short list reads in plain words, taken from its manifest and service worker:

  • storage: holds lookup results for an hour in session storage, so reloading a Google page does not spend the user's credits a second time.
  • contextMenus: adds a single right-click item, "Look up keyword volume," for text the user has selected.
  • One host permission: keywords.gatorcrawlseo.com, the extension's own web app, where the API it calls lives.
  • One content script match: Google search result pages, the only place the numbers are drawn.

Notice what is absent: no tabs, no history, no access to every website. Fewer lines to justify leaves fewer lines to question. Our guide to extension permissions and privacy lists the warning each common permission puts in front of users and how to avoid most of them.

A pre-flight list that ends the resubmission loop

The loop runs like this. Rejected. Fix the one thing named. Resubmit. Wait. Rejected for something else. Each round buys another wait of unknown length. The way out is to check the whole package before the first submission, not just the item in the last email.

  1. 1

    Load it unpacked and use it like a stranger

    Chrome's hello world tutorial shows how: chrome://extensions, Developer mode on, Load unpacked. Do it in a fresh browser profile, sign in as a brand-new user and click everything.

  2. 2

    Strip the manifest to today's features

    Google's permissions policy tells developers not to "future proof" by requesting permissions for features that are not built yet. If next quarter's feature needs it, next quarter's update can ask.

  3. 3

    Bundle every script

    No script tags to outside servers and no code fetched at run time. Minify if you like; Google disallows obfuscation outright.

  4. 4

    Give the reviewer a way in

    The Test instructions tab takes instructions and credentials "only if needed." If your extension needs an account to do anything, it is needed. Supply a working test login with enough credits to try every feature.

  5. 5

    Write the listing for a person

    A real icon, a title, screenshots and a description in sentences, plus a privacy policy linked in the dashboard field if the extension handles any user data.

  6. 6

    Keep a change log per submission

    Our practice, not a Google rule: one short note per build listing what changed, so when a reply cites a code you know which change set it off.

Our own extension waits like everyone else's. When we read the GatorCrawl Keywords listing on November 16, 2026, it showed version 0.1.0, updated November 15, 2026, while our code had already moved to 0.1.1; the store had not yet published the newer build. That gap is ordinary, and it is why we plan releases around review instead of around a calendar promise. A cross-browser release adds the other stores' review steps on top.

Handing the submission, and the paperwork, to us

Store submission, the privacy disclosures and the permission plan are part of every extension we build, from $1,500, depending on complexity, with a fixed written estimate before work starts. We publish under your developer account, so the listing and its history belong to you. What we will not do is promise approval or a review time. Google says its review times vary, and we quote that rather than improve on it. The pricing guide and the timeline guide cover the rest.

Already rejected? Send us the email. If the fix is small, we will say so and quote it. If the extension needs rework, the estimate says what and why. Updates after launch, including the ones a policy change forces, are quoted separately, as the maintenance page explains. The section overview shows what else we build. DataCram is a San Antonio web studio building for the web since 1999; see our work, get in touch or call (210) 346-0848.

Questions owners ask about custom browser extensions

It is Google's code for excessive permissions. Google's troubleshooting page gives the common reason as an extension requesting a permission it does not use. Open the manifest, list every permission, and match each one to code that ships in this build. Remove any that do not match, rebuild the package and resubmit. Our permissions guide covers which ones show warnings.

Yes. Google's review process page says all submissions, for a new item or an update to an existing one, are subject to the same review process, as of November 2026. The exception is a narrow set of Declarative Net Request rule changes that can skip review. Plan bug-fix releases with that wait in mind.

Google's Red Magnesium, Red Copper, Red Lithium and Red Argon codes mean the reviewer found two or more purposes in one extension. The quality guidelines require a single purpose that is narrow and easy to understand. Either remove the unrelated feature or publish it as a second extension, then rewrite the description so it names one job.

According to Chrome's publishing guide, once review is complete you have up to 30 days to publish, as of November 2026. After that the staged submission reverts to a draft and must be submitted for review again. If a launch date is fixed, submit close enough to it that approval does not expire first, and remember no one can predict the review length.

No. Google's distribution documentation says all visibility settings, public, unlisted and private, have the same policy requirements and go through the same review process, as of November 2026. Google's enterprise page does say domain-published extensions usually get through review more quickly. Our page on internal team extensions covers private publishing for staff tools.

Google's registration page says that after an account is created, you cannot change its email address. That is why we recommend opening the account on an address your company controls, with 2-Step Verification, which Google requires before publishing or updating. Chrome's April 30, 2026 What's new entry adds that teammates can be invited to a publisher account at no cost.

Keep reading

Free · No obligation

Send us the rejection email

Paste the code Google sent, or describe the extension you plan to submit. Someone at DataCram replies with what we would check first and what the fix or the build would cost.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote