Show HN: How to Write a Hacker News Post That Actually Gets Traction

Hacker News is the highest-signal launch channel available to an indie founder with no budget and no audience. A Show HN that hits the front page can send 5,000-20,000 visitors in 24 hours, generate hundreds of substantive comments, and produce the kind of feedback that 1,000 user interviews couldn't replicate. It can also disappear into the "new" queue with 2 upvotes and never be seen again. The difference between those two outcomes is not luck — it's a handful of specific, learnable things that most founders either don't know or don't do.

What Hacker News is actually good at

Before the tactics, it's worth being honest about what HN is and isn't. The HN audience is overwhelmingly technical — developers, founders, researchers, and technologists. If your product is for that demographic, a Show HN is probably your single best launch channel. If your product is for restaurant owners, elementary school teachers, or anyone else outside the tech world, HN will generate interesting discussion but almost no actual customers.

The second thing to understand is that HN is not a marketing platform — it's a conversation platform. The posts that do well are the ones that generate a genuine conversation. The posts that fail are the ones that read as product announcements looking for upvotes. The algorithm actively deprioritizes submissions that get fast upvotes without comments, because fast upvotes without engagement usually mean the submitter's friends are voting it up. What HN rewards is early, substantive engagement from users it doesn't recognize — people who found it organically and found it worth discussing.

The title is everything

The most common reason a Show HN fails is the title. Specifically, titles that:

• Lead with marketing language ("The revolutionary platform for...")
• Are vague about what the product actually does ("Show HN: I built something for productivity")
• Over-explain ("Show HN: A web app that uses AI to automatically generate and send personalized email follow-ups based on calendar events and CRM data")

The title format that works on HN is: Show HN: [What it is] ([the key differentiator or unexpected thing about it])

Examples that work:

• "Show HN: I built a tool that converts any PDF into a flashcard deck"
• "Show HN: Stripe Atlas alternative that works in 150 countries"
• "Show HN: A text editor that shows you how long each sentence takes to read"

The pattern: specific noun phrase for the product, specific claim in parentheses that either states the differentiator or names the surprising constraint. The parenthetical is optional but tends to increase click-through because it tells the reader what's interesting about this specific thing, not just what category it's in.

What you're optimizing for is for someone scrolling the front page to understand the product in 4 seconds and feel like there's something worth clicking to learn more about. "I built a tool that converts any PDF into a flashcard deck" does that. "AI-powered learning platform" does not.

Timing: when to post

HN is heavily US-centric. The best posting windows, in order:

1. Monday–Wednesday, 7-9am ET — early week, high traffic, tech workers arriving at their desks
2. Tuesday–Thursday, 12-2pm ET — lunch hour browsing spike
3. Avoid Friday afternoon and weekends — traffic drops significantly, HN audience skews toward weekend hobbyists rather than professionals who are your likely customers

Post at the start of the window, not the end. Early upvotes matter more than total upvotes; a post that gets 5 upvotes in the first 30 minutes outranks one that gets 20 upvotes spread over 3 hours, because the algorithm weights velocity. Being first in your time window gives you the best velocity window.

The first comment is yours

After posting, immediately write the first comment yourself. This is not cheating — it's how the best Show HN submissions work. The first comment should:

1. Add context the title couldn't fit — why you built this, what problem you were solving personally
2. Be honest about the current state ("It's rough around the edges in a few places, especially X")
3. Invite specific questions ("Happy to go deep on Y if anyone's curious about the technical implementation")

This comment sets the tone for the entire thread. A first comment that leads with "hope you find this useful, happy to answer questions" signals that you're a human who wants feedback. A first comment that's a feature list or a pitch signals that you're using HN as a broadcast channel, and the community responds to that badly.

The other reason to write the first comment immediately is practical: if the first comment on your post is a criticism or a "what's the difference between this and X?" challenge, that becomes the frame through which everyone else reads the discussion. Your own first comment prevents that by establishing your framing first.

Responding to comments: the only rule

Respond to every comment in the first two hours. Not a template response — a specific one that engages with what the person actually said. If someone asks "how does this compare to X?" give a real answer, including the honest "X does Y better than we do, but we do Z differently." HN commenters can detect a defensive or evasive response immediately, and a bad response to a challenging question often does more damage than the question itself.

The founders who get the most out of Show HN posts are the ones who treat the comment section as a research session, not a customer service queue. HN commenters who criticize your product are usually telling you something real — something your users will think but not say, something your landing page is failing to address, something about the positioning that doesn't land for a technical audience. That feedback is worth more than any user research you could buy.

What to do in parallel on launch day

A Show HN that performs well generates a traffic spike that lasts 24-36 hours, then drops sharply. Before the spike, make sure:

• Your server can handle it (HN traffic is bursty and can hit 500+ concurrent visitors within minutes of hitting the front page)
• Your onboarding flow is as simple as possible — HN visitors are technically sophisticated but also impatient, and a complex signup flow loses them
• You have an email capture for visitors who don't sign up immediately — the spike is brief and you want a way to reach people who were interested but not ready

Running a pay-to-rank listing on outbids.es in parallel on the same day captures the visitors who discover you through a different path — the board audience and the HN audience are different people, and there's no downside to being visible in both places simultaneously.

What if it doesn't make the front page?

Most Show HN posts don't make the front page. This is the norm, not a verdict on your product. A few things to know:

• You can resubmit after 30 days with a different title if you believe the title was the problem. Don't change the URL — changing the URL to get a fresh post is against the rules.
• A Show HN that doesn't front-page still shows up in search results. A surprising number of people find Show HN posts by searching for the product category months or years later. Your post has long-tail SEO value even if it never trends.
• The comments you receive on a post that doesn't front-page are often more candid and useful than the comments on a post that does. Front-page posts attract pile-on dynamics; a smaller post tends to attract more genuine engagement from the people who found it.

After HN: the follow-up post

If your Show HN does get traction, a follow-up post 2-4 weeks later tends to perform well: "Show HN: [Product] — 30 days later (what we learned)" or a post about a specific technical decision you made that the community found interesting in the comments. The HN community rewards honesty about what worked and what didn't, and a thoughtful follow-up can generate a second spike and establish you as someone worth following.

The pattern of Show HN → real engagement → follow-up post is one of the most consistent ways to build a small, loyal audience on HN over time — and HN audience members tend to be exactly the people who become power users, write about your product, and refer other technical people to it.

The short version

Write a specific, concrete title. Post Tuesday or Wednesday morning ET. Write your own first comment with honest context. Respond to everything in the first two hours. Don't treat it as a broadcast — treat it as the first conversation with a very smart, skeptical potential user.

If you're launching this week, submit your project to the board on the same day as your Show HN — the channels are complementary and the audiences don't overlap.