Extension directories link people to your Chrome Web Store page, so the store listing comes first. This guide covers what the store asks for, how review works, how to test before you launch, and where badges and launch posts fit.
Fill in the store listing completely
The one-line summary is capped at 132 characters. Three assets are mandatory: a 128x128 icon, a 440x280 small promo tile and at least one screenshot (up to five) at 1280x800 or 640x400. The 1400x560 marquee tile is optional, but without it an extension can’t appear in the marquee, and items without a small tile are shown after those that have one. A blank description, or a missing icon or screenshot, gets the item rejected.
- Keyword spam is a listed violation, including repeating the same keyword unnaturally more than 5 times.
- Unattributed or anonymous user testimonials are not allowed in the description.
- Metadata that misstates your store status or performance, such as “Editor’s Choice” or “Number One”, is not allowed.
Sources: Chrome Web Store: Supplying images · Chrome Web Store: Creating a great listing page · Chrome Web Store program policies
Review takes days, sometimes weeks
Google says most extensions finish review within a few days, though it can take up to a few weeks; after three weeks, contact developer support. New developers, new extensions, dangerous permissions and significant code changes can draw a closer look, and host patterns that match every site add time. Obfuscated code is disallowed; minified code is allowed but harder to review. On the Privacy practices tab, state one narrow purpose, justify every permission and declare any remote code, which Google says helps review go as quickly as possible.
- The activeTab permission shows no install warning, and optional permissions can be requested at runtime.
- Adding a permission that triggers a warning disables the extension for existing users until they accept it.
Sources: Chrome Web Store review process · Chrome Web Store: Fill out the privacy fields · Chrome Extensions: Permission warning guidelines
Test and time your launch
Set the item to Public, Unlisted or Private; all three follow the same policies and review. Unlisted creates no store listing, but anyone with the URL can install it. Private limits installs to trusted testers or Google Groups you manage. A BETA or TESTING copy can run beside production if its name ends in BETA or DEVELOPMENT BUILD and its description says it is for beta testing; otherwise both can be taken down. Deferred publishing then holds an approved version for up to 30 days, so you can pick your launch moment.
- A new publisher starts with a limit of two published extensions and can request an increase in the dashboard.
- The Test instructions tab takes credentials and steps if reviewers need a login to try a feature.
Sources: Chrome Web Store: Set up distribution · Chrome Web Store: Publish in the Chrome Web Store · Chrome Web Store: Provide test instructions
Ranking, collections and badges
Store ranking uses a heuristic built on ratings and usage, such as downloads against uninstalls over time. Collections are curated and Google says requests to be placed in one are not accepted. Nobody can pay to be featured on the home page, and no checklist guarantees it. Established Publisher is granted automatically once your identity is verified and you have a consistent record of following the policies, which takes new developers at least a few months. Featured is a manual review by the Chrome team; nomination is described as a trial in One Stop Support.
- To nominate, the extension must be public, have English support, have no active policy violations and work without extra credentials or payments.
- Google’s badges post puts the request in One Stop Support under My item, “I want to nominate my extension…”.
Sources: Chrome Web Store: Discovery · Chrome Web Store Help: Understand badges · Google blog: new Chrome Web Store badges
Reviews and support
Google says ratings and reviews can raise your ranking, so answer them. You can reply to any review and edit the reply later, but you can’t delete a review; report fake ones through the support form. Link people to the review page by adding /reviews to your item’s URL. The Spam and Abuse policy bans inflating ratings, reviews or install counts, including fraudulent or incentivized downloads and reviews, so never trade perks for reviews. The built-in Support hub collects questions, bug reports and feature requests, each with the extension version, browser and operating system.
Sources: Chrome Web Store: Manage user feedback · Chrome Web Store program policies
Launch posts: Show HN and Product Hunt
Show HN is for something people can run on their own computers, so an installable extension fits. It has to be non-trivial, something you made and will be around to discuss, easy to try without sign-ups, and not a landing page. Routine upgrades and small new features generally aren’t substantive enough. Neither community wants vote-begging: Show HN says not to ask friends to upvote, and Product Hunt’s launch guide says not to ask people directly to upvote but to invite them to visit and comment. Product Hunt also has a Chrome Extensions topic page.
Sources: Hacker News: Show HN guidelines · Product Hunt: launch guide · Product Hunt: Chrome Extensions topic
Facts checked Oct 9, 2026 against the sources linked in each section.