How to Get Users for a Chrome Extension (Without Paid Ads)
How to market a Chrome extension for free: a listing that converts, Chrome's own ranking factors, review rules, and where first users come from.
By The Larvabot team7 min read
Before you spend anything on ads, three free things matter more for a new Chrome extension: a store listing built the way Google's own guide describes, enough real usage and honest reviews to earn the store's trust signals, and getting in front of people who already have the problem you solve, in the communities where they actually ask about it. Paying for installs or reviews isn't a shortcut — it's the fastest way to get removed.
What makes a Chrome Web Store listing actually convert?
Chrome's own listing guide is specific about what matters, and most of it is free to fix today.
- Title: Clear and descriptive enough that someone understands the core function from the name alone. Short and unique beats keyword-stuffed.
- Summary: 132 characters, plain text, highlighting the features that match your main use case. No generic praise or superlatives, and no mentioning competing extensions by name.
- Description: An overview paragraph, then a short feature list. Concise, accurate, no typos. Google's Keyword Spam policy can get an item suspended for repetitive or irrelevant keywords stuffed in here.
- Store icon: Simple and recognizable — your brand or developer logo, not a screenshot or UI element, which gets hard to read at small sizes.
- Screenshots: At least one, ideally the full five, at 1280×800 or 640×400, full-bleed with square corners, showing the real UI on the current version.
- Promotional images: A 440×280 small tile (shown on the homepage, category pages and search) and, if you're featured, a 1400×560 marquee image — high-resolution, on-brand, and not just a screenshot.
- Prohibited claims: Don't write "Editor's Choice," "Number One," or anything else that misrepresents your status, including on promotional images.
(All of the above is from Chrome's "Creating a great listing page" guide, checked November 2026.)
How does the Chrome Web Store actually rank extensions in search and discovery?
Google's own discovery documentation names four things the ranking heuristic weighs: your listing's metadata completeness, user ratings, usage trends (downloads compared with uninstalls over time), and qualitative signals like design appeal, a clear purpose, and easy onboarding (developer.chrome.com/docs/webstore/discovery).
Two badges sit on top of that:
- Featured badge: Nominated through Chrome's One Stop Support form. You need to own the extension, publish it publicly with English support, have no active policy violations, and the core features must work without requiring extra credentials or payment. It can raise your search and filter ranking and earn promotional placement — but it can't be bought.
- Established Publisher badge: Granted automatically once your publisher identity is verified and you have a consistent, policy-compliant track record with Google. New developers need a few months of clean history first. Google's own page says roughly 75% of current extensions meet this standard, so it's a bar most serious, policy-compliant developers eventually clear.
New extensions can take a few hours to get indexed after publishing; if yours isn't showing up, check the regions selected in your Distribution tab first.
Do the permissions you request affect whether people install?
Yes, directly — Chrome shows requested permissions to the user before they install, so a long or scary-looking permission list is a conversion killer before anyone even sees your extension in action. Chrome's own policy requires developers to "request access to the narrowest permissions necessary" for the extension's features, and to pick the option with the least data access when more than one would work (developer.chrome.com/docs/webstore/program-policies/policies). You also can't "future-proof" by requesting permissions for features you haven't built yet.
The same policy requires a single, narrow, easy-to-understand purpose. Bundling unrelated functionality — the page's own examples are a ratings tool that also injects ads, or a news aggregator that also handles email notifications — is a quality violation, and removal is permanent unless you fix it with a revision. Practically: if you're tempted to add an unrelated feature to boost perceived value, ship it as a second extension instead.
Can you ask users for reviews, and what crosses the line?
Asking is fine. Paying, requiring, or gating features behind a review is not. Chrome's Spam and Abuse policy explicitly bans manipulating "the placement of any extensions in the Chrome Web Store," and names inflating ratings, reviews or install counts "by illegitimate means" — including fraudulent or incentivized downloads, reviews and ratings — as a specific example of what's prohibited (developer.chrome.com/docs/webstore/program-policies/spam-and-abuse).
In practice, that means: prompt for a review after someone has used the extension successfully a few times, never before they've gotten value, and never with a discount, unlock, or any other reward attached.
Where do you find your first real users?
The store rewards extensions that already have usage and ratings, which is exactly what a brand-new listing doesn't have — so your first users almost always come from outside the store.
- Go to the community where the underlying problem gets discussed, not just extension subreddits. If you built a tool for freelancers tracking invoices, the people who need it are in freelancer and small-business communities, not only r/chrome_extensions. How to promote on Reddit without getting banned covers finding the right subreddit and posting in a way that doesn't read as spam.
- Submit to the free directories and launch sites that are still worth the hour it takes. Free startup directories that still send traffic lists which ones are actually worth your time, and Show HN's own rules explain what qualifies if your extension is open source or solves a genuinely technical problem.
- Watch for people already asking for something like yours. Someone posting "is there an extension that does X" in a relevant subreddit or forum is a warmer lead than anyone you cold-pitch. Larvabot's Reddit watch is built for exactly this: it scores posts asking for what you've built and drafts a reply you post yourself.
- Reach out to roundup blogs and newsletters in your extension's niche, not general "Chrome extension" roundups — a time-tracking extension belongs in a freelancer newsletter, not a generic tech blog. Read a few of their past issues first so your pitch actually fits what they cover.
- Write the page that answers the exact question your extension solves. Someone searching "how to track billable hours in the browser" is closer to installing than someone searching "best Chrome extensions 2027." A simple page targeting that specific problem, with your extension as the answer, compounds in search long after a single Reddit post or directory listing stops sending traffic.
This is the same channel-by-channel thinking behind how to get your first 100 users: a few channels done properly beat a long list done badly.
What's a realistic number of users to expect?
Low, at first, almost everywhere. Profitable's Chrome Web Store statistics, which tracks live install counts reported by the store itself, puts the median Chrome extension at around 10 users, with roughly 8% ever reaching 1,000 users and about 0.5% reaching 100,000 (checked November 2026, from 343,500 live extensions). That's the backdrop you're marketing against: a handful of real, engaged users who leave honest reviews will do more for your ranking than a large number who install once and forget it.
If your extension is genuinely useful but installs stay flat for weeks, the listing and discovery sections above are the first places to check — a vague summary, a blurry screenshot, or a title that doesn't say what the extension does will quietly cap your conversion rate no matter how much outreach you do.
Frequently asked questions
Can I pay for Chrome extension installs or reviews?
No. Chrome's Spam and Abuse policy explicitly prohibits inflating ratings, reviews or install counts through fraudulent or incentivized activity, and extensions found doing it can be removed from the store.
How long does it take for a new Chrome extension to show up in search?
Usually a few hours after publishing. If it still isn't appearing after that, check that you've selected the right regions in the Distribution tab of your developer dashboard.
Does the Chrome Web Store favor extensions with more installs?
Install counts matter, but Google's own discovery documentation says the ranking heuristic also weighs ratings, the trend between downloads and uninstalls, and qualitative signals like a clear purpose and easy onboarding — not raw install count alone.
What's the Established Publisher badge, and do I need it?
It's an automatic badge for developers with a verified identity and a clean policy record over time. You don't need it to publish or get users, but Google's own page notes most compliant, longer-running developers eventually earn it, and it can help with user trust.
Is Reddit or Product Hunt better for a new Chrome extension?
It depends on what the extension does. A developer tool fits Show HN or a programming subreddit; a consumer productivity extension fits the community built around the problem it solves (freelancers, students, shoppers). Pick the audience with the problem first, then the platform they're already on.