I Just Published My First Chrome Extension. Now What?

You clicked Publish. The zip file uploaded. The Chrome Web Store dashboard now shows your extension with a little Pending review badge.

Congratulations — you’re officially a browser extension developer.

But what actually happens next?

We analyzed 185,000+ public Chrome extensions to get a realistic picture of what happens after launch — and what new developers should expect.

Key takeaways

• The median Chrome extension has just 18 users.
• If you break 100 users, you’ve already outperformed most of the store.
• Half of all extensions have zero ratings.
• The Chrome Web Store is a distribution channel, not a built-in growth engine.

If you just published your first extension and your numbers look underwhelming, that’s not failure. That’s normal.

First: the review process

After you hit publish, your extension goes into Google’s review queue.

Google says review times vary. In its documentation, it notes that in early 2021, most submissions were reviewed in under 24 hours and over 90% completed within three days — but actual timelines depend on what your extension does and what permissions it requests.

Things that can slow review down:

• broad permissions like <all_urls>
• remotely hosted code
• sensitive behavior like browsing-data access or script injection
• a brand-new developer account

Common rejection reasons include:

• asking for permissions you don’t really need
• missing or vague store listing metadata
• broken functionality
• privacy-policy issues when your extension handles user data

None of this is unusual. A rejection is usually a revision cycle, not a dead end.

Then comes the part no one tells you about: almost nobody gets users quickly

A week after launch, you open the dashboard and see:

• 4 users
• maybe 11
• one of them is probably you

That feels bad until you look at the broader market.

Here’s what the user distribution looks like across 185,459 active Chrome extensions in our dataset:

That means the median extension has 18 users total.

And here’s the more useful framing:

• 70.3% of extensions currently have fewer than 100 users
• 87.9% currently have fewer than 1,000 users
• only 12.1% are at 1,000+ users

So if your first milestone is 100 users, that is not small. That is meaningful.

The Chrome Web Store is extremely skewed. A small number of giant extensions absorb most of the installs. Everyone else is competing in the long tail.

Ratings are even harder than installs

Most new developers assume that if they get a few users, ratings will follow.

Usually they don’t.

In our data, 50.5% of active Chrome extensions currently have zero ratings. The median number of ratings across the store is exactly zero.

Among extensions that do have ratings, the numbers look much better:

• median rating: 5.0
• average rating: 4.56

That tells you two things:

1. Getting the first rating is the hard part
2. Once people do rate, they’re often rating after a positive outcome

So early on, don’t obsess over stars. With only a handful of ratings, one annoyed user can distort the picture completely.

What matters more is whether your early users are actually succeeding with the product.

The Chrome Web Store will not market your extension for you

This is the biggest misconception I see.

A lot of developers publish to the Chrome Web Store as if it were an app marketplace with built-in discovery. It isn’t.

Google’s discovery docs make it clear that ranking and visibility depend on things like:

• ratings
• usage signals
• uninstall rates over time
• listing quality
• UX quality
• clarity of purpose

So yes, new extensions are at a disadvantage. Not because listing quality doesn’t matter — it does — but because quality alone usually isn’t enough to create traction from zero.

There are discovery surfaces:

• search
• categories
• homepage features
• editorial placements
• badges

But for a brand-new extension with no installs, no ratings, and no retention history, visibility is limited.

That’s why your listing matters so much: the store probably won’t create demand for you, but when traffic does arrive, your listing determines whether that traffic converts.

Badges matter more than most people think

There are two Chrome Web Store trust signals worth knowing about:

Featured Badge

This is awarded by Google to extensions that meet higher UX and technical standards.

It is manually reviewed, but developers can nominate eligible public extensions for consideration through Google’s support flow.

Established Publisher Badge

This badge is granted to verified publishers with a strong compliance track record.

Google says badge holders may receive better visibility in search and filtering, so this is more than cosmetic trust signaling.

If you plan to be in the ecosystem for real, this stuff matters.

What actually helps after launch

1) Treat your store listing like a landing page

A lot of developers underinvest here because it feels superficial. It isn’t.

Your listing should do three things quickly:

• explain the problem
• show the workflow
• create trust

That means:

• lead with user benefit, not implementation details
• use screenshots that show the extension doing real work
• choose the most accurate category for the use case
• include clear privacy information, especially if you handle user data

Even a good extension can look sketchy if the listing is thin.

2) Bring your own audience

Early installs usually come from places where your users already hang out, not from the store itself.

For developer-facing or technical extensions, that often means:

• dev.to
• Hacker News
• Reddit
• niche Discord servers
• Slack communities
• X
• GitHub discussions
• indie maker communities

The best early distribution angle is usually not “here’s my product.”

It’s:

• “I built this because I had this problem”
• “here’s how it works”
• “here’s what I learned”
• “here’s the ugly first version”

That performs better with a dev audience because it feels like shipping, not marketing.

3) Use early feedback as product direction

At the start, you do not need scale. You need signal.

If one user emails a bug report, that’s valuable.

If three users get confused at the same step, that’s a usability problem.

If someone asks for the same feature twice, that’s roadmap input.

The first version of your extension is rarely the version that grows.

The extensions that eventually compound are usually the ones where the developer keeps shipping after the silent launch period.

4) Benchmark your progress properly

One of the hardest parts of shipping a Chrome extension is that most developers have no idea what “normal” looks like.

That’s exactly why we built exstats.com: to track installs, ratings, and trends across the Chrome extension ecosystem and make it easier to benchmark progress against the market.

Without context, 30 users feels disappointing.

With context, 30 users might mean you’re ahead of the median already.

That distinction matters.

A more realistic mental model

A lot of developers think launching an extension should feel like launching a SaaS product.

Usually it doesn’t.

A more realistic model looks like this:

Week 1

• review approval, if all goes well
• a handful of users
• probably no ratings

Month 1

• maybe 10–50 users if you’ve posted it in a few places
• maybe your first review
• some first real bug reports

Month 3

• clearer understanding of who it’s actually for
• better onboarding
• a stronger listing
• a few iterations based on real usage

Month 6+

• compounding starts only if you kept improving it
• some organic search visibility may show up
• retention and word of mouth begin to matter more

These are not guarantees. They’re just a healthier expectation model than “I launched, why am I not growing?”

The real takeaway

The biggest mistake first-time extension developers make is treating the publish button like the finish line.

It isn’t.

Publishing is the starting line.

Most extensions launch quietly. Most get very few users. Most get no ratings at all for a long time. That does not mean the idea is bad.

It usually means you are now in the real phase:

• improve onboarding
• simplify permissions
• tighten the listing
• share it where the right users already are
• respond fast to feedback
• ship updates

That’s how extensions grow.

Not from launch-day excitement, but from consistency after launch.