Chrome Web Store migration

In order to streamline the add-on discovery experience for users and to facilitate add-ons publication, we are phasing out publication of add-ons to the Chrome Web Store. Once this process is completed, the G Suite Marketplace will be the sole add-on store; Chrome extensions will continue to be presented in the Chrome Web Store and are unaffected by this change.

To prepare for this shift, all add-ons must have a G Suite Marketplace listing prior to January 25, 2019. In the short term this means editor add-ons will be listed in both the Chrome Web Store and the G Suite Marketplace, but sometime after this date the add-on Chrome Web Store listings will be removed.

This guide provides information about this migration, and explains the steps you need to take (if any) to ensure your add-ons are listed properly in the G Suite Marketplace when published.

Background

Originally when a developer published an editor add-on the resulting listing was added to the Chome Web Store. When a user selects Add-ons > Get add-ons... from the editor menu, the resulting dialog is populated from Chrome Web Store listings.

In addition to publishing in the Chrome Web Store, developers could optionally publish in the G Suite Marketplace as well. This was referred to as publishing for domain-wide installation, because doing so would allow domain admins to find the add-on in the G Suite Marketplace and install it on behalf of their domain users.

The decision to phase out the Chrome Web Store means that publishing for domain-wide installation is no longer optional. For now, new and existing add-ons must be published to both stores, but once the phase out is complete add-ons will only need to publish to the G Suite Marketplace.

Once this phase out is complete, the G Suite Marketplace will handle all add-on listings, for users and domain administrators.

What you need to do

Depending on how you published your add-on, you may need to take action. Read the following to determine what actions are required, if any.

  • If your editor add-on isn't published yet, publish it to both the Chrome Web Store and the G Suite Marketplace. Sometime after January 25, 2019 these instructions will be revised again to only describe publication to the G Suite Marketplace.

  • If your editor add-on is already present in the G Suite Marketplace (because you published it for domain-wide installation), you do not need to take any further action.

  • If you published your editor add-on but it only is present in the Chrome Web Store, you must create a new G Suite Marketplace listing for your add-on.

Create a new G Suite Marketplace listing for an editor add-on

If your editor add-on was published but not for domain-wide installation, the add-on's listing only appears in the Chrome Web Store. To migrate your add-on, you must take a few steps to create a new G Suite Marketplace listing:

  1. Review the required assets for G Suite Marketplace listings and make sure you have these assets for your add-on. These assets are used to define the appearance and content of your add-on's G Suite Marketplace listing. The add-on's original Chrome Web Store listing also uses some of these assets; you can simply provide the same asset again.
  2. Enable the G Suite Marketplace SDK in your add-on's Cloud Platform project, if it isn't already.
  3. Complete the Configuration panel in the SDK settings, using the assets you assembled. Be sure to click Save changes when finished.
  4. Complete the Publication panel in the SDK settings, using the assets you assembled.
  5. In the Publication panel, click Publish to start the publication process.

FAQ

This section provides answers to some common questions about this migration.

Are Gmail add-ons or Hangout Chat bots affected?

No. All published Gmail add-ons and Hangouts Chat bots already appear in the G Suite Marketplace. You don't need to take action for these applications.

What happens if I don't or can't add a G Suite Marketplace listing to my add-on by that date?

At some point on or after the January 25, 2019 deadline, your add-on listing will be removed from the Chrome Web Store. When that happens, new users will be unable to find or install the add-on. Users that have already installed the add-on can continue using it, but if they ever uninstall the add-on they won't be able to re-install it again.

Is the Chrome Web Store being shut down?

No. The Chrome Web Store is simply not the best place to showcase add-ons, and it is better to have add-on listings in one location so that users and domain administrators can find them more easily.

If my editor add-on is privately published/visible, do I need to migrate?

Yes.

Does migration require my editor add-on to be reviewed again?

By itself, no. However, if you also make updates to your add-on code that change its authorization scopes an additional review may be required when you republish in the G Suite Marketplace.

How does migration to the G Suite Marketplace affect my editor add-on user installs, user ratings, and user reviews?

If the add-on was previously only published in Chrome Web Store, user installs, reviews, comments, and star ratings will be migrated to the new G Suite Marketplace listing. Since user installs are migrated, your existing add-on users can use the add-on without interruption.

For add-ons that were already published to both Chrome Web Store and G Suite Marketplace, only the Chrome Web Store user installs will be migrated to G Suite Marketplace.

If my editor add-on is currently bundled with another G Suite Marketplace app, do I need to create a separate listing for it?

No. If you bundled your editor add-on with a G Suite Marketplace app, the add-on is currently using that app's Cloud Platform project and its G Suite Marketplace listing. You don't need to take extra action in this case.