You published an extension and the install count barely moves. Most advice on promoting one is a few years old, and the Chrome Web Store changed in 2026: Google is retiring the Featured badge, the rating will focus on recent reviews and new publishers get two extension slots by default. This guide covers what changed, how the store ranks extensions, a listing checklist with Google's own specifications, the rules that get promoted extensions removed, which channel fits which kind of extension, a 30-day launch plan, a review request and uninstall survey you can copy and the numbers to watch each week. It is useful without a Soloop account.
The short answer
To market a Chrome extension, fix the store listing first, because the store ranks items partly on ratings and on installs compared with uninstalls, and a listing that sets the wrong expectation produces both bad reviews and uninstalls. Then choose one channel where the people with your extension's problem already talk, show the extension doing one job, and ask happy users for a review after they succeed, never in exchange for anything.
Badges are no longer a growth plan. Google stopped accepting Featured badge nominations on August 20, 2026 and will end the program later in the year, so the rating, recent reviews and retention are the quality signals you can still influence. Track impressions, installs and uninstalls every week and change one thing at a time.
What changed in the Chrome Web Store in 2026
Two announcements matter for anyone promoting an extension: a policy update on July 1 that tightened data rules, and a store update on August 20 that changed ratings, badges and publishing limits.
| Dimension | What changed | What it means for marketing |
|---|---|---|
| Featured badge | Being retired later in 2026. Self-nominations closed on August 20 and pending nominations were closed. | Do not plan a launch around getting the badge. Google says the refreshed rating is the main quality signal. |
| Rating | The displayed rating will focus on more recent reviews, as Google Play does. No formula or rollout date is published. | Old five-star reviews will count for less. Ask for reviews steadily, and fix the cause of recent complaints quickly. |
| Publishing limits | Each publisher has an extension limit, two slots by default. Existing extensions stay; increases are requested in the dashboard. | Put effort into one extension instead of publishing many small variants, which the spam policy also forbids. |
| Review and install checks | Uploads are tested for installation problems before you submit, and review levels are back to normal. No review time is promised. | Leave room in a launch date for review; publish first and announce after the listing is live. |
| Data collection (from August 1) | Data must be strictly necessary for the extension's disclosed single purpose, disclosed prominently, and users told when handling changes. | Growth tracking and marketing data outside that purpose are not allowed. Keep the privacy tab and your claims consistent. |
Pre-submission installation testing; review levels back to expected baselines; default of two extension slots; rating to focus on recent reviews; Featured badge sunset later in 2026, self-nominations closed August 20.
Chrome for Developers: Chrome Web Store updates (Aug 20, 2026)Data strictly necessary for the disclosed single purpose; prominent disclosure and notice of changes; new prohibitions on circumventing AI-service safeguards and on prediction markets; enforcement from August 1, 2026.
Chrome for Developers: Chrome Web Store policy updates (Jul 1, 2026)How the Chrome Web Store ranks and features extensions
Google describes ranking as a heuristic that weighs user ratings and usage, such as installs compared with uninstalls over time, along with a clear purpose, design, onboarding and ease of use. Search also reads the listing's metadata, so the title, summary and description decide which searches you can appear in. New items can take a few hours to appear in search.
Editors choose the home page and collections by hand. You cannot pay for placement, and collection requests are not accepted. The Established Publisher badge is given automatically to publishers with a verified identity and a good policy record, so verify your publisher identity early. In practice, the store rewards an extension that keeps the people who install it; marketing that brings the wrong people can hurt ranking.
Ranking heuristic weighs ratings and usage statistics such as installs versus uninstalls over time; search uses listing metadata; editors pick featured items; no paid placement or solicited collections; Established Publisher badge for verified publishers with a good compliance record.
Chrome for Developers: Discovery on the Chrome Web StoreChrome Web Store listing checklist
Most store visitors decide from the name, the summary and the first screenshot. Check each item before you promote the listing anywhere.
- Name: clear and specific about the main job, without a string of keywords.
- Summary: up to 132 characters of plain text that says who it helps and what it does; no superlatives or competitor names.
- Description: one overview paragraph, then a short list of the main features, using your keywords naturally. Repeating one keyword more than five times can be treated as keyword spam.
- Screenshots: at least one and preferably all five, at 1280×800 or 640×400, showing the real extension at work with little text.
- Small promo tile (440×280) for search and category pages, and a 1400×560 marquee image in case editors feature you.
- A short video or screenshot sequence that shows setup and the first useful result.
- Category: the closest of the current categories.
- Website and support links, and a privacy tab that matches what the extension actually collects.
- Testimonials only with a real name attached; anonymous quotes are not allowed.
- Localized summary and screenshots for the languages your users speak.
Summary limited to 132 characters; up to five 1280×800 or 640×400 screenshots; 440×280 small promo tile; 1400×560 marquee; no keyword stuffing; add website and support URLs.
Chrome for Developers: Creating a great listing pageUnnatural repetition of a keyword more than five times is keyword spam; unattributed or anonymous testimonials are not allowed; listings without a description, icon or screenshots are rejected.
Chrome Web Store policy: Listing requirementsPromotion that can get an extension removed
Some growth tactics that work elsewhere break Chrome Web Store policy. Removal costs you every install, so check a plan against this list before you start.
- Buying or trading installs, reviews or ratings, or offering anything in return for a review.
- Trying to manipulate where the extension appears in the store.
- Publishing near-copies of the same extension under different names to take more search space.
- Collecting browsing or personal data for marketing that is not needed for the extension's single purpose.
- Affiliate links, codes or cookies added without a clear user benefit, prominent disclosure and an action by the user.
- Notifications or messages users did not ask for, or messages sent for the user without letting them confirm the content and recipients.
No manipulation of placement; no fraudulent or incentivized downloads, reviews or ratings; no duplicate experiences; no notification abuse or unconfirmed messages.
Chrome Web Store policy: Spam and abuseAffiliate programs must be described prominently in the listing, the UI and before installation; each code, link or cookie needs a user benefit and a related user action.
Chrome Web Store policy: Affiliate adsChoose a channel by what the extension does
An extension is a small tool for a specific moment in someone's day. Go where people describe that moment, and show the extension handling it in a few seconds.
| Dimension | Where the first users are | First move |
|---|---|---|
| Developer tool | Hacker News, GitHub, developer communities and the issue threads where the problem comes up. | A Show HN or a short demo with the source or a clear privacy explanation; answer every technical question. |
| Productivity for one job (recruiters, sellers, researchers) | Communities, newsletters and accounts for that profession on Reddit, X or LinkedIn. | A short clip of the extension saving a step in their real workflow, posted where the rules allow it. |
| Companion to your web app or SaaS | Your existing users and visitors. | Offer it inside the product and on your site at the moment it helps; this is usually the cheapest source of installs. |
| Consumer or shopping | Search, short video and comparison articles. | A landing page that answers the search, plus clear disclosure of any affiliate model. |
| AI sidebar or writing assistant | A crowded category where generic claims are ignored. | Pick one narrow task and audience, and show a before-and-after for that task only. |
A 30-day launch plan
- Days 1–3: write one sentence naming who the extension is for and the moment they need it. Rewrite the summary, first screenshot and description from that sentence.
- Days 4–7: add a welcome page on install that gets the user to the first useful result, and an uninstall survey (see the template below). Verify your publisher identity.
- Days 8–14: contact 20 people who have the problem, one at a time, in the place they already discuss it. Ask them to try one task and tell you where they got stuck.
- Days 15–21: fix the step where most people stopped, then ask the users who succeeded for an honest review.
- Days 22–30: make one public launch in the channel that produced the best conversations, such as a Show HN or a demo post, and compare impressions, installs and uninstalls with the first two weeks.
Copy the review prompt and uninstall survey
Ask after a success moment, not on install, and make the request the same for everyone. Because the rating will now favor recent reviews, a steady trickle of honest reviews matters more than a burst on launch day.
The uninstall survey tells you whether people leave because the listing set the wrong expectation or because the product failed. Chrome opens the page you set with chrome.runtime.setUninstallURL; the URL must use http or https and be at most 1,023 characters. Do not put personal data in that URL. The onInstalled event, with the reason install, is where to open your welcome page.
setUninstallURL sets a page visited on uninstallation (http or https, up to 1,023 characters); onInstalled fires with reasons including install and update.
Chrome for Developers: chrome.runtime APIMeasure the funnel every week
The Developer Dashboard reports impressions, daily installs and uninstalls by country, language and operating system, and weekly users. Weekly users counts installations, not active use, so measure activity in your own product if you need it. You can also opt in to Google Analytics for the store listing from the Store listing tab.
Illustrative example, not a benchmark: in one month a listing gets 4,000 impressions and 240 installs, an install rate of 6.0% (240 ÷ 4,000). In the same month 72 people uninstall, 30% of installs (72 ÷ 240), leaving 168 net new installations. If the uninstall survey says most left because the extension did not do what the listing promised, fix the listing before buying more traffic; if they left because it broke on a site, fix the product.
Installs and uninstalls by country, language and OS; impressions from search, browsing and direct visits; weekly users count installations rather than activity; optional Google Analytics opt-in.
Chrome for Developers: Analytics for your store listingWhere Soloop fits
Soloop does not edit Chrome Web Store listings, read your store analytics or publish extensions. It helps with the outreach around them. According to the Soloop manual, it can research where a group of people discusses a problem and return sources, post on X after you connect it with OAuth, prepare Reddit posts for you to publish yourself, send cold email through Gmail (beta) and prepare Google Search Ads for your review and payment. Actions wait for your approval by default.
A bounded first request: My Chrome extension [store URL] helps [audience] [do one task]. Find where [audience] discusses [problem], with sources, suggest one channel for a 30-day test and draft five short messages asking people to try one task and tell me where they get stuck. Do not post or send anything.
Sources, limitations and refresh
Google's July 1 and August 20, 2026 announcements, the Chrome Web Store discovery, listing, policy and analytics pages and the chrome.runtime reference were read on October 29, 2026. Google has not published the Featured badge end date or how recent reviews are weighted, and some documentation pages still describe the older badge process. The channel table, launch plan, templates and removal checklist are editorial guidance; the funnel example is illustrative. Nothing here guarantees ranking, installs or approval.
This guide will be reviewed by January 29, 2027, or sooner if Google announces the badge end date or rating details.
The Soloop manual describes research with sources, X publishing with OAuth, Reddit preparation with manual publication, beta cold email through Gmail and Google Search Ads after review and payment; approval comes first by default. It does not manage Chrome Web Store listings.
Soloop product manual