Skip to main content

Apr 3, 2019 - 3 minute read - Evil Tester JavaScript Chrome Extension

Chrome Extension Rejection Handling

Writing a Chrome Extension is pretty easy (getting it in the Chrome Store is much harder!). In this post I describe the steps to handling if your extension is rejected.

I have now released two extensions to the Chrome Store.

Both were rejected.

Multiple times.

For the same generic reasons.


Dear Developer, Your Google Chrome item, “…” did not comply with our policies and was removed from the Google Chrome Web Store. Your item did not comply with the following section of our policy:

  • Do not post repetitive content.

  • Do not attempt to change the placement of any Product in the store, or manipulate any Product ratings or reviews, by unauthorized means, such as fraudulent installs, paid or fake reviews or ratings, or offering incentives to rate Products.

  • Do not post an app if the primary functionality is to link to a website not owned by the developer posting the app.

  • Do not post an app where the primary functionality is to install or launch another app, theme, or extension. For example, you cannot post an app if its primary function is to launch a desktop app that the user has already installed. Another example of a disallowed practice would be to post a packaged app that just launches a website.

  • Your app must comply with Google’s Webmaster Quality Guidelines

If you’d like to re-submit your item, please make the appropriate changes to the item so that it complies with our policies, then re-publish it in your developer dashboard. Please reply to this email for issues regarding this item removal.

My extensions did none of this.

The Quality Guidelines are too vague to be any help.

If you Google the error message you will see other people in the same situation. This doesn’t help, but it makes you feel less alone.

What to do?

Since you receive the rejection in an email.

Reply to the email nicely asking.

“Can you provide more information about why this failed the review and what I have to do to fix it?”

Or words to that effect.

If you are told to resubmit. Then resubmit, expecting to be rejected. Because you will likely go through this process multiple times.

I went through this cycle. With no changes to my extension. 9 times from 26th Feb 2019 until it was accepted into the Chrome Store on the 1st of April.


I suspect it is automatically rejected.

You might get lucky.

If you don’t then keep trying.


  • first google the error message
  • you’ll see other people in the same situation
  • if changes you need to make are not obvious then email support asking for a specific reason
  • keep doing this, and submitting and asking, until you get a reason
  • eventually, if you persist, you can make it


I’ve created a video showing the steps I took.

Watch on YouTube

If you are interested in writing a Chrome Extension then check out all blog posts in this category Chrome Extension and see the videos in this Chrome Extension Playlist

You will need a Github account to comment. Or you can contact me with your comment.

I reserve the right to delete spam comments e.g. if your comment adds no value and its purpose is simply to create a backlink to another site offering training, or courses, etc.