Chrome Web Store policy bans duplicate extensions, manipulated ratings and install counts, notification spam, messages sent for users without confirmation, impersonation, false endorsement claims, mimicking browser warnings, and fake store labels such as an invented Editor's Choice. Enforcement ranges from removal to account termination.
Spam and abuse rules
The program policies list these items under spam and abuse:
- Multiple extensions with duplicate experiences or functionality, including through related accounts or affiliates.
- Manipulating placement with inflated ratings, reviews or install counts from fraudulent or incentivized sources.
- Abusing notifications to send spam, ads, promotions, phishing or unwanted messages.
- Sending messages on the user's behalf unless the user can confirm the content and recipients.
- Not meeting Google's Webmaster Quality Guidelines.
The duplicate rule matters for security. Throwaway copies of an extension are a standard way to keep a malicious version in circulation after a takedown. Banning related accounts shuts that route.
Impersonation rules
The same policies prohibit:
- Pretending to be someone else, or claiming endorsement by an organisation when that is not true.
- Mimicking browser or operating system functionality or warnings.
- Linking to or passing off a site as the Chrome Web Store.
- Misrepresenting store status, for example a false Editor's Choice label.
- Infringing intellectual property.
These rules target the lookalike problem. A user who sees a familiar name, logo and five star rating is trusting signals that can be faked, and the policy tries to make faking them a violation.
A quick map from abuse to risk
| Abuse | Risk to the user | What to check yourself |
|---|---|---|
| Duplicate listings | Malicious twin of a real extension | Publisher name, developer site, ID |
| Fake reviews | False confidence | Review dates, repeated phrasing |
| Notification abuse | Phishing delivery channel | Notification permission requested |
| Browser warning mimicry | Social engineering | Does a "browser alert" come from a page, not the browser |
| Store status claims | Borrowed trust | Check the store itself, not the extension's own text |
What happens when rules are broken
The enforcement section says removals are permanent unless a revision fixes the issue, and enforcement applies globally by default. Developers may appeal once. Attempts to circumvent enforcement can lead to immediate termination of the developer account and possibly related accounts. Serious or repeated violations can lead to suspension, a store ban, and in extreme cases suspension of related Google services.
What a company should do with this
You cannot rely on store policy to catch every lookalike. Make three habits routine:
- Install from an allowlist of extension IDs, not from names.
- Compare the publisher and developer website against the vendor's own documentation.
- Treat ratings as marketing. Use them as a prompt to read, not a decision.
If you publish your own extension, put the exact store link and extension ID on your website, so your users can verify the real listing. Publishing that link also gives your support team a clean answer when someone reports a lookalike.
Quick check
Are fake reviews against the rules?
Yes. The policies prohibit inflated ratings, reviews or install counts from fraudulent or incentivized sources.
Can an extension claim endorsement from a well known organisation?
Only if true. Claiming endorsement that does not exist is listed as impersonation.
Does the store remove lookalikes automatically?
Policy bans them, but you should not assume detection is perfect. Install by extension ID from an allowlist.
Sources
Last reviewed: 19 October 2026.
