How to launch on Product Hunt

A Product Hunt launch is a one-day window that you prepare for over weeks, and Product Hunt's own launch guide is the most reliable checklist for it, because it is the platform describing its own rules. Its explanation of how launches work puts the timing plainly: "The best launches start weeks before launch day."

The 37signals book Getting Real made the same point years earlier in its chapter on the Hollywood launch, which warns that "if you launch your app without any pre-hype, people aren’t going to know about it."

Everything below comes from those two kinds of source: the platform's help center for the rules, and founders who have written about what a launch can and cannot do. Where a number appears, it is Product Hunt's own. Vendor claims about how many upvotes come from your own audience are left out, because nobody outside Product Hunt can see the data behind them.

What should you decide before you pick a launch date?

Decide what the launch is for before you decide when it happens. Product Hunt's article on goals and launch dates asks you to pick one or two measurable goals, such as a number of signups, feedback responses or website visits, and adds that "Product of the Day is a great goal, but it's far from the only one."

A goal changes how you spend the day. If the goal is 50 feedback conversations, you spend the day replying and asking follow-up questions. If the goal is waitlist signups, the link in your maker comment and the page behind it matter more than your rank. Write the number down where your team can see it, so that at 6 PM nobody is refreshing the leaderboard instead of answering a comment.

Pick the date last. The same guide says no weekday guarantees a top spot and recommends the day you are most prepared for, when you and your team can be present for the key hours and your audience is online. Weekdays bring more traffic and more competition; weekends are quieter. The launch FAQ answers the best-day question in one line: "The day you're most prepared for and can be fully present."

What do the Product Hunt rules say about timing and scheduling?

Product Hunt's timing rules are short, and every one of them affects your plan. The table collects the ones that matter, each from Product Hunt's own help center.

Rule	What Product Hunt says	Source
Go-live time	12:01 AM Pacific Time on the scheduled date, until midnight Pacific	Goals and launch date
Scheduling window	From tomorrow up to 30 days ahead	Goals and launch date
Hunting limit	Each person can hunt up to 2 launches per day	Goals and launch date
Accounts	Personal accounts only; company and brand accounts cannot submit or comment	How Product Hunt works
Relaunch gap	Inside two months of your last launch, you need a relaunch request	Relaunch your product
Cost	Launching is free	How Product Hunt works

The go-live time is the one founders outside California underestimate. From Lisbon or London, 12:01 AM Pacific is about 8 AM on your launch day, and the Pacific day does not end until about 8 AM the next morning, so the last third of the launch runs through your night. Split the day into shifts before the week starts, and make sure every co-maker has a personal account set up well in advance, because Product Hunt wants them on the page with their own profiles.

What does a four-week Product Hunt prep timeline look like?

A four-week runway fits inside Product Hunt's 30-day scheduling window and gives you time to show up in the community before you ask anything of it. The weeks below are a working plan, not Product Hunt policy; the rules each week follows are Product Hunt's.

When	What to do	Why
4 weeks out	Set your one or two goals. Complete your personal profile. Start commenting on other launches and Forum threads.	Product Hunt's guide says to engage with the community weeks before launch and to complete your profile before launch day.
3 weeks out	Write the name, tagline and description. Capture the gallery images and a short demo video.	These are required fields, and the gallery should show the product in use.
2 weeks out	Draft the maker comment. Add co-makers. Tell your users, subscribers and team the date.	Co-makers need accounts in time to reply to comments; a heads-up beats a launch-day blast.
1 week out	Test signup in production from a clean browser. Prepare the emails and posts you will send on the day. Schedule the launch.	Product Hunt's pre-schedule checklist starts with a working product, including signup.
Launch day	Share the link where your audience already is. Reply to every comment. Run shifts.	The day runs a full 24 hours Pacific.
The week after	Keep replying, follow up with everyone who engaged, compare results with the goals.	People keep finding the launch for days.

The first row is the one most founders skip. Product Hunt's promotion guide lists inviting your community only on launch day as a common mistake, alongside leaving the website, emails and posts unprepared. Four weeks of comments on other people's launches is also how you learn what a good maker comment reads like.

What goes on the Product Hunt product page?

The product page is where a stranger decides in a few seconds whether your launch is worth a click, so Product Hunt's field limits force the same discipline a good landing page needs. According to Product Hunt's guide to building your product page, the name runs up to 40 characters, the tagline up to 60 characters and the description up to 500 characters. You choose up to 3 launch tags, upload at least one gallery image (the guide recommends three or more), and can add an optional video or clickable demo.

The tagline carries the most weight. Product Hunt's test is whether someone who reads only the name and tagline understands what the product does, and it gives "Meeting notes that write themselves" as an example that passes. A tagline that names only a category and a mood, with no hint of what the product does, fails that test. If you are struggling to get a tagline that specific, the method in AI for positioning and messaging forces variants that each lead with a different axis, so you can choose rather than polish one weak line.

Use the draft option until every required field is done. Product Hunt's page-building guide is blunt: "Schedule only when everything is ready." Its pre-schedule checklist asks that the product works in production, including signup, that the name and tagline are clear on their own, that the gallery shows the product in use, that co-makers are added, that the maker comment is written and that any promo code works.

How should you write the maker comment?

The maker comment is the first thing in the discussion and the only part of the page that sounds like a person, so write it as a note from you, not as a press release. Product Hunt gives it up to 5,000 characters and pins it at the top of the discussion when you launch. Its suggested contents are who you are, why you built it, what it does in two or three points, who it is for, what makes it different, a specific question for feedback and any offer.

The specific question is what turns a visit into a comment. Asking what people think gets politeness. Asking freelancers which part of a client proposal they rewrite most often after a first draft gets answers you can use, and those answers are the feedback the launch was supposed to produce. Product Hunt's product page guide sets the tone in one line: "Ask for feedback, never for upvotes."

How should you treat comments on launch day?

Comments are the work of launch day, and Product Hunt ranks a launch on more than upvotes. Its guide to what to do during and after your launch tells makers to "Answer every comment you can, as close to real time as possible", and explains that rankings shift through the day based on upvotes, comments, time since launch and other signals. Product Hunt does not publish the formula; its explanation of how launches work says "We don't share the exact formula, because that would make it easier to game."

Treat every comment as a short customer interview. Thank the person, answer the question they asked, and when the comment hints at a use case you had not planned for, ask one follow-up. Product Hunt suggests replying with a short demo video or a live link rather than a long paragraph when someone asks how something works. Hard questions deserve a straight answer in public; the people reading the thread see how you handle criticism, and that is part of what they are deciding about.

Keep a running document of what commenters say, sorted into feature requests, confusion about what the product does, and objections. The confusion pile is the most valuable, because it tells you what your tagline and first screen failed to explain. Collecting feedback on an MVP covers how to turn that pile into decisions after the day ends.

What should you never do on Product Hunt?

The rule that gets launches removed is asking for votes, and Product Hunt states it without qualification. Its promotion guide says "Never ask for upvotes." and warns that "Bought or low-quality engagement is easy for us to spot, and it can get your launch removed and your account banned." The same guide rules out running contests that require or reward upvotes, paying for upvotes or comments, mass DMs, scraped email lists, copy-paste messages, and fake or extra accounts. If you are unsure whether something crosses the line, it suggests emailing Product Hunt before you do it.

Spare accounts also do less than founders expect. The launch FAQ says upvotes from established, active community members earn a launch far more points than upvotes from brand-new or low-quality accounts, so asking friends to sign up on the day mostly adds noise. What Product Hunt wants you to ask for instead is in one line of the promotion guide: "Ask for feedback, comments, and help spreading the word instead."

Where you share the link matters as much as how. Post it to your email list, your own social accounts and communities where you already take part. The promotion guide is direct on this: "Communities you've never posted in before are not the place to drop a link."

Two myths waste the most preparation time. The first is that you need a famous hunter; the launch FAQ says "You can, and should, hunt your own product." The second is that the launch only counts if you finish first. The same FAQ answers that one too: "Feedback, users, and connections count too."

What can a Product Hunt launch actually do for a new product?

A launch gets a new product in front of early adopters for one day and gives you a permanent product page afterwards; it does not create retention, and it rarely creates a business on its own. Paul Graham's essay Do Things That Don't Scale calls the Big Launch "one sort of initial tactic that usually doesn't work" and writes: "All you need from a launch is some initial core of users." That is a useful frame for a Product Hunt day. If the launch hands you a few dozen people who care and a few hundred comments' worth of language about the problem, it did its job.

The counterargument is real. A launch day can produce a large spike, and for some products the spike is the start of everything. The case against relying on it is what happens next: visits that arrive in one day tend to leave in one day, and an upvote costs the voter nothing, so it is weak evidence of demand. Read the result against your pre-launch goals, not against the leaderboard. Signups that never activate are a message or product problem, which is why the activation metric guide belongs in your post-launch week.

The repeatable part is that Product Hunt expects you to come back. Its relaunch guide allows a new launch after two months, or sooner with a relaunch request for a major update such as a new feature set, a new platform or a significant redesign, and it notes "Loom is a good example: they've launched 15 times." That turns one launch into a habit: ship a real change, launch it, collect feedback, fix what it shows.

What should you do in the week after launch?

The week after launch decides whether the day was worth it, because the people who engaged are still warm and most of them will not come back on their own. Product Hunt's after-launch guidance asks you to keep replying, to "Reach back out to the users, prospects, and partners who engaged with you", and to "Compare your results with the goals you set before launch."

Write the follow-up as a person, not a newsletter. A short note that names what the reader said in their comment and asks one question will get more replies than a thank-you blast. Then do the manual work Paul Graham describes: talk to the ones who replied, find out why they signed up, and look for the pattern in who stayed. Getting your first 100 users is the plan for that stretch, one channel at a time, after the spike has passed.

If you are building the product and the launch plan at the same time, the From Idea to Launch with AI bootcamp is built for that stretch. It runs 1 week with 2 live sessions and 8 self-paced microlessons, and its curriculum covers launch narrative and positioning, a landing page outline, distribution options for first users without an audience, and traction metrics for after the first launch.

See the From Idea to Launch with AI bootcamp

Before you schedule anything, open your current product page draft and read only the name and tagline to someone who has never seen the product. If they cannot tell you what it does in one sentence, that is the first thing to fix, and it costs nothing to fix four weeks out.