Best Practices and Guidelines

  1. Research and understand the Chrome Web Store policies. Before developing a Chrome extension, it is important to review the Chrome Web Store Developer Program Policies and ensure your extension complies with all guidelines and requirements.
  2. Extensions should add value to the Chrome Web Store. If your extension is not particularly useful or unique, it doesn’t belong on the Chrome Web Store.
  3. No cheating. If you attempt to scam the system (for example, by misleading users, circumventing enforcement, copying the work of other developers, or manipulating your extension’s reviews or ratings) you will be banned from the Chrome Web Store.
  4. Developers must carefully adhere to strict guidelines regarding the collection, use, and disclosure of user data, and must obtain user consent for any data collection or usage. Apps that access sensitive user data such as financial information, health information, or personal information must comply with additional policies and guidelines.
  5. Ensure that all of your extension’s information and metadata are up to date and accurate. This also includes information provided in the developer dashboard at the time of publishing, such as data collection certifications, item category, etc.
  6. Test your extensions for crashes, broken features, and bugs prior to submission.
  7. Verify that your contact information is correct to ensure you receive important communications for the Chrome Web Store. Some of these emails will require action on your part. Failing to respond could result in the removal of your item from the Store.
  8. Include detailed information in the single purpose field regarding your extension’s primary functionality.
  9. Provide meaningful customer support for your extension.
  10. Chrome Web Store policies are subject to change. Google may update the policies at any time, and developers are responsible for keeping up-to-date with any changes and complying with the updated policies. Updates to our policies will be announced via email to the address listed in your developer account.