How to Launch a Chrome Extension: A Practical Checklist

Building the extension is the part most makers enjoy. Launching it is the part that decides whether anyone ever uses it. This checklist covers what to do in the weeks before and after you press "Submit for review", in the order that tends to save the most time.

It comes from shipping several extensions ourselves and watching what slowed each one down. Where something is our observation rather than a published rule, we say so.

Before you submit

Write the one-sentence job of the extension

The Chrome Web Store expects an extension to have a single, clear purpose. Write that purpose in one sentence now, before you write any store copy: "Exports your Instagram followers to a spreadsheet", "Blocks cookie banners", "Saves your open tabs as a session".

If the sentence needs the word "and" more than once, the extension is probably two products. Reviewers read your listing against your permissions, so a muddled purpose is also a review risk.

Ask for the narrowest permissions that work

Every permission you request is shown to the user at install time and read by the reviewer. Broad host permissions (access to every website) draw more scrutiny and more drop-off at the install prompt. If your extension only works on one site, request that site and nothing else.

A useful test: for each permission, can you point to the line of code that needs it? If not, remove it.

Prepare the listing assets

Have these ready before you open the developer dashboard:

• Icon: 128 by 128 pixels.
• Screenshots: at least one, up to five, at 1280 by 800 (or 640 by 400). Show the extension doing its job, not an empty state.
• Promo images: a small promo tile (440 by 280) and a marquee (1400 by 560) are used when the store promotes extensions, so prepare them even though you can submit without them.
• Short description: the description field in your manifest is capped at 132 characters. It is what shows in search results, so it does more work than any other sentence you write.
• Privacy policy: if you handle user data at all, you need a public privacy policy URL. Write it plainly: what you store, what leaves the browser, what you never collect.

The next post, the Chrome Web Store listing checklist, goes through each field in detail.

Submitting and review

Expect a wait, and plan around it

Review time varies. In our experience small updates to an established extension have been approved within an hour, while a first submission can take days. A first submission with broad permissions can take longer. Do not schedule a public launch date until the extension is approved and live.

Read the rejection reason literally

Rejections cite a specific policy. Fix exactly what it names and resubmit rather than arguing. Two real examples from our own listings:

• A description that listed many brand names (apps and sites the extension works with) was rejected as keyword spam. Describing what the extension does in plain sentences fixed it.
• A listing with a "who it's for" list of professions and audiences was rejected for the same reason.

The lesson is that lists of names, sites or audiences in a description look like keyword stuffing, even when each item is true.

Avoid trademarks in your extension name

Putting another company's trademark in your extension's name is a common cause of takedowns. Describe what the extension does ("Export group members to Excel") and keep brand names for factual compatibility statements where the policy allows them. After one of our extensions was taken down over its name, we renamed it to a descriptive title and republished.

The first week after you go live

Put the listing link everywhere you control

Your own website, your GitHub README, your email signature, your social profiles. These cost nothing and send the first trickle of installs. Add a "Add to Chrome" button to a page on your site that explains the problem the extension solves.

List it on launch directories and in communities

Submit to directories that accept extensions and post in communities where your users already are. Each community has rules about self-promotion; read them first. Our guide to places to submit a Chrome extension covers what each type gives you.

Ask your first users for a review

Early ratings matter because a new listing has no social proof. Ask users who have just had a good experience, inside the product, at the moment of success. Never offer rewards for ratings; that breaks store policy.

Track what happens

You need three numbers from day one: installs, active users and, for paid extensions, buyers. The store dashboard gives you installs and users. For rankings, note which search terms you want to appear for and check where you stand, then check again weekly. We cover how in tracking your Chrome extension keyword rankings.

A launch day order that works

1. Listing is live and you have installed it from the store yourself.
2. Your website page and README link to it.
3. Submit to directories and post in one or two communities.
4. Reply to every comment and every review the same day.
5. Write down your starting rank for your five main keywords.
6. Repeat the directory and community steps for the next new feature, not the same one.

What to do next

If you want a free place to list your extension, collect upvotes and track keyword positions, you can submit your extension to Extension Club. The listing fills itself in from your store link.