Originally published on ExtensionLaunch.
You posted on Product Hunt, shared it on Reddit, maybe sent a Show HN, and a week later the install chart is flat. You can relaunch a Chrome extension, and the second launch often goes better because you now have data, users and a clearer story. Here is how to find out why the first one stalled, what counts as news, and what each platform allows.
Step 1: Decide if a relaunch is the right fix
A relaunch fixes a reach or positioning problem. It does not fix an extension people try and abandon. Look at what your existing users do:
- They install and keep it. Weekly users hold steady after the spike, reviews are positive and people send unprompted feature requests. Not enough people saw it. Relaunch.
- They install and leave. Weekly users fall after each install wave, or reviews say it does not do what the listing promised. Fix onboarding or the product first, or a bigger audience only speeds up churn.
- Nobody installs. Usually a listing or positioning problem, which a relaunch can fix once the story changes.
Step 2: Read your store funnel
The Chrome Web Store Developer Dashboard splits analytics into Installs & Uninstalls, Impressions and Weekly Users. Page views can also be broken down by utm_source, utm_medium and utm_campaign, so tagged launch links show which channel sent visitors. Weekly Users also has an Enabled vs. Disabled chart.
| What you see | Likely meaning | Fix before relaunching |
|---|---|---|
| Few impressions in the store | The store rarely shows your item for searches | Name, summary, category, description |
| Link clicks, few listing page views | Visitors dropped between your post and the store | Landing page or post copy; link straight to the listing with UTM tags |
| Many page views, few installs | The listing does not convince | Icon, first screenshots, summary, permission warnings, ratings |
| Installs, then falling weekly users | People try it and leave | Onboarding and the core feature |
| Disabled users jump after an update | A permission increase switched users off | Ship without that permission |
Reread every comment from the first launch too. "How is this different from X?" tells you which part of the story was missing.
Step 3: Find real news
A relaunch needs something new to say. The platforms that allow a second post spell it out:
- Product Hunt requires "a significant update to the product." Its examples are a new mobile app or a complete redesign with new functionality. New UIs and pricing plan changes do not count.
- Hacker News Show HN guidelines say minor releases like "Foo 1.3.1 is out" are not enough, but "A major overhaul is probably ok."
For an extension, these usually qualify:
- A new capability that changes what the extension is for, not a settings toggle.
- A new platform: Firefox, Edge, Safari or a mobile companion.
- A rebuild, such as a Manifest V3 version of an extension the store removed.
- A new audience with features built for them, such as teams instead of individuals.
Step 4: Relaunch the same listing
Don't publish a fresh item to get a clean slate. The Chrome Web Store spam and abuse policy bans submissions that provide duplicate experiences or functionality, and forbids attempts to manipulate the placement of extensions. A second listing also splits your users and reviews in two.
Ship it as an update to the existing item instead:
- Raise the version and refresh the listing.
- Submit for review with deferred publishing, so the approved version goes live on announcement day.
- For a big change, roll out to a percentage of users first.
Step 5: Know each platform's rules
| Channel | Post again? | Conditions |
|---|---|---|
| Product Hunt | Yes | Two months between posts for the same product or company, plus a significant update. Sooner needs a relaunch request. |
| Hacker News | Within limits | If a story has not had significant attention in the last year or so, a small number of reposts is ok. Do not delete and repost. |
| Depends | Each subreddit sets its own self-promotion rules. Read them first. | |
| Directories you joined | Update | Refresh description, screenshots and version instead of resubmitting. |
| Platforms you skipped | Yes | For you it is a first launch there. |
A four-week schedule
- Weeks 4 to 3: fix what the funnel showed. Ask a few first-launch users to try the new version.
- Week 2: write one sentence saying what is new and who it is for. Rework the summary, screenshots and demo video around it.
- Week 1: submit the update with deferred publishing, create UTM links for every channel, and draft each post separately because each community expects a different tone.
- Relaunch day: publish the approved version, then post, and stay in the comments all day.
- The week after: compare page views, installs and weekly users by channel with the first launch. Keep the channels whose users stayed, not the ones with the most clicks.
Tell existing users too, but skip system notifications: the spam policy prohibits notifications used for spam, ads or promotions. Use a "What's new" note in your popup, listing release notes and email. Never offer anything in return for ratings or reviews.
Key takeaways
- Diagnose before relaunching: each weak funnel step points to a different fix.
- Relaunch the same listing. A duplicate item breaks the Repetitive Content rule and splits your reviews.
- Product Hunt wants two months and a significant update; Hacker News allows a repost if the story had no significant attention in the last year or so.
- Offer news, not a repeat: a new capability, platform, rebuild or audience.
- Judge channels by users who stay, not by clicks.
The full guide has the complete checklist, FAQ and sources: how to relaunch a Chrome extension after a quiet launch. If your extension needs a place to keep sending visitors after launch day, the ExtensionLaunch extension directory is one option.
Which channel sent your first launch the users who actually stayed, and what would you change if you relaunched tomorrow?
Top comments (0)