Stores & marketplaces

Google Workspace Marketplace

Add-on store for Gmail, Docs, Sheets and other Workspace apps.

Visit workspace.google.com
Cost
Free

Free to list. Check current terms for paid add-ons.

Verdict
slow burn

Reaches people who use Gmail, Docs and Sheets. Listings go through Google review, which takes time.

Difficulty
Medium

Needs preparation, a review, or a steady habit before results.

Effort
Medium

About 5 to 10 hours a month.

First result
1 to 3 months, including review

A rough range for one person working on it part-time.

Payoff
Steady

a trickle that lasts while you run it.

Best for

Add-ons for Gmail, Docs, Sheets or Drive.

Not for

Products with no Google Workspace use.

Pros

  • Reaches Gmail, Docs and Sheets users
  • Clear add-on use cases

Cons

  • Google review and permission scrutiny
  • Narrow scope

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · All links answer

01What it is and who is there

The Google Workspace Marketplace lists add-ons and apps that run inside Gmail, Google Docs, Sheets, Drive and other Workspace products. People find add-ons by searching for the job they want done inside a tool they already open every day. The audience is anyone who uses Workspace, from solo users to large organizations.

02Cost and what you actually pay for

Listing fees and terms for paid add-ons are set by Google and can change. Check Google's current developer terms and marketplace policies before you publish, especially for a paid add-on.

03Is it right for you?

It fits add-ons that fix one job inside Gmail, Docs or Sheets, such as a template generator or a data cleaner. It fits poorly for products that never touch Google data, and for products that need a lot of permissions users will not grant.

04Before you start

  • Build the add-on or app with Google's developer tools.
  • Read Google's marketplace and developer policies, including the rules on requested permissions.
  • Prepare an icon, screenshots and a short description that names the job.
  • Request only the OAuth scopes you need. Broad scopes slow review and worry users.
  • Prepare a privacy policy that matches what the add-on does with data.

05Step-by-step: how to distribute here

  1. Build the add-on and test it with a normal Workspace account, not only your developer account.
  2. Submit it for Google's review. Allow time for at least one round of changes.
  3. Write a listing that names the job in the title and the first sentence of the description.
  4. Add screenshots that show the add-on doing the job.
  5. Tell existing users, and link the listing from your product's help page.
  6. Check reviews and support requests weekly, and fix permission or login issues first.

Timing: plan for review time. The timing is not published as a fixed number in the pages checked for this entry.

06What to post or submit

Listing title: [Job] for Google [Docs/Sheets/Gmail]

Short description:

[Product] [does the job] inside [app]. [One benefit]. [Free plan or pricing note, checked against current terms].

Privacy statement: state what data the add-on reads, what it stores and for how long, and whether it shares data with anyone.

07Common mistakes and do-nots

  • Do not request scopes you do not use. Google's review checks requested permissions.
  • Do not publish a privacy policy that does not match the add-on's behavior.
  • Do not stuff the title with keywords.
  • Do not leave support requests unanswered. Reviews are public.

08How to measure it

  • Track installs and uninstalls from the Google Workspace Marketplace developer dashboard, if it shows them.
  • Track reviews and support requests after each release.
  • A realistic test: two to three months after listing, check whether installs are coming from search inside the marketplace or from your own promotion.

09Time budget

  • Before: 15 to 40 hours to build and test the add-on, depending on scope.
  • Review: 4 to 10 hours of changes.
  • Ongoing: 2 to 4 hours a month.

10Pair it with

11Sources

Sources