Skip to content
Ask Claude about any Chrome extension, answered with Ext Watch data. See how →
Growth and ranking

Chrome Web Store policy rules that get extensions removed

Chrome Web Store policy removes extensions for fake installs, unclear purpose, data misuse and remote code.

By Ext Watch Research6 min read
Pip, the blue bird mascot, reading a big rulebook scroll, a red-free gentle warning triangle in amber floating

The short answer

Google removes extensions that inflate installs or ratings, bundle unrelated features, misuse user data or run remote code. These rules are in its published Chrome Web Store policy. The Manifest V3 move also changed what extensions can do. Over 99.9% of extensions in the store declare Manifest V3.

  • Fake installs and ratings can mean removal and account termination.
  • One extension, one narrow purpose.
  • Accurate privacy policy and narrow permissions are required.
  • No remote code under Manifest V3.
In this guide12 sections
  1. 01The Chrome Web Store policy rules that bite
  2. 02Manifest V3: the change everyone felt
  3. 03What we won't claim
  4. 04The privacy fields, in plain words
  5. 05Affiliate links, ads and other money rules
  6. 06Permission habits that keep you safe
  7. 07What happens after a warning
  8. 08Rules that change, and how to keep up
  9. 09Policy areas by type of extension
  10. 10A policy check before every release
  11. 11A five-minute self-check
  12. 12Questions people ask

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

RuleWhat Google says, in shortWhat it usually catches
Spam and abuseNo inflating ratings, reviews or installs by illegitimate meansBought installs, incentivised reviews
Single purposeA single purpose that's narrow and easy to understandToolbars bundling unrelated features
User privacyAccurate privacy policy, narrowest permissions, limited useData sold to brokers, missing disclosures
Manifest V3 codeLogic must be clear from submitted code, no remote codeScripts loaded from a server at runtime
QualityListings must be honest and functionalMisleading 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 data, over 99.9% of the roughly 270,000 extensions in the store declare Manifest V3, and only about ten still declare V2.

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.

The privacy fields, in plain words

The privacy tab in the dashboard trips up many first submissions. It asks what data you collect and why. Google's user data policy sets the bar.

Question on the formWhat a good answer looks like
What data do you collect?Name each type, like "page URLs on sites you enable"
Why?The feature that needs it
Is it sold?It shouldn't be, and the form says so
Is it used for anything else?No, beyond the stated feature
Where is your privacy policy?A live page that matches the form

The common failure is a gap between the form and the code. If the code sends page URLs to your server but the form says you collect nothing, that's a violation, even if you never use the data.

Many extensions earn through affiliate links or ads. Google allows some of this, with conditions.

  • Affiliate links must be disclosed and need a clear user action. Quietly swapping links on pages people visit is the classic problem.
  • Ads must be clearly labelled as ads and come from your extension, not injected into other sites in a way that looks native.
  • Paid features are fine, but the listing must say they exist.

If you're unsure, write a line in your listing that says how you make money. It costs nothing and removes most doubt for users and reviewers alike.

Permission habits that keep you safe

Policy and permissions are tied together. Most removals for privacy start with access the tool didn't need.

In our data, about 53,000 extensions, roughly one in five, ask for access to all sites. Many need it. Many don't. If your tool works on a list of known sites, name them. If it only acts after a click, activeTab is usually enough.

Our guide to permission changes shows how users and rivals read these choices from the outside.

What happens after a warning

Google may email a warning with a deadline before removing an item, depending on how serious the issue is. Treat any policy email as urgent.

  1. Read the named policyin full.
  2. Fix the exact issueand nothing else in that update.
  3. Resubmit before the deadlineif one is given.
  4. Reply through the dashboardif you think the call was wrong, with a short, specific note.
  5. Keep a copyof every email and your replies.

If an item is removed, your other items usually stay up. Repeated or serious violations can affect the whole account, which is why the spam rules matter so much.

Rules that change, and how to keep up

Store policy changes a few times a year. Google posts updates on the Chrome for Developers blog and in the policy pages themselves. A short habit helps: once a quarter, open the policy page and skim for anything new against your own listing. Our guide to review timing covers how policy checks fit into each submission.

Policy areas by type of extension

Different kinds of tools tend to run into different rules. Here's where to read first.

Type of toolPolicy areas to read closely
Ad blockers and privacy toolsPermissions, user data, single purpose
Shopping and coupon toolsAffiliate disclosure, ads
AI helpersUser data, remote code, privacy fields
Social media toolsSpam, impersonation, user data
New tab and theme toolsSingle purpose, search settings

Search settings deserve a note. Tools that change the default search engine or new tab page have their own rules. Read them before shipping anything that touches either.

A policy check before every release

Make this a habit, not a one-off. It takes ten minutes.

  1. List any new permissionand the feature that needs it.
  2. Check the privacy fieldsstill match what the code collects.
  3. Read your listing textfor claims the tool can't back up.
  4. Confirm all logic shipsin the package.
  5. Note any money changes, like ads or affiliate links, and disclose them.

Releases that pass this list rarely bounce in review. Our Privacy & Security category page shows how tools in a sensitive category present their permissions and data use.

A five-minute self-check

  1. Can you describe your extension's purpose in one sentence?
  2. Does your privacy policy match what the code collects?
  3. Does every permission map to a visible feature?
  4. Is all your logic in the package you upload?
  5. 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 data 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.

Can I put ads in my Chrome extension?

Google's policies allow some ads but set rules on how they appear. Ads must be clearly labelled and can't interfere with the sites people visit. Read the ads section before adding any.

Do I need a privacy policy for my extension?

If your extension handles user data, yes. The privacy fields in the dashboard must match what the code collects, and the policy must be easy to find.

Ext Watch logoExt Watch ResearchBuilt from Ext Watch’s own store data
Privacy & Security

5,863 extensions tracked in Privacy & Security. See them all.

Extensions gaining users fastest, and what they changed.Store data, updated today

Plans from $19/mo