Product Hunt and launch directories in 2026: a practical guide

Product Hunt is still the most visible launch venue for software, but it only pays off if you arrive with a usable product, a finished listing and someone answering comments for the full 24-hour day, which starts at 12:01 am Pacific Time. The rule that sinks most launches is asking for upvotes: it is not allowed. Around it sit a dozen useful directories (Show HN, BetaList, Peerlist, DevHunt, AlternativeTo and, for AI products, the MCP server registries) that you should pick by product type rather than joining them all.

What a launch directory is and what to expect from it

A launch directory is a site where a community discovers, votes on and discusses new products. They come in two kinds: event directories (Product Hunt, Peerlist, Microlaunch, Show HN), where you compete for a day, a week or a month before your listing moves to the archive; and catalogue directories (AlternativeTo, SaaSHub, G2, the MCP registries), where your listing lives permanently and people arrive by searching a category or an alternative to a tool they already know.

That split decides how you work each one. Event directories need preparation and a full day of attention; catalogue directories need a complete listing that you keep current. None of them replaces an audience of your own: a launch works best when you already have a waitlist, some social presence and a site that explains clearly what you do (covered step by step in our guide to launching a web project).

Platform rules change without notice. Everything below reflects each platform's own documentation as of October 2026, linked so you can re-check it on the day you launch.

Product Hunt rules as of October 2026

When the day starts and who can launch

• Timing. The Product Hunt launch guide says 12:01 am Pacific Time is the best time for makers who plan ahead, because it gives you the whole day. That is 8:01 am in London for most of the year and late evening of the previous day in Asia-Pacific: plan your response shifts around it.
• Anyone can post. A free account is enough; whoever submits is the hunter. As how Product Hunt works explains, most products are self-hunted, and the guide says there is no discernible advantage to using a third-party hunter.
• Personal accounts only. Company accounts are prohibited. Teammates are added as makers by username, and the guide asks for those accounts to be created well before launch day.
• Drafts and scheduling. The old Launch Now button is gone: you can create an unlisted draft to review with your team, or schedule it, according to the help centre, up to a month ahead per the preparation guide.

What is not allowed

There is one clear rule: you cannot ask people directly to upvote your product. The guide's own wording is to ask them to visit and comment instead. The page on sharing your launch adds that they may ask you to remove posts that request upvotes, that contests or giveaways rewarding upvotes are banned (including ones run by your hunter or anyone you pay), and that if you keep going they may unfeature your product. They also warn against sending hundreds of people the same message or emailing scraped addresses.

Two myths their launch day questions page puts to rest: linking directly to your launch carries no penalty (they encourage it), and a maker's upvote does not count more than anyone else's: all upvotes are equal.

How ranking works and what is not featured

The homepage leaderboard shifts through the day based on upvotes, comments, time since submission and other factors that Product Hunt keeps private so the system is harder to game. One detail is easy to miss: not everything that is posted gets featured. The featuring guidelines look for products that are useful, novel, well crafted and creative, and explicitly exclude, among others, waitlisted products without immediate access, directories and lists, templates, courses, services and stores. If your product is still behind a waitlist, Product Hunt is not your venue yet.

To relaunch, the relaunch policy requires at least six months between posts for the same product or root domain and a significant update (a new mobile app, a full redesign with new functionality); UI tweaks or pricing changes do not qualify.

Preparing the day: listing, first comment and shifts

The preparation guide sets the minimum: at least two gallery images (1270 × 760 recommended), a square thumbnail (240 × 240 recommended, under 3 MB, GIFs allowed), a tagline of up to 60 characters without hype, an optional video as a non-private YouTube link and, if you like, a promo code with a description and an expiry date.

On the maker's first comment, Product Hunt publishes its own figure: 70% of products that reached Product of the Day, Week or Month included one. On video: about 53% of Product of the Day winners since 2021 had one. These are correlations the platform reports, not guarantees, but they show what the community expects to see.

What goes into each piece

• Gallery: the first image shows the outcome, not the interface. Then two or three screenshots of the key moments, each with one line saying what is happening.
• First comment: who you are, why you built it, who it is for, what it does today (no roadmap promises), the price or launch offer, and one specific question that invites feedback. The guide recommends a humble, helpful tone.
• Video: 30 to 90 seconds of the product in use. If you cannot make a good one, skip it rather than ship something generic.
• Offer: simple and dated (a first-year discount, an extra month). Product Hunt asks for an expiry date on the code.
• Destination: the link should land on a page that works on mobile, offers signup or a trial straight away, and carries UTM parameters so you can measure what arrives.

Who replies, and when

The day lasts 24 hours and comments arrive from every time zone. Split it into shifts: one person covers the first hours, another the US working day, and someone either covers the night or posts in the thread when replies will resume. Answer every comment with something specific, never a bare thank-you, and log every request and criticism: they are the most valuable output of the day. Off the platform, share the launch asking for feedback rather than votes, and keep an eye on the launch day dashboard mentioned on the launch day duties page.

Show HN: the official rules and when it is worth it

Show HN is the Hacker News section for showing something you have made. The official guidelines are short and strict: it must be something people can try, that you worked on personally and that you are around to discuss. They ask you to make it easy to try, ideally without signups or emails; they rule out landing pages and fundraisers; version bumps are generally not enough; and if it is not ready for users, do not post it. The title starts with Show HN.

The general Hacker News guidelines add the essentials: do not solicit upvotes, comments or submissions, and do not use the site primarily for promotion. Show HN suits technical tools, open source and products built on an unusual idea; it suits a waitlist landing page or a consumer app without a demo badly. If you post, stay in the thread and answer technical criticism with facts rather than defensiveness.

Other directories: which one fits which product

You do not need to be everywhere. Pick three or four based on product type and stage. The table summarises what we could verify in each site's documentation or pages on 6 October 2026; where no cost is given, it was not published on the page we checked.

AI directories deserve a separate word: there are dozens, many charge to list or to feature, and their terms change often. If your product uses AI, pick a few, read their terms on the day you submit and record the traffic each one sends. For a product that exposes its features to AI assistants, the channel that makes most sense today is the MCP server registries covered below.

Nofollow and dofollow links, handled with care

Many directories sell their link as dofollow and high authority (Uneed says so on its submission page; Peerlist says only the top five projects each week get a backlink). We found no reliable source measuring the SEO effect of any specific directory, so we do not promise one. What Google does say: links marked rel="nofollow", sponsored or ugc will generally not be followed, per its guide to outbound links, and its spam policies list buying links for ranking purposes and low-quality directory links as link spam. Choose directories for their audience, not their link.

G2 and Capterra: B2B review sites

If you sell to businesses, review catalogues carry weight in the buying decision. On G2 you can claim your product profile for free: you submit a form, their research team verifies the product in about 3 to 5 business days and, once you claim it, approval takes 1 to 3 business days. Capterra's vendor page currently points to G2's product listing flow. An empty profile does nothing for you: you need genuine customer reviews, and how to ask for them without breaking the rules is the subject of our article on reviews and social proof.

AI products: the official MCP Registry and server directories

If your product ships an MCP (Model Context Protocol) server so that AI assistants can use your features, start with the official MCP Registry. Its documentation still describes it as a preview, with possible breaking changes or data resets. The registry stores metadata only: your package has to be published first on npm, PyPI or another supported registry, or be a remote server.

1. Add verification to the package. For npm, an mcpName field in package.json holding the name it will have in the registry.
2. Publish the package (for example, npm publish --access public).
3. Install mcp-publisher (GitHub release binary or brew install mcp-publisher).
4. Run mcp-publisher init to generate server.json, then check name, description, repository, version and packages. The name in server.json must match mcpName.
5. Authenticate with mcp-publisher login github or, to use your own domain, via DNS (a TXT record) or HTTP (a file at /.well-known/mcp-registry-auth).
6. Publish with mcp-publisher publish and confirm it through the registry API.

The authentication method decides the name: with GitHub it is io.github.your-username/server; with a domain, the reverse-DNS form such as com.example/server. All of this comes from the registry's quickstart and authentication pages.

• Smithery: for a remote server you enter its public HTTPS URL in their publishing flow; it requires Streamable HTTP transport and, if auth is needed, OAuth that returns 401 to unauthenticated requests, per their docs.
• Glama: a server catalogue with an add-server button and license, quality and maintenance grades, visible in its directory.
• PulseMCP: as of October 2026 submissions are paused, and it recommends publishing to the official registry, from which it says it will pick servers up once it resumes.
• mcp.so: you submit the repository URL, with a free reviewed option and a one-off USD 39 option that publishes without review.

Launch day checklist

After the launch: the two weeks that matter

Product Hunt's guide to the days after launch says you can promote your launch page for two weeks, after which you should move to the permanent product page, which collects launches, reviews and awards. They recommend continuing to answer comments as you did on the day, following up with people who tried the product and sharing the feedback with your team.

For a view of everything that comes before and after the day itself, the product launch checklist covers site, measurement, legal and channels in the order that makes sense.

Submitting to twenty directories and losing count is one of the causes of the silent launch. LaunchSuite's directory tracking keeps the status of each submission so none slips away.