Chrome extension submission guidelines.
If you have built and submitted a Chrome extension, you know about the vague review process and how much time it takes for approval.
If you have never published a chrome extension before and you are going to publish one now, you are at the right place.
In this post, I will provide guidelines for submitting your extension to the chrome web store.
Follow chrome web store submission guidelines
https://developer.chrome.com/docs/webstore/best-listing
- You will need an icon (128x128 pixels)
- You will need at least one screenshot (1280x800 or 640x400)
- Your extension should have a single purpose
Initial submission
Chrome web store usually takes longer duration to approve your extension on the first submission. The duration depends on the type of extension, the host permissions you have requested and other permissions your extension needs.
The broader the host permissions, the more your extension will be scrutinized.
What you can do
- Only request permissions that are essential for your extension.
- If your extension is designed to function only on certain websites, make sure to list only those websites in the host permissions and content script matches.
- Don't obfuscate your code. Minification is fine, but don't obfuscate.
Subsequent submissions
I have noticed that the more submissions you make, the faster the approval process becomes. The duration of subsequent submissions still depends on the host permissions and the number of permissions you have requested. But in most cases, it won't take the same duration as it did for the initial submission.
What you can do
- Try to keep your changes small in every release
- Frequent releases speeds up the approval process
- Separate your code changes from the store listing changes. I've noticed that if your extension has code changes and store listing changes in the Chrome Web Store, the approval process tends to take longer.
How not to get rejected
- Don't inject external code. Include all your Javascript code in the extension package. Instead download the 3rd party code and package it within your extension.
- Don't request permissions which are not needed for your extension.
- Code obfuscation is not allowed.
- Your extension listing should have a clear single purpose. Your extension might get rejected if your description is vague.
- If you are collecting user data, ensure to check the corresponding fields in the privacy tab under data usage section. You will also have to provide a link to the privacy policy if you are collecting user data.
- Your permissions justification should be accurate
- Try to put in at least 100 words in the description
Conclusion
If you are submitting your extension for the first time, it might feel daunting. Follow the guidelines from this post and you should have no issues in getting your extension approved.