Google Marketplace Listing: A Step-by-Step Guide with Real Examples

You've built your add-on, passed OAuth verification, and now you're ready for the final stretch: getting your add-on listed on the Google Workspace Marketplace.

Here is the official guide from Google. Below I'll walk you through the full process—every asset, every field, every gotcha—based on my experience publishing the Doc to PDF add-on.

Watch the full walkthrough:

Step 0: Enable the Marketplace SDK

Before you can configure anything, you need to enable the Google Workspace Marketplace SDK API in your Google Cloud Project.

Go to your Google Cloud Console
Navigate to APIs & Services > Library
Search for Google Workspace Marketplace SDK and enable it
Go to Google Workspace Marketplace SDK > Manage

Here you'll configure the core settings:

App Visibility — Public (for anyone to install) or Private (organization only). Once published, this cannot be changed.
Installation Settings — Whether only admins or all users can install
App type — Select what your add-on extends (Docs, Sheets, etc.)
Apps Script deployment version — The version number from Extensions > Apps Script > Deployments. Make sure this matches your latest stable deployment.
OAuth Scopes — These should match what you declared during OAuth verification
Developer Information — Your developer name, website URL, and contact info

Once everything is configured, hit Save and move to the Store Listing tab.

Step 1: App Name and Descriptions

Application Name

This must be identical to your OAuth consent screen app name. This is a critical requirement—mismatches are the most common rejection reason.

Real example: When I first submitted Doc to PDF, I used Docs™ to PDF as the name. Google rejected it—they didn't want the trademarked form in the Marketplace name. I had to rename it to Doc to PDF in both the OAuth consent screen and the Marketplace listing. The key takeaway: update the OAuth branding first, then match the Marketplace name. Both must be in sync before you submit.

Short Description

Up to 200 characters. This appears in search results and the Marketplace card, so make it count. Focus on the core value proposition.

Example:

Convert Google Docs tabs to PDFs. Fast, secure, and easy. Supports merging and password protection.

Detailed Description

This is your full pitch. Google Marketplace supports basic formatting in descriptions. Structure it to be scannable:

Lead with the key features
Use line breaks to separate sections
Include a brief "how it works" flow
Mention your contact/support info at the bottom

TIP: This doesn't need to be perfect on the first pass. You can always iterate after publishing—just update the listing and save.

Pricing

Select the pricing model that matches your add-on:

Free — Completely free
Free with paid features — Freemium model (e.g., basic tier free, pro tier paid)
Paid — Requires payment to use

Step 2: Graphic Assets

You'll need to prepare several image assets in specific sizes:

Application Icons

Size	Usage
32×32 px	Small UI contexts
48×48 px	Marketplace search results
96×96 px	Marketplace listing
128×128 px	Marketplace detail page

Keep your icon consistent across all sizes. Use a simple, recognizable design that works at the smallest size (32px). These should all be the same icon, just at different resolutions.

220×140 px — This is the thumbnail that appears in Marketplace search results and browsing. It's the first visual impression users get of your add-on.

Tips from experience:

I use Canva to design these. Create a custom size canvas at 220×140 and design from there.
A white or light background tends to contrast better against the Marketplace UI. I tried a dark version first but switched to white after comparing how it looked in context.
Include your app name and a visual hint of what it does.

Step 3: Screenshots

Optimal size: 1280×800 px (16:10 aspect ratio). You can upload up to 5 screenshots.

This is where you can really sell your add-on. Here's what I learned:

GIFs are supported and recommended

Instead of static screenshots, consider recording short (~30 second) screen recordings and converting them to GIFs. They auto-play in the Marketplace listing and give users a much better sense of how your add-on works.

Size limit: Google doesn't officially document the max GIF size, but from my testing, GIFs around 2-3 MB work fine. I had issues with larger files and had to use freeconvert.com to compress my MP4-to-GIF conversions down to ~2 MB.

Order matters

The first screenshot is the most prominent—it's what users see without scrolling. Put your strongest visual first.

My approach for Doc to PDF:

Application card banner (enlarged) — Immediate brand recognition
GIF showing core feature — Converting a doc to PDF in action
Static screenshot — The add-on sidebar interface
Another GIF — Showing a secondary feature (merge tool)

The reasoning: most users won't scroll through all 5 screenshots. Front-load your best content.

Upload 1 YouTube video demonstrating your add-on. This appears in the listing's overview section.

What to cover:

The pain point your add-on solves
A live demo of the key features
Keep it between 2-4 minutes—long enough to be useful, short enough that people watch it

Tips:

Address the use case and pain point directly at the start
Show the actual user flow, not slides
You can use the same demo video style as your OAuth verification video, but focus on features rather than scopes
Copy the YouTube URL and paste it in the promo video field

Example promo video used for Doc to PDF:

Step 5: Links and Support Info

You'll need to provide several URLs:

Field	Required	Details
Terms of Service	Yes	Public URL to your ToS page
Privacy Policy	Yes	Public URL to your privacy policy
Support URL	Yes	Where users go for help (support page, email, contact form)
Help URL	No	Optional link to documentation or FAQ
Post-Install Tip	Recommended	A message shown after installation

Post-Install Tip example:

Need help? Reach out to contact@yourdomain.com

This small detail improves the user experience significantly. New users immediately know where to go if they have questions.

TIP: If you haven't created your privacy policy and terms of service yet, check out the OAuth Verification Guide where I cover exactly what Google expects in those documents.

Step 6: Test Before Submitting

Before you submit your listing for review, test thoroughly.

Use Test Deployments

In Apps Script, go to Deploy > Test deployments and create a new test. This simulates exactly what an end user will experience when they install your add-on from the Marketplace.

Best practices:

Create test documents for each use case your add-on supports
Test with the released version (not the development/head deployment)
Go through the full flow: install, open, use every feature, check edge cases
Test in an incognito window or with a different Google account if possible

This is your last chance to catch issues. Once the listing is live, every bug is a real user's problem.

Preview as Draft Tester

After filling in all listing details, click Save Draft and then View Marketplace Listing. You can preview exactly how your listing will appear. Only accounts listed as draft testers can see this preview—it's not public yet.

Check everything:

Name, description, and formatting
Screenshot order and quality
Video playback
All links work correctly

Step 7: Submit and Review Process

Once you're satisfied with the preview, submit your listing for review.

What to expect

Private apps — Published immediately to your organization
Public apps — Reviewed by Google, which takes anywhere from a few days to a few weeks

Common Rejection: Name Issues

The most frequent rejection reason I've seen (and experienced) is a name mismatch or trademark issue.

My real experience: Google initially rejected my listing because the name Docs™ to PDF didn't meet their requirements. I first thought it was the trademark symbol in the description, so I added ™ everywhere—still rejected. The actual issue was they didn't want that specific name format at all. I had to:

Change the OAuth consent screen name to Doc to PDF
Then update the Marketplace listing name to match
Resubmit

The OAuth name and the Marketplace name must always match. If Google asks you to change one, you need to change both.

After Approval

After your listing is approved, it becomes public. Anyone can find and install your add-on from the Marketplace.

Post-Approval: Enable Analytics

Don't skip this step. Go to Google Workspace Marketplace SDK > Manage and find the Analytics tab.

Opt in to Google Analytics to track:

Install and uninstall counts
User engagement metrics
Geographic distribution of installs

It takes a couple of weeks for data to start appearing, so enable this as early as possible. This data is invaluable for understanding how your add-on is performing and where your users are coming from.

The Full Checklist

Run through this before submitting:

Wrapping Up

The Marketplace listing is the final piece of the publishing puzzle. Compared to OAuth verification, it's more about presentation than compliance—but the details still matter. A strong listing with clear screenshots, a good demo video, and a polished description can be the difference between users installing your add-on or scrolling past it.

Take the time to get your graphic assets right, write descriptions that speak to your users' pain points, and test everything before you submit. If your listing gets rejected, don't stress—Google gives you specific feedback, and the second attempt usually goes through smoothly.

If you're earlier in the process, check out Google OAuth Verification: A Step-by-Step Guide for passing the verification step. And for strategies on growing your user base after publishing, see How I Market Google Workspace Add-ons and Finding Your Google Workspace Add-on Niche.

If you're building your add-on with ShipAddons, the boilerplate takes care of the technical infrastructure so you can focus on what matters: building a great product and getting it in front of users.