Product Hunt Relaunch Rules: When You Can Go Again

Yes, you can launch the same product on Product Hunt more than once. The default rule is a gap of at least six months between posts for the same product or from the same company, and the new launch also needs a significant update behind it. If you want to go again sooner, Product Hunt detects the relaunch, asks you to describe what changed, and its team reviews the request. A new mobile app or a complete redesign with new functionality is the kind of change it has in mind. A new UI or a pricing change is not. Even an approved relaunch is not guaranteed a spot on the homepage, so the real question is less "am I allowed?" and more "is this change big enough that people will care twice?"

That is the policy as Product Hunt states it today, in its help article Can I relaunch my product?, last updated in July 2026. Plenty of what circulates about relaunching is older than that, or is a founder's guess repeated until it sounds official. Below are the rules in plain terms, the grey areas they leave open, and a checklist you can run before you commit to a second launch day.

Can you launch the same product twice?

You can. Product Hunt's own launch guide answers the question directly: "You can launch as often as you have new significant product iterations available." The first launch is not a one-time ticket, and treating it like one is why so many makers rush a half-ready product out the door or sit on a big release for fear of wasting their only shot.

What Product Hunt limits is repetition, not ambition. Its post-launch guide on launching again explains the history: the six-month prompt exists because the community felt the homepage was getting repetitive as the same makers launched again and again in quick succession. That framing is useful, because it tells you what the moderators are protecting. They are not guarding a lifetime quota. They are guarding the homepage from products that show up with nothing new to say.

It also helps to know how Product Hunt judges fit in the first place. Its page on how Product Hunt works lists "The product is new" as a guideline, then immediately adds the alternative: "Or the product has substantive updates since its last launch." The examples it gives are a new app, a major feature launch, or an extension. A relaunch is simply a launch that passes the second test instead of the first.

How long between launches?

Here is the timeline, stated as simply as the sources allow:

Time since your last launch	What the rules say	What happens when you submit
Under six months	Allowed only with a significant update, by request	The system detects the relaunch and prompts you to describe what changed. The team reviews it and can approve it.
Six months or more	Allowed, and a significant update is still expected	You submit like any launch. Featuring is still an editorial decision.

Two details in that table get lost in most retellings.

The first is that six months is not a free pass. The help article is clear that makers need to wait at least six months "and there also needs to be a significant update to the product." Waiting out the clock with the same product and a fresh gallery is not what the rule describes.

The second is that the gap applies to more than one listing. It covers posts "for the same product or from the same company", and the help article adds that products sharing the same root domain must keep the same six-month gap. A second product that lives on your main domain counts against the clock too.

How often should you actually go, as opposed to how often you are allowed? In Product Hunt's own forum, a member of the Product Hunt team suggested that a big update is worth launching whenever it lands, while smaller features are better bundled "in a 'suite of updates'", which he said typically comes around three to six month markers. That is advice, not policy, but it matches the logic of the rules: batch small changes until they add up to a story.

What counts as a "major update"?

This is the part that decides your request, and it is where makers most often talk themselves into a relaunch that will not land. Product Hunt gives a small number of anchors. It names a new mobile app and a complete product redesign with new functionality as significant. It names new UIs and pricing plan changes as not significant. Its fit guidelines add a new app, a major feature launch and an extension as the kind of update the community finds interesting.

Reading those anchors together, the line is about what a user can now do, not how much work you did. Here is how common changes fall against them:

Change	Likely to count?	Why
A new mobile app for a web product	Yes	Named as significant by Product Hunt
A complete redesign that ships new functionality	Yes	Named as significant, and the functionality is the operative word
A major new feature that serves a new use case	Usually	Fits "major feature launch" in the fit guidelines
A browser extension or new platform for the same product	Usually	"Extension" is one of Product Hunt's own examples
A new UI or visual redesign on its own	No	Named as not significant
New pricing, a new free tier, a plan change	No	Pricing plan changes are named as not significant
A rewrite on a new stack with the same features	No	Nothing changes for the user
A batch of small improvements and fixes	Rarely, alone	Better bundled into a larger release first

A quick test that works: write one sentence describing what a person can do with the new version that they could not do with the old one. If the sentence needs the words "faster", "cleaner" or "better", you probably have an improvement, not a relaunch. If it needs a new noun, such as a platform, a workflow or an audience, you may have one.

Should you relaunch under a new name?

Only if the name changed for real reasons. A new name does not reset the clock, and there is no rule suggesting it would. The gap applies to posts "for the same product or from the same company", and to anything sharing a root domain. A product that is renamed but still lives at the same domain, built by the same team, is the same product for the purposes of the rule.

This matters because a common workaround in circulation is to disguise a relaunch: a new name, a tracking parameter on the URL, a lightly different landing page. Product Hunt's help center does not publish a rule on URL variants, but it does publish the intent of the six-month rule, and a submission engineered to avoid the relaunch prompt is working against that intent in the open. It is not worth putting your account in front of a moderator that way when the honest route exists: submit, answer the prompt, explain the change.

A genuine rebrand is different. If you repositioned for a new audience, rebuilt the product around a different job, and renamed it to match, the rename is part of a significant update rather than a way around one. Say so plainly in the relaunch request and in your first comment. The name is the least interesting part of that story.

How is a relaunch day different from a first launch?

The mechanics are the same. You still schedule for 12:01am Pacific, you still cannot ask people directly to upvote (Product Hunt's launch guide calls that "the only real rule" about sharing your link), and your launch still needs to be posted from a personal account rather than a company account. What changes is the story and the audience.

You are explaining a difference, not introducing a product. Some visitors will remember the first version. Your tagline, gallery and first comment should lead with what is new, and the first comment should say outright that this is a relaunch and why. Product Hunt's preparation guide reports that "70% of products who achieved Product of the Day, Week, or Month had a first comment by the maker", and on a relaunch that comment is where the case gets made.

Your history is visible. Product Hunt's product pages roll up launches, reviews, team members and awards in one location. People can see the earlier launch, which is fine. It means old assets reused on the new launch look worse than they would on a first one. Record a new demo, and make the screenshots show the thing that changed.

Your warm audience is bigger. You now have users from the first launch, and the people who left a comment or a review the first time are the most natural people to tell. Tell them what changed and when it goes live, and let them decide whether to show up.

The day plan stays the same. If you want the hour-by-hour version, the Product Hunt launch day timeline applies to a relaunch as well as a first launch, and choosing the day itself is the same trade between reach and ranking.

What if the first launch flopped?

Then the rules have not changed for you. They count posts, not outcomes. Product Hunt does not publish an exception for a launch that went quietly, so a flat first day starts the same six-month clock as a Product of the Day.

That is less harsh than it sounds, because a flop is rarely a Product Hunt problem. A launch that got a handful of upvotes and no comments usually means one of three things: nobody knew it was happening, the page did not make the product clear in a few seconds, or the product was not ready for strangers. None of those is fixed by posting again. A second launch with the same page, the same audience and the same onboarding tends to reproduce the first result, and it does so while spending the goodwill of the people who showed up twice.

Use the gap. Put the product in front of people who can try it without a launch day attached, watch where they get stuck, and fix that. If the honest conclusion is that Product Hunt is the wrong room for this product, that is a legitimate answer too, and it is worth reading whether Product Hunt is worth it for indie apps before planning round two. When a relaunch does come, it should come with a significant update and a warm audience, not a second attempt at the same day.

Relaunch eligibility checklist

Run through this before you submit. Every box in the first two groups should be ticked. The third group decides whether it is worth doing, not whether it is allowed.

The interval

• It has been at least six months since the last post for this product, or you are ready to submit a relaunch request explaining the change
• No other product from your company, or on the same root domain, has launched in that window
• No second launch from your company is scheduled for the same day (Product Hunt may move one of them to a later date)

The change

• You can describe, in one sentence, something users can do now that they could not before
• The change is more than a new UI, a visual refresh or a pricing change
• It resembles one of Product Hunt's examples: a new app, a redesign with new functionality, a major feature, an extension
• If it is a set of smaller improvements, they are bundled into one release with one name

The listing

• The tagline leads with what is new, not with what the product was
• The gallery and demo video are new and show the change
• Your first comment is drafted, says this is a relaunch, and explains why
• The launch is posted from a personal account, not a company account
• You have told the people who used the first version, without asking anyone to upvote
• The product is usable today, with a free path someone can try without a sales call

If the change column is weak, stop there. An approved relaunch still does not guarantee featuring, and a listing that cannot explain its own update is the kind of launch the rule was written to discourage. If you are unsure whether your update qualifies, Product Hunt's help article gives a contact address for asking before you submit, which beats guessing.

Frequently asked questions

How often can you relaunch on Product Hunt?

As often as you have significant product iterations, with a default gap of at least six months between posts for the same product or from the same company. You can go sooner by submitting a relaunch request that describes what changed, which the Product Hunt team reviews. Products that share a root domain are held to the same six-month gap.

Does relaunching hurt your ranking?

Product Hunt does not publish any rule that penalizes a relaunch in the daily ranking. Each launch competes on its own day. The practical risks are different: an approved relaunch is not guaranteed to be featured on the homepage, and a relaunch with little new to show tends to get a thinner response than the first launch, because the people who already saw it have no reason to come back.

Can a rebrand relaunch?

A rebrand on its own does not reset the six-month clock. The gap applies to the same product, the same company and the same root domain, so a new name on the same product still counts. A rebrand that comes with a significant update, such as a new platform or a product rebuilt around a different use case, can qualify, and the change is what you should explain in the request.

Should a failed launch be relaunched or forgotten?

Neither, at first. A quiet launch still counts as a launch, so the same rules apply. Spend the gap fixing the reason it went quiet, usually the audience, the page or the onboarding, and relaunch only when you have a significant update and people who already want to see it. If the product still does not fit Product Hunt's audience after that, spend the effort on channels that do fit.

---

Six months is a long time for a product to sit between launch days, and the traffic from any single day fades within a week. A listing that keeps working in between is the part of the plan you control. Submit your app to TryMy free: a human reviews it before it goes live, it sits in a showcase of apps people can actually try, and it keeps pointing at your product while you build the update worth a second launch. If you are still deciding where else to post in the meantime, where to post your app in 2026 covers the channels that do not come with a six-month clock.