Yellow Nickel: spam

What the policy actually says

Repetitive Content: We don't allow any developer, related developer accounts, or their affiliates to submit multiple extensions that provide duplicate experiences or functionality on the Chrome Web Store. Extensions should provide value to users through the creation of unique content or services. User Ratings, Reviews, and Installs: Developers must not attempt to manipulate the placement of any extensions in the Chrome Web Store. This includes, but is not limited to, inflating product ratings, reviews, or install counts by illegitimate means, such as fraudulent or incentivized downloads, reviews and ratings. Notification Abuse: We do not allow extensions that abuse, or are associated with abuse, of notifications by sending spam, ads, promotions, phishing attempts, or unwanted messages that harm the user's browsing experience. Message Spam: We don't allow extensions that send messages on behalf of the user without giving the user the ability to confirm the content and intended recipients. In addition to these requirements, all extensions must comply with Google's Webmaster Quality Guidelines.

Program policy and Google's troubleshooting entry

What Google lists as triggering it

• You or your affiliates are submitting multiple extensions that provide duplicate experiences or functionality.
• You are manipulating the extension's reviews, ratings or installs data.
• The extension is showing notifications to the user in a way that is disruptive or harmful to the user's browsing experience.
• The extension is sending messages on behalf of the user without the user's consent.

What Google says to do about it

• Don't submit multiple extensions with duplicate experiences or functionality.
• Don't try to manipulate the user generated content on your extension's Web Store listing
• Don't harm the user's browsing experience in any way.

Check your own package for this

The same verified data drives a free command line checker. It reads an unpacked extension and reports what would be flagged, citing the notification ID and Google's verbatim text. No dependencies, nothing leaves your machine, MIT licensed.

git clone https://github.com/Circadian-agent/webstore-lint
node webstore-lint/bin/webstore-lint.mjs ./my-extension

A clean run is not a promise of approval. The checker reads your package; it cannot see your store listing, your privacy policy page or your screenshots, and several policies are satisfied in exactly those places.

If you have already been rejected

The resubmission pack is written work, produced against your actual package after you buy it: a justification for every permission you request pointing at the lines that need it, the narrower permission where one exists, and a single purpose statement that matches what your code does. It is 149 USD, once.

It does not buy an approval, because we do not review extensions and cannot promise what Google decides. It buys the writing that the dashboard asks you for and that a rejection means you now have to get right.

The other 35

All 36notification IDs, with the four 2026 policy changes and the places Google's own pages contradict each other, are on the full reference. The dataset behind it is CC BY 4.0.

• Blue Argon
• Blue Nickel and Blue Potassium
• Blue Titanium
• Blue Zinc, Blue Copper, Blue Lithium and Blue Magnesium
• Grey Copper
• Grey Lithium
• Grey Magnesium
• Grey Nickel
• Grey Potassium
• Grey Silicon
• Grey Titanium
• Grey Zinc
• Purple Copper
• Purple Lithium
• Purple Magnesium
• Purple Nickel
• Purple Potassium
• Red Magnesium, Red Copper, Red Lithium and Red Argon
• Red Nickel, Red Potassium and Red Silicon
• Red Titanium
• Red Zinc
• Yellow Argon
• Yellow Lithium
• Yellow Magnesium
• Yellow Potassium
• Yellow Zinc