TL;DR for fellow indie devs: 86.3% of Chrome extensions on the store have fewer than 1,000 active users. The path from 0→1,000 isn't a sprint — it's 4 phases, each with a different playbook. Skip a phase, the funnel breaks. This is the field-tested system I share with everyone who DMs me asking "how do I get installs?"
Here's a number that reframes everything about Chrome extension marketing:
86.3% of extensions on the Chrome Web Store have fewer than 1,000 active users. Nearly 70% have fewer than 100.
The store hosts 137,000+ extensions. The vast majority are essentially invisible — and it's not because they're bad. It's because shipping a great extension and marketing a great extension are completely different skills, and the dev community talks endlessly about the first while quietly struggling with the second.
If you've launched (or are about to) and feel like you're shouting into a void, this playbook is for you.
The Cold-Start Problem Nobody Talks About
Before the tactics, the structural problem you're fighting:
The Chrome Web Store's discovery algorithm weights heavily on ratings, recent installs, and engagement. In other words: the more users you have, the more new users you get.
- Extensions with zero ratings don't rank
- Extensions that don't rank don't get found
- Extensions that don't get found don't accumulate ratings
This is the cold-start loop. Simply publishing and waiting doesn't work. You have to manually break the loop by importing early users from outside the store — enough installs and ratings to become visible before organic search kicks in.
The 1-10-100-1000 framework maps exactly to this reality.
Phase 1: Installs 1→10 — Your Network Is Your First Market
The first 10 installs don't come from marketing. They come from people who trust you enough to try something unproven.
This is not a moment for pride. Message everyone — former coworkers, Discord friends, X followers, family on Chrome. The ask: "Install it, use the core feature once, and leave an honest star rating if it worked." Don't ask for 5 stars. Ask for honest. Authentic early reviews crush obviously coerced ones in the algorithm's eyes.
What actually works here:
- Dev communities you're already in. A loose Slack/Discord member dropping "I just shipped this, would love 5 min of feedback" converts way better than cold asks from strangers.
- Build-in-public on X. If you've been posting progress, launch becomes an event. Even a small audience converts at unusually high rates because they feel invested.
- Your email list, however small. 50 opted-in subscribers > 5,000 cold impressions. If you don't have one yet, start today — even a 3-line landing page.
The goal isn't scale. It's getting enough legitimate installs and ratings to stop looking like a brand-new untrusted extension to the CWS algorithm.
Phase 2: Installs 10→100 — Communities That Actually Convert
Once you have a handful of ratings, you're ready to go to communities. This is where most devs make their biggest mistake: spam every relevant subreddit with a link dump, get banned, and conclude "community marketing doesn't work."
Community marketing works only when you show up as a member first, marketer second (or not at all).
The 5 communities that genuinely move the needle for extension launches:
r/chrome_extensions
Built for exactly this. Show-and-tell posts welcome. The format that converts: lead with the problem, not the extension.
"I was spending 20 minutes a day doing X manually, so I built an extension that does it in 2 clicks"
…will out-perform "Check out my new extension!" every time. Engage in the thread. Thank people for criticism. The algorithm + the community both reward presence.
r/SideProject
Broader audience, less technically narrow. Best for extensions with mainstream appeal. Share the build story.
IndieHackers
Audience = other makers. They understand the early-distribution grind. A genuine "I built this and here's what happened in week 1" post performs extremely well. Brutal honesty about what's broken gets way more engagement than pure promotion. IH readers may not be your end users, but they share and link in ways that generate downstream traffic.
Product Hunt
Less potent than 3 years ago, but still matters for the indexed content, backlinks, and signals it generates. The #1 trap: treating PH as your big launch moment. It should be one node in a coordinated multi-platform push.
- Launch Tue/Wed/Thu, never Mon/Fri
- 12:01 AM Pacific — votes reset daily and you want maximum runway
- Do not launch until you have 20+ installs and a few ratings; the "coming in hot" story needs you to actually be hot
Hacker News — Show HN
Highest ceiling, highest variance. A landing Show HN drives thousands of users in 48 hours. One that doesn't disappears.
What works on HN:
- Technical credibility
- Genuine novelty
- Compelling problem statement
What doesn't: vague "productivity" claims, marketing language, anything that reads like a press release. Write your Show HN like you're talking to a senior engineer who'll immediately probe your technical decisions.
Phase 3: Installs 100→1,000 — Building the System
Getting from 100 to 1,000 requires shifting from individual effort to repeatable channels. The tactics that got you to 100 won't scale.
Chrome Web Store SEO — The Underrated Growth Engine
Past the 200-user mark, organic CWS search drives a massive % of installs. Most devs treat their listing as a one-time setup. Treat it like a landing page you continuously optimize.
- Title: Primary keyword in the title — not buried in the description. "Tab Manager Pro" won't rank. "Tab Manager: Group, Save & Restore Chrome Tabs" will. CWS now uses NLP intent matching; natural keyword placement beats exact-match stuffing.
- Short description (132 chars): Above-the-fold hook. Problem + audience. Don't repeat your title.
- Detailed description: Structure it like a landing page. Benefits before features. Bullets for scannability. Secondary keywords naturally — not a keyword soup at the bottom.
- Screenshots that convert: They load before the description on mobile and are often the only thing a user sees before installing. Annotated mockups with clear value callouts convert way better than raw UI dumps.
💡 If you want shortcuts here, I've been using ExtensionBooster's free Screenshot Makeup tool for annotated CWS screenshots and Tile Cropper to nail the dimensions. Both free, no signup. Saves a ton of Figma time.
The Review Flywheel
Ratings → rankings → installs → ratings. To spin it, you need a systematic (not spammy) approach.
The only prompt timing that works reliably: after a clear success moment. If your extension saves a step, show the prompt right after that save. Not on first install. Not on a timer. After value delivery.
Keep the ask simple: "Enjoying [Name]? A quick star rating helps other developers find it." One tap. No guilt-tripping.
The Cold-Start Hack Most Indie Devs Miss
Here's the part most growth guides skip because it sounds taboo: there's a legitimate, compliant way to accelerate the cold-start.
ExtensionBooster runs a real-user review and install model — actual Chrome users (other devs in the ecosystem) install your extension and leave genuine reviews. Not bot installs. Not fake reviews. A credit-based marketplace where real humans evaluate your product.
For a 50-install extension trying to break into organic search, a modest ExtensionBooster campaign can be the difference between staying invisible and hitting the threshold where the algorithm starts surfacing you. It's the warm-start mechanism CWS doesn't give you natively.
(Disclosure: I write for the EB blog — but the reason I keep recommending it is the alternative is waiting 6 months hoping organic finds you.)
Content That Pulls — Not Pushes
Highest-ROI content play for extension devs: a tutorial that solves the same problem your extension solves — manually, step by step — then mentions your extension as the automated version.
This works for 3 reasons:
- Genuinely useful, so people share it
- Ranks for the same keywords your target users search
- Converts readers at unusually high rates because they just spent 5 min doing the manual version and are highly motivated to never do it again
Publish on your own site (SEO benefit) then cross-post to DEV, Medium, Hashnode for distribution. (Yes — DEV crossposts via the canonical URL pattern this post is using. Free SEO juice + new audience.)
The Week-by-Week Timeline
| Week | Focus | Target |
|---|---|---|
| 1 | Network outreach, first installs, polish CWS listing | 10 installs, 3+ ratings |
| 2 | r/chrome_extensions post, IH intro, X launch thread | 25–40 installs |
| 3 | Product Hunt prep (assets, hunter outreach), r/SideProject | 50–75 installs |
| 4 | Product Hunt launch, Show HN if technically compelling | 100–150 installs |
| 5–8 | CWS SEO iteration, ExtensionBooster campaign, content marketing | 300–500 installs |
| 9–12 | Organic search starts contributing, review flywheel active | 700–1,000 installs |
Weeks 9–12 are where most devs give up — right as organic search is starting to work. The trough between "I've done all the launch stuff" and "organic is kicking in" feels like failure. It's not. It's latency. Hold the line.
What Doesn't Work (Honestly)
- X threads without prior audience. A thread about your extension with 200 followers = 4 impressions and 0 installs. Build-in-public works only if you've been building in public for months before launch.
- Mass cold outreach. Emailing 50 tech bloggers generates unsubscribes. One warm intro from a mutual outperforms 100 cold emails.
- Buying fake reviews. Google's detection improved dramatically. Pattern-similar phrasing, no-history accounts, single-cluster geographies → flagged → reviews removed → listings suspended in severe cases. The risk-reward is catastrophic. Real installs + authentic reviews are the only sustainable path.
- Ignoring your first 10 1-star reviews. Public, thoughtful responses signal to potential installers that there's a human dev who cares. Converts skeptics better than any marketing copy.
The One Metric That Predicts Everything
Of all the metrics you can track — install count, star rating, impressions — the one that best predicts long-term success is:
Weekly active users ÷ total installs
- High ratio (40%+): people who install actually use it → core value is real → every new install compounds
- Low ratio: conversion/onboarding problem no amount of marketing will fix
Fix retention before scaling marketing. An extension people actually use generates organic word-of-mouth, prompt-driven reviews, and the engagement signals that push CWS rankings up.
Putting It Together
The first 1,000 installs aren't a marketing campaign. They're a system — channels activated at the right time with the right message, building on each other toward the threshold where organic takes over.
If you want a head start, the free tools at ExtensionBooster.com handle most of the painful CWS asset work — Screenshot Makeup, Tile Cropper, and Download Reviews (huge for competitor review analysis — your users' language is already written in your competitors' reviews).
And when you hit the week-4-to-8 trough, remember: 86% of extensions never reach 1,000. The ones that do aren't necessarily better products. They're products built by devs who stayed systematic long enough for organic to kick in.
Originally published on extensionbooster.com — where I also write about Chrome Web Store ASO and the AI discovery channel for extensions. What channel worked for *your first 100? Drop it in the comments — always looking for more data.*
Top comments (0)