Add-on review is a process where add-ons are examined to confirm they meet Google's design, content, and style guidelines prior to being published publicly. Add-on review ensures that add-ons presented in the Chrome Web Store and G Suite Marketplace provide a good user experience, which in turn reflects well on the add-on developer.
Add-on review is occurs during the publication process. For Gmail add-ons, the add-on review process is started when you explictly request review; your add-on must be whitelisted by the review team before you can configure the G Suite Marketplace SDK and select public visibility. For editor add-ons, add-on review is triggered at the end of the publication process, at which point a review request is automatically generated and sent to Google's internal review team.
After a review team member makes their initial assessment, they will send you an email to tell you whether your add-on has been approved or needs more work. If your add-on requires additional work, the add-on review team will send you a review document containing specific information about what aspects of the add-on need improvement. Address all highlighted issues and follow the provided instructions to resubmit your add-on. Many developers are required to improve their add-ons prior to public release; some may be required to do this multiple times. You may always contact our review team for more information and guidance with this process.
Once the review team's concerns (if any) are satisfied, you are informed that your add-on is approved for publication. For Gmail add-ons you must finish the remainder of the publication process to have the add-on appear in the G Suite Marketplace. Editor add-ons are automatically added to G Suite Marketplace upon approval.
Areas of review
The review team examines the several aspects when considering an add-on for publication. Your add-on should do the following to maximize its chances of passing review:
- Present a well-designed user interface and experience.
- Take appropriate steps to safeguard user data.
- Adhere to the style guidelines for your add-on; see the Gmail add-on style guide or editor add-on style guide.
- Ensure your add-on contains no malicious code or other unacceptable content. See the Chrome Web Store Developer Agreement and the G Suite Marketplace Developer Agreement for guidelines.
- Request verification of your add-on prior to starting the publication process.
- Avoid using restricted scopes if at all possible. If you must use restricted scopes, comply with all the Additional requirements for restricted scopes.
The amount of time it takes to review an add-on can vary depending on how many add-ons have been recently submitted for review and how many corrections the add-on requires. It is not uncommon for an add-on review to take several days to complete, so take this into account when planning your development and publishing timelines.
You can improve your chances of a speedy approval by making sure your add-on meets all the guidelines and has a polished user experience prior to starting the publishing process.