Chrome Web Store changes in 2026: publishing limits, recent-review ratings and the end of the Featured badge

The Chrome Web Store changed more in the summer of 2026 than in the previous few years combined. Between July and August, Google tightened its data policies, capped how many extensions a publisher can list, announced that the public rating will lean on recent reviews, and scheduled the Featured badge for retirement. Each change is small on its own. Together they shift what a healthy listing looks like and which numbers you should be watching.

This post walks through what was announced, what it means in practice, and a short checklist for each change. Everything below is based on Google's own announcements, linked in each section.

Key takeaways

• New publishers start with two extension slots. Existing publishers keep a limit at least equal to what they have published, and can request more from the dashboard.
• The public rating will focus on more recent reviews, so a bad release can pull your stars down faster, and a fix can lift them faster too.
• The Featured badge is being sunset later in 2026. Self-nominations are closed. Ratings become the main quality signal.
• Since August 1, 2026, data you collect must be strictly necessary for your extension's single purpose, and changes to data handling must be disclosed to users.

What changed, at a glance#

The August changes come from the Chrome Web Store team's post Faster reviews, new publication limits, badge updates, and more. The policy changes come from Chrome Web Store policy updates: enhancing user privacy and platform integrity.

Review times and pre-submission testing#

Google says the store saw a significant increase in extension submissions over the past months, and that the volume led to extended review times for many publishers. Two things were done about it.

First, the review process and its prioritization were reworked, which Google describes as bringing review times back to expected baselines. Second, the store now runs automated installation checks as soon as you upload a package, to confirm the extension installs on all supported Chrome platforms. The point is to fail fast: a broken package gets flagged before it enters the queue instead of after a reviewer picks it up.

What to do:

1. Treat an upload warning as a release blocker, not a formality. Fix it before submitting.
2. Keep recording when you submit and when each version goes live, so you know what "normal" looks like for your extension.
3. If you ship to other stores too, remember that each has its own queue. A fast Chrome approval does not mean Edge or Firefox users have the same build. Our guide on tracking one extension across Chrome, Edge and Firefox covers how to spot a store that is left behind.

New per-publisher extension limits#

This is the change that affects publishers with large catalogs, and new publishers most of all.

Each publisher account now has an individual extension limit. Google says the limit is based on several factors, such as the quality and usage of your published extensions. The default is two extension slots.

Existing extensions are protected. All published extensions stay published, and your new limit is at least the number of extensions you had published when the change landed. Google's own example: a publisher with six published extensions who would qualify for four under the new rules gets a limit of six.

If you need more, you can request a limit increase from the developer dashboard, and Google says most requests receive an immediate response.

Who this hurts, and who it does not#

• One product, one listing. Nothing changes. Two slots is enough for a main extension plus a beta or companion.
• Portfolio publishers. If you ship many small utilities, each new one now competes for a slot. The limit is tied to quality and usage, so a catalog of low-usage or poorly rated listings works against you.
• Template and white-label shops. Publishing near-identical extensions from one account was already a policy risk. It is now also a capacity problem.

What to do#

1. Count your published extensions and check the limit shown in your dashboard before you plan the next launch.
2. Retire listings that no longer earn their slot. An abandoned extension with a falling rating is a weak signal for your account.
3. Consider merging overlapping tools into one extension with a clear single purpose, which also helps with the data policy below.
4. Request an increase early, before a launch date depends on it.

Ratings now favor recent reviews#

Google says the extension rating will focus on more recent reviews to better reflect current user sentiment, in line with other marketplaces such as Google Play. On Google Play, the public rating has been weighted towards more recent ratings for years, while the lifetime average is only visible to the developer in Play Console.

The Chrome Web Store post does not publish the exact weighting or a date for the switch, so do not assume a specific window. The direction is what matters.

What a recency-weighted rating means for you#

• Old goodwill counts for less. An extension with thousands of five-star reviews from 2022 can no longer coast on them. The stars reflect what users think of the current version.
• Bad releases hurt faster. A burst of one-star reviews after a broken update moves the visible rating more than it used to, because it is not diluted by years of history.
• Fixes pay off faster too. Ship a fix, and the recovery shows up sooner than a lifetime average would allow.
• Low-volume listings get noisier. If you receive a handful of reviews a month, each one carries more weight. Read the rating next to the number of recent reviews behind it.

This makes the week after a release more important than ever. The signals worth checking day by day are in our post on what to watch after an extension release, and the habits for reading stars and reviews properly are in reading review and rating trends.

A practical response plan#

1. Watch new reviews, not the average. The average is the last number to move. New low-star reviews are the early warning.
2. Reply to reviews that describe a real bug, and say when the fix ships. Users sometimes update their rating after a reply that solves their problem.
3. Release smaller changes more often so a regression affects fewer users before you can fix it. The same logic now applies to the browsers themselves, which ship a new version every two weeks and can break an extension without any release from you.
4. Keep your own history. The store only shows today's rating. If you want to know whether the switch to recent reviews moved your stars, you need your own record of the rating before and after.

In Extenify, the daily capture keeps that history for you, and the Rating dropped, Rating recovered, New review and Unusual burst of new reviews changes show up in the digest the day after they happen.

The Featured badge is being retired#

Google is sunsetting the Featured badge program later this year. The reasoning given is that improved baseline review standards across the store made the badge less meaningful, and Google is pointing developers to the refreshed rating system as the strongest signal of an extension's quality. Self-nominations closed on the day of the announcement, and all pending self-nominations were closed.

The separate Established publisher badge is not part of this announcement. According to the store's discovery documentation, it is granted automatically to publishers whose identity is verified and who have a consistent positive track record with Google services and policy compliance.

What this means for your listing#

• If you have the Featured badge today, plan for it to disappear. Remove "Featured on the Chrome Web Store" claims from your website, screenshots and promotional images before the badge goes, so your marketing does not contradict the store.
• If you were waiting on a nomination, stop waiting. Put that effort into the rating instead.
• Make sure your publisher identity is verified, since that is one of the conditions for the Established publisher badge.

If you track listings in Extenify, expect a Lost featured placement line in the digest when the program ends. For this one event, it reflects the program closing, not a verdict on your extension. You will likely see the same line on competitors' listings around the same time.

The data policy changes that took effect August 1#

The July policy update is the one with enforcement attached. Extensions found out of compliance after August 1, 2026 may face enforcement action. Four policies changed:

A compliance checklist#

1. List every piece of data your extension sends off the device, including analytics and error reporting. For each item, write one sentence explaining why your single purpose needs it. If you cannot, stop collecting it.
2. Check your disclosure. Data collection should be explained in a prominent notice inside the extension, not only in a privacy policy link.
3. Plan how you will announce data changes. If a future version collects something new, users need to be told. An in-extension notice on update is the simplest route.
4. Keep the privacy practices form in the dashboard in sync with what the code actually does, and update it in the same release as the code change.
5. Watch permission changes in your own releases. A version that requests more permissions is often also a version that handles more data. Extenify reports Requests more permissions as its own change, which makes a good trigger to re-read your disclosure.

Other updates worth knowing#

A few smaller announcements from Google I/O 2026, covered in What's new in web extensions: I/O 2026 recap, round out the year:

• Team roles in the dashboard. Publisher accounts now support Admin, Item Manager and Viewer roles, and extra team members can be invited at no cost without their own developer registration. Give people who only need numbers the Viewer role.
• The browser namespace. Chrome now supports the browser global namespace used by other browsers, which makes a shared codebase across Chrome, Edge and Firefox simpler.
• More developers. Google reports that monthly developer registrations more than doubled over the past year, that 17% of extensions created for the store in that time use AI, and that registration is opening to more than 120 additional countries. More publishers means more competition in every category, which is part of why the store now leans so heavily on quality signals.

Frequently asked questions#

Will the new publishing limit remove any of my extensions?#

No. Google says all published extensions remain published, and your limit is at least the number you had published when the change took effect. The limit only matters when you want to publish something new.

How many extensions can a new Chrome Web Store publisher publish?#

The default is two extension slots. The limit is individual and based on factors such as the quality and usage of your extensions, and you can request an increase from the developer dashboard.

When will the rating start to favor recent reviews?#

Google announced the direction on August 20, 2026 but did not publish an exact date or weighting. The safest assumption is that your current reviews matter more than your historical ones from now on.

What replaces the Featured badge?#

Nothing directly. Google points to the refreshed rating system as the main quality signal. The Established publisher badge continues and is granted automatically to verified publishers with a good track record.

Does the Limited Use change apply to analytics?#

The policy covers any user data your extension collects. If you send usage analytics, you need to be able to justify it against your disclosed single purpose and disclose it prominently. When in doubt, read the Limited Use policy and collect less.

Summary#

The 2026 Chrome Web Store is stricter about who publishes, what data they collect and which signals count. Slots are tied to quality, the rating reflects recent users rather than old ones, and the Featured badge is going away. The common thread is that the current state of your listing matters more than its history. Keep a record of your own rating and reviews, watch every release closely, and set up store change alerts so a slipping rating reaches you before it reaches the store's ranking.

Image credits#

• Cover photo: Developer working on code in a modern office by Zayed Hossain on Pexels, Pexels License.