Store policy reads like the small print on a parking sign. Nobody reads it until the tow truck shows up. These rules sit beside the visibility levers in Chrome Web Store SEO.
The Chrome Web Store policy rules that bite
| Rule | What Google says, in short | What it usually catches |
|---|---|---|
| Spam and abuse | No inflating ratings, reviews or installs by illegitimate means | Bought installs, incentivised reviews |
| Single purpose | A single purpose that's narrow and easy to understand | Toolbars bundling unrelated features |
| User privacy | Accurate privacy policy, narrowest permissions, limited use | Data sold to brokers, missing disclosures |
| Manifest V3 code | Logic must be clear from submitted code, no remote code | Scripts loaded from a server at runtime |
| Quality | Listings must be honest and functional | Misleading names or descriptions |
The install-inflation rule is blunt. Google's spam section says violations lead to removal and possible account termination. Our post on buying installs shows why it backfires.
Manifest V3: the change everyone felt
MV3 changed how extensions run, and it bans remotely hosted code. Blockers and tools that changed behaviour from a server had to rework themselves.
In our crawl as of 3 Oct 2026, 61,788 extensions declare Manifest V3, 2 still declare V2, and 30 had no version we could parse. That's a crawl of about 21% of store IDs, so treat it as a big sample.
If your extension needs to fetch logic from a server, redesign it before you submit.
You can check these figures yourself on the Privacy & Security category page.
What we won't claim
You'll see lists online of famous extensions "killed by policy". We haven't verified the reason for each removal, and Google rarely says publicly why a listing went. So we don't name any here.
What we can say: when a listing disappears from the store, our crawler marks it removed with the date. We're biased, since we build Ext Watch, but that date beats a rumour.
A five-minute self-check
- Can you describe your extension's purpose in one sentence?
- Does your privacy policy match what the code collects?
- Does every permission map to a visible feature?
- Is all your logic in the package you upload?
- Have you ever paid for installs or reviews? If yes, stop now.
Read the parking sign before you park.
Questions people ask
Can an extension be removed without warning?
Google describes periodic reviews of published items, with outcomes that depend on how serious the violation is.
Are Manifest V2 extensions still allowed?
Our 3 Oct 2026 crawl shows almost none left. Check Google's MV3 docs for current rules.
What is the single purpose policy for Chrome extensions?
Google's policies say an extension must have a single purpose that's narrow and easy to understand. Toolbars that bundle unrelated features are the usual target.
Where these numbers come from
- developer.chrome.comChrome Web Store program policiesAccessed 3 Oct 2026
- developer.chrome.comChrome Web Store review processAccessed 3 Oct 2026
Part of our guide: Chrome Web Store SEO: titles, descriptions, screenshots. More in Growth and ranking.
286 new extensions in the last 30 days in Privacy & Security. See them all.
Extensions gaining users fastest, and what they changed. Updated 3 Oct 2026 from our Chrome Web Store crawl
