Originally published on ExtensionBooster.
Bad reviews on a Chrome extension rarely come out of nowhere, and they are rarely random. The ExtensionBooster team hand-labeled a sample of real one-star Chrome Web Store reviews to find out what actually pushes users to the review box, and the pattern is clear enough to turn into a release checklist. Here is what the data says and what you can change in your next version.
How the data was collected
On October 21, 2026, the team pulled the newest public English reviews (up to ten per listing) from 805 Chrome Web Store listings:
- 7,355 reviews from 798 listings
- 1,433 one-star reviews from 515 listings
- 400 one-star reviews, randomly sampled from 255 listings, each tagged with its main complaint
The listings came from category pages, searches and related-extension links, so they lean toward popular, well-ranked extensions. With 400 samples, expect a margin of error of roughly 4 to 5 points on each percentage.
What one-star reviews are actually about
| Main reason | Share of sample |
|---|---|
| It doesn't work (bugs, crashes, unsupported sites or browsers, lost data) | 43% |
| Trust and intrusions (ads, redirects, injected content, new permissions, suspected malware) | 13.8% |
| Pricing, paywalls or billing | 11.5% |
| Missing features, poor UX, misleading description | 9.5% |
| No reason given, or off-topic | 9% |
| It used to work until an update | 8.5% |
| Login or account friction | 4.3% |
| Support never answered | 0.5% |
Three things stand out for developers:
- Breakage dominates. Nearly half of all one-star reviews are some flavor of "it doesn't work."
- Change is risky. About 1 in 8 bad reviews reacted to something that changed. Across all one-star reviews, 11.4% used words like "update" or "used to", compared with 4.0% of five-star reviews.
- Money complaints are mostly about surprise. More than half of the pricing reviews were about unexpected charges or limits, not the price itself.
Notice that unanswered support barely registers (2 of 400). Users don't email you first and then review in anger; they skip straight to the review box because it is the channel they can find.
The shape of a bad review
Length tells you something too. The median one-star review is 14 words, while the median five-star review is just 10 words (and a quarter of five-star reviews are three words or fewer). The most detailed reviews are the middle ratings: two-star and three-star reviews hit medians of about 25 words and often read like bug reports from people who still want the extension to work.
Meanwhile, developers replied to only 15.5% of one-star reviews (222 of 1,433). That is a lot of unanswered public criticism sitting on listing pages.
A prevention checklist mapped to each cause
- Silent bugs: put a "Report a problem" link in the popup and options page so the review box isn't the only outlet.
- Other Chromium browsers: test in Brave and Edge before each release, or say clearly which browsers you support.
- Breaking sites or other extensions: scope content scripts to only the sites you need, and test alongside popular extensions.
- Risky updates: use percentage rollouts and keep a rollback plan. Google's update docs describe rollouts for published items with more than 10,000 seven-day active users.
- New permissions: Chrome disables an extension when an update adds a permission with a new warning, until the user accepts it. Ask for new access at runtime via optional permissions and explain why.
- Paywalls: state pricing in the first lines of the description, and grandfather existing users when adding limits.
- Billing: make cancelling one click, and answer billing emails the same day.
- Ads and affiliate links: don't introduce them into an extension that never had them. If you must, follow program policies and announce it ahead of time.
- Account walls: let people try the core feature before signing up, and test login in other browsers.
For the optional permissions point, the runtime request uses the chrome.permissions API and looks roughly like this:
// manifest.json: "optional_permissions": ["tabs"] document.getElementById('enable').addEventListener('click', async () => { const granted = await chrome.permissions.request({ permissions: ['tabs'] }); if (!granted) showMessage('Tab features stay off until you allow access.'); }); When a one-star review lands anyway
- Reply within a day or two. Ratings can be changed at any time, and future visitors read your reply.
- Take it off the store. Reviewers aren't notified of replies and you can't message them, so include an email or feedback link.
- Fix it and say so, naming the version that resolved the issue.
- Talk to a few reviewers. A short call with a frustrated user often teaches more than a pile of reviews.
- Balance the record. Happy users rarely review on their own, so ask them at a good moment.
You can't get an honest negative review removed just for being negative; only reviews that break Google's terms come down. Vague ones still deserve a short, calm reply asking what went wrong.
Key takeaways
- 43% of sampled one-star reviews say the extension simply doesn't work.
- Roughly 1 in 8 bad reviews is a reaction to a change, so updates, permissions and pricing shifts need care.
- Users go straight to the review box; an in-extension feedback link gives them a better option.
- Only 15.5% of one-star reviews got a developer reply, which is an easy gap to close.
The full breakdown, with examples for each category, is in the original study of why people leave bad reviews on Chrome extensions. For more on ratings and growth, see the ExtensionBooster guides for Chrome extension developers.
Which of these causes has cost your extension the most stars, and what did you change afterward?
