How to Launch on Hacker News (Show HN): The 2026 Guide

Why Hacker News matters for SaaS#

Hacker News is not a launch platform. It is a community of engineers, founders, and technical people who happen to be very good at finding interesting new tools. That distinction matters because everything about how you approach HN follows from it.

A front-page Show HN post can drive 5,000 to 30,000 visitors in 24 hours. But these are not passive readers scrolling through a feed. HN visitors click through, try the product, inspect your technical decisions, and form opinions fast. If your product is solid and your pitch is honest, these are some of the highest-quality users you will ever acquire.

The backlink alone makes it worth attempting. Hacker News has a domain rating of 91. A link from the front page passes serious authority to your domain. Combined with other launch channels like directories, communities, and launch platforms, a successful HN post can meaningfully accelerate your SEO from day one.

But here is the honest truth: HN is unpredictable. You can follow every piece of advice in this guide and still get zero traction. The algorithm is opaque, the community is fickle, and timing plays a bigger role than anyone wants to admit. This guide will maximize your odds, but it cannot guarantee outcomes.

Show HN rules and expectations#

Show HN is a specific post format on Hacker News. It is not a general submission. Before you write anything, you need to understand the rules because breaking them will get your post flagged or ignored.

The official rules#

• Your product must be something people can try. Show HN is for demos, live products, open-source projects, and side projects people can interact with. If you only have a landing page with an email capture, wait until the product is actually usable.
• Put "Show HN:" at the start of your title. This is not optional. Without the prefix, your post will not appear in the Show HN section and will not get the special treatment (like being immune to certain flagging rules).
• Include a URL. Link directly to your product, demo, or repository. Self-posts (text-only) are allowed but linking to the product is strongly preferred.
• You must be involved in the project. Show HN is for showing your own work, not someone else's product.

The unwritten rules#

The HN community has expectations that go beyond the official guidelines:

• No marketing speak. If your title includes words like "revolutionary," "game-changing," or "disrupting," you are already dead.
• Transparency is currency. Sharing your tech stack, architecture decisions, revenue numbers, or honest struggles earns respect.
• The audience is technical. Many readers are senior engineers, CTOs, and experienced founders. They will notice if you are hand-waving over technical details.
• Self-promotion is fine if the product is good. Unlike some communities, HN does not punish self-promotion. What it punishes is bad self-promotion -- products wrapped in hype with nothing behind it.

How to write your Show HN post#

The title and the first comment are the two things that determine whether your Show HN gets traction. Get these right and you have a shot. Get them wrong and nothing else matters.

The title formula#

The format that works on HN is simple:

Show HN: [Product Name] -- [What it does in plain English]

That is it. No buzzwords. No superlatives. No "the best" or "the fastest" or "AI-powered." Just what it does.

• "Show HN: Pagecrypt -- Client-side password protection for static HTML pages"
• "Show HN: Stashpad -- A markdown notepad for developers"
• "Show HN: I built a tool that finds broken links on your website"

• "Show HN: The Revolutionary AI Platform That Will Transform Your Workflow"
• "Show HN: We're disrupting the $50B analytics industry"
• "Show HN: [Product] -- The best tool for developers (YC W26)"

HN readers decide whether to click based on the title alone. If the title clearly describes something useful or interesting, they click. If it sounds like a press release, they scroll past.

The first comment#

When you submit a Show HN post, immediately add a comment from your own account. This is your chance to tell the story. A strong first comment covers:

URL post vs self-post#

You have two options: submit a URL (which links directly to your product) or submit a text post with your story. A URL post is almost always better. HN readers want to click through and try the product immediately. Put the backstory in your first comment instead.

When to post#

Timing on HN matters more than most people realize because of how the ranking algorithm works. New posts start on the "new" page and need upvotes quickly to reach the front page. If you post when the audience is asleep, you lose that critical early window.

The optimal window#

Post between 8:00 AM and 9:00 AM Eastern Time on a weekday. This catches the US East Coast morning crowd and gets your post in front of people before the front page fills up with the day's submissions.

Why early morning works#

The HN front page algorithm factors in both upvotes and time. A post that gets 10 upvotes in 30 minutes ranks higher than one that gets 10 upvotes in 3 hours. By posting at the start of the US workday, you maximize the window where technically-minded readers are checking HN with their morning coffee.

Block your calendar#

Plan to be available for at least 3 to 4 hours after posting. The comment section is where Show HN posts live or die. If someone asks a question and you respond 8 hours later, the conversation is already over.

How to engage in the comments#

This is where most Show HN launches fail. The product might be good, the title might be perfect, and the timing might be right. But if you handle the comments poorly, you will sink.

The golden rules#

• Respond to every single comment. Yes, every one. Thank people for trying the product. Answer technical questions thoroughly. Acknowledge bug reports.
• Be technical. When someone asks how something works, give them the real answer. "We use a combination of X and Y, with Z handling the edge cases" beats "Our proprietary technology handles that."
• Accept criticism gracefully. This is the hardest part. HN commenters can be blunt, sometimes harsh. Someone will tell you your product is pointless, your architecture is wrong, or your pricing is absurd. Respond with genuine curiosity: "Interesting point -- can you tell me more about what you'd expect?" or "Fair criticism. We went with X because of Y, but I can see the argument for Z."
• Never get defensive. The moment you argue with a commenter, you lose the room. Even if they are wrong. Even if they are being rude. Other readers are watching how you handle it, and defensive founders get downvoted hard.
• Share your numbers. Revenue, users, conversion rates, costs. HN rewards transparency. If someone asks "how are you monetizing this?" and you dodge, it looks bad. If you say "We have 200 users, 12 paying, at $29/month," people respect that.

What not to do#

• Never ask for upvotes. Not on HN, not on Twitter, not in Slack groups. HN actively detects and penalizes vote manipulation. If they catch you, your post gets killed and your account may get banned.
• Do not coordinate voting rings. Sending a link to your team or community with "go upvote this" is vote manipulation. HN's detection is surprisingly good at catching this.
• Do not use multiple accounts. Sockpuppet detection is real on HN.

Handling the traffic spike#

A front-page HN post can send thousands of concurrent visitors to your site in minutes. This is commonly called the "hug of death" and it has killed more launches than bad titles.

Before you post#

During the spike#

Monitor your error rates and response times. If pages start loading slowly, that is worse than being down -- slow pages frustrate users and they leave without trying the product. Have someone watching your monitoring dashboard for the first two hours after posting.

What works on HN (and what gets you killed)#

After watching hundreds of Show HN posts succeed and fail, the patterns are clear.

What works#

• Genuine technical stories. "I built this because I was frustrated with X. Here's the interesting engineering problem I solved" resonates deeply with the HN audience.
• Open-source projects. HN has a strong open-source culture. If your project is open-source or has an open-source component, lead with that.
• Showing your work. Blog posts about how you built something, what you learned, what failed. The behind-the-scenes story often gets more engagement than the product itself.
• Honest trade-offs. "We chose X over Y because of Z, even though it means we can't do W" shows maturity and earns trust.
• Side projects and weekend hacks. HN loves when someone builds something clever in a weekend. The bar for polish is lower when the story is genuine.
• Solving a real problem. "I was doing X manually and it drove me crazy, so I automated it" is the kind of origin story HN respects.

What gets you killed#

• Marketing language. Words like "revolutionary," "disruptive," "next-generation," "10x," "best-in-class" are immediate red flags. HN readers interpret marketing speak as a signal that the product cannot stand on its own merits.
• Asking for upvotes. Anywhere. Even subtly. Even "would love your support on HN." Do not do it.
• Defensive responses to criticism. One defensive reply can tank an entire comment thread and turn sentiment against you.
• Ignoring the comments. Posting and disappearing signals that you do not care about the community. HN is a conversation, not a billboard.
• Overly polished launches. A product with a perfect landing page, a launch video, and coordinated social media looks like a marketing campaign, not a maker sharing their work. HN reacts negatively to this.
• Hiding what the product does. If it takes 3 clicks to understand what your product does, you have already lost. HN readers need to "get it" from the title and the landing page above the fold.

The randomness factor#

Here is the honest part most guides skip: HN is random. Two identical products posted a week apart can have wildly different outcomes. The first might hit the front page and get 300 comments. The second might get 3 upvotes and disappear.

This is why you should never make HN your only launch strategy. Treat it as one channel in a broader approach that includes Product Hunt alternatives, community engagement, and a structured SaaS launch plan.

What to do after your HN launch#

Whether your Show HN hit the front page or flopped, the work does not stop when the traffic dies down.

If it went well#

If it flopped#

Do not panic. A failed Show HN does not mean a failed product. It might mean the title was wrong, the timing was bad, or HN's algorithm simply did not pick it up. You can try again in a few weeks with a different angle or after making significant product improvements. There is no rule against reposting.

Layer your launch channels#

HN should be one piece of a multi-channel launch strategy. Before or after your HN post, validate your product by launching on RankInPublic. The tournament format gives you structured feedback from other founders without the unpredictability of HN's algorithm. Getting real votes and comparisons against similar products helps you refine your positioning before facing the HN crowd.

After HN, keep the momentum going:

• Submit to directories for long-tail SEO value and additional backlinks
• Post on Reddit in relevant subreddits with an honest "I built this" story
• Share your HN launch story on Indie Hackers and Twitter
• Enter weekly RankInPublic tournaments for ongoing discovery
• List on every relevant platform to compound your launch over weeks, not just one day

FAQs#

Can I launch on Hacker News if my product is not technical?#

Yes, but set your expectations accordingly. HN's audience skews heavily toward developers, engineers, and technical founders. Non-technical products can succeed if they solve a clear problem and the story behind them is compelling. Consumer products, design tools, and productivity apps have all hit the front page. But "we built a social media scheduling tool" will get less natural traction than "we built a distributed systems debugger." If your product is not technical, focus your pitch on the problem-solving angle and be ready for questions about your technical architecture regardless.

How long should I wait before posting on HN again if my first attempt fails?#

There is no official cooldown period. You can repost after a few weeks, especially if you have made meaningful improvements to the product. The key is to bring something new to the conversation. "Show HN: [Same Product] -- now with feature X and Y based on your feedback" works well because it shows you are iterating. Reposting the exact same thing a week later does not work and may get flagged by the community.

Should I post my Show HN on a different day than my Product Hunt launch?#

Absolutely. Running both launches on the same day splits your attention and energy. You need to be actively engaged in comments on both platforms for hours. Launch on Product Hunt one day and HN on another, ideally a few days apart. This also gives you two separate spikes of traffic instead of one combined spike that strains your infrastructure. Use the gap between launches to incorporate any feedback you received from the first one.

Is the HN backlink really worth it from an SEO perspective?#

Hacker News has a domain rating of 91, putting it in the top tier of backlink sources alongside sites like Product Hunt (DR 90+) and Reddit (DR 95+). A front-page Show HN post gives you a dofollow link from one of the most authoritative domains on the internet. Beyond the raw authority, HN links also generate secondary backlinks as bloggers and journalists pick up stories from the front page. You can monitor the impact on your own domain with a free authority checker tool.

What if my site goes down during the HN traffic spike?#

If your site goes down while you are on the front page, you are losing the most valuable traffic window of your launch. HN readers will click, see an error, and move on -- they will not come back. This is why you must load test before posting. At minimum, serve your landing page through a CDN like Cloudflare and cache it aggressively. If your product itself cannot handle the load, consider putting it behind a signup wall so the landing page stays up while you rate-limit access to the actual product. Some founders keep a static HTML backup ready to deploy at a moment's notice.

Should I build HN karma before my Show HN launch?#

It helps, but it is not required. Having an established account with comment history signals that you are a genuine community member, not someone who created an account just to promote a product. Spending a few weeks commenting thoughtfully on posts in your area of expertise before launching is worthwhile. That said, plenty of successful Show HN posts have come from relatively new accounts. The quality of the product and the post matters more than your karma score.