How to Launch on Hacker News in 2026: A Show HN Playbook That Won't Get Flagged or Buried

Hacker News can send you 50,000 visitors, a wave of signups, and a permanent SEO-friendly backlink in a single afternoon. It can also flag your post to death in nine minutes if you get the format wrong. There is no in-between on HN, and that is exactly why founders keep coming back to it despite the risk.

This is a tactical playbook for getting a Show HN post to the front page, written for people who have actually shipped something and want the post to survive contact with the community.

Why Show HN Is Different From a Regular Launch

Show HN is not a press release format. It is not Product Hunt. The audience is mostly engineers, technical founders, and people who have built things themselves, and they can smell marketing copy from three sentences away.

The unwritten rules of Show HN:

• The product should be usable without a sales call, a waitlist, or a "book a demo" wall.
• The post should read like a builder talking to other builders, not a company talking to customers.
• Self-promotion is allowed and expected in the Show HN category, but it still needs to feel like a genuine share, not a pitch.
• Comments matter more than the post itself. A great post with a founder who goes silent in the thread underperforms a mediocre post with an engaged, honest founder.

If you keep those four things in mind, you are already ahead of most Show HN submissions, which read like landing page copy pasted into a text box.

Writing a Show HN Post That Doesn't Read Like Marketing

The Title Format

HN has a de facto title convention: "Show HN: [Product] - [what it does, plainly]." Not a tagline. Not a value prop. A literal, boring description of the thing.

Bad: "Show HN: Launchly - The Future of Product Launches"

Good: "Show HN: I built a tool that schedules your product launch across 12 channels at once"

The second version tells a reader exactly what happens when they click. The first one triggers the same reflex as an ad, and HN readers have a very well-trained ad reflex.

Keep it under 80 characters where possible. If your product name is unfamiliar, describe the function first and the name second, or skip the name in the title entirely.

The Body Copy

The post body (what shows up as the first comment, essentially) should cover, in order:

1. What it is, in one sentence. No adjectives. No "revolutionary," no "seamless," no "powerful."
2. Why you built it. A real problem, ideally one you personally hit. This is the part that builds trust. "I kept losing track of which launch channel drove which signups" is more credible than "we saw a gap in the market."
3. What it actually does technically. HN readers want the mechanism, not the outcome. If you built something with an interesting architecture decision, a scraping approach, a novel use of an LLM, or a tricky sync problem, say so. This is your credibility anchor.
4. What's rough or unfinished. Naming your own limitations preempts the first three comments that would have pointed them out anyway, and it reads as honest.
5. A direct link and how to try it without friction. No signup wall if you can avoid it. If you must gate something, say so plainly.

Keep the whole thing under 200 words. Show HN posts that run long read as if you're compensating for a thin product.

What Gets Flagged Fast

Moderators and the community flag posts for a specific set of reasons. Avoid these and you clear the first filter:

• Vague or hype-y titles. "Show HN: The Best Way to Manage Your Team" gets flagged before anyone even opens it.
• Landing pages with no working product. If the link goes to a waitlist form, expect flags and comments calling it out within minutes.
• Reposting too soon. HN's guidelines allow reposting if a launch has meaningfully changed, but reposting the same thing within a few months reads as spam.
• Vote manipulation. Do not ask friends, Slack groups, or Twitter followers to upvote. HN's ranking algorithm actively detects unusual upvote velocity from new or low-karma accounts and will kill the post's ranking even if it isn't outright flagged. This is the single most common way good launches get buried, and it's self-inflicted.
• A founder who doesn't show up. Threads that go unanswered for hours look abandoned, and low engagement accelerates the natural drop-off in ranking.

Timing a Hacker News Launch

Timing is not a minor detail on HN, it is close to half the outcome.

Best Days and Times

• Tuesday through Thursday consistently outperform Monday and Friday. Monday's front page is crowded with weekend backlog; Friday traffic drops off by early afternoon US time.
• Post between 7am and 9am Eastern (roughly noon to 2pm UK time). This lines up with the overlap of East Coast US morning readers and European afternoon readers, which gives you two waves of traffic instead of one.
• Avoid US holidays and the week between Christmas and New Year. Traffic is real but thinner, and thin traffic means less chance of the early upvote velocity that gets you onto the front page.

Understanding the Ranking Window

A new Show HN post lives or dies in its first 60 to 90 minutes. HN's ranking algorithm weighs recency heavily, but it also weighs the ratio of upvotes to page views, and it discounts votes that look coordinated (arriving in a tight cluster from accounts with no history).

Practically, this means:

• Don't blast the link to your whole audience the second you post it. A slow, organic trickle of genuine upvotes over the first hour beats a spike.
• Don't post and walk away. Sit at your desk. The first 90 minutes is when you need to be answering comments fastest, because early engagement also feeds the ranking signal.
• If it doesn't catch in the first hour, it usually won't. That's fine. HN gives you more shots later if you have something genuinely new to show next time.

Handling the Comment Thread

This is the part most founders underprepare for, and it's the part that determines whether the launch actually converts into users, or just traffic.

Answer Fast, Answer Honestly

Respond to comments within minutes where you can, especially in the first hour. Speed signals that a real person is behind the post, not a marketing team running a campaign.

When someone points out a bug, a security concern, or a design flaw, the correct move is almost always to agree, thank them, and say what you'll do about it. HN rewards founders who take criticism well far more than it rewards founders who launch a flawless product. Arguing with a well-reasoned critical comment is one of the fastest ways to tank a thread's overall sentiment, which drags down engagement and, indirectly, ranking.

The Comment Types You'll See

• The "why not just use X" comment. Answer this directly and specifically. Don't get defensive. If X is genuinely better for some use cases, say so.
• The technical deep-dive question. These are gold. Answer thoroughly. These threads often become the most-upvoted comments and pull more eyes into the post.
• The pricing or business model skeptic. Be transparent about how you make money. HN is allergic to vagueness here.
• The pure nitpick. Fix what's fixable, thank them, move on. Don't spend your limited attention window on someone quibbling about a font.

What Not to Do in Comments

• Don't reply with copy-pasted answers to different people. It's noticeable and it reads as impersonal.
• Don't argue about whether a criticism is "fair." Answer the substance instead.
• Don't disappear for a stretch of hours. If you have to step away, say so in a comment; "stepping away for an hour, will answer more questions after" reads better than silence.

What a Good Show HN Launch Actually Gets You

Set expectations correctly. A front-page Show HN post typically drives:

• A short, sharp traffic spike, often 10,000 to 60,000+ visits depending on how long it stays on the front page.
• A wave of signups that converts at a lower rate than warm channels, because HN traffic is curious, not necessarily buying-intent.
• A durable backlink and a long-tail SEO benefit, since HN threads rank well and get indexed permanently.
• Direct, often blunt product feedback that's genuinely useful for roadmap decisions, if you're willing to read past the tone.
• A small number of high-quality users who become vocal advocates, because HN's audience skews toward people who build things themselves and talk about tools they like.

What it usually doesn't get you: a sustainable growth channel. Treat a Show HN post as one strong day inside a longer distribution plan, not the plan itself.

Coordinating Show HN With the Rest of Your Launch

Because a Show HN post depends so heavily on tight comment-thread response and specific, non-marketing copy, most founders end up writing it separately from their Product Hunt post, their Twitter/X thread, and their press outreach, which all use a different register. This is where a tool like welaunch.sh is useful in practice: it helps founders prep channel-specific copy (the plain, technical HN voice versus the punchier Product Hunt tagline versus the press-ready one-pager) ahead of time and schedule the multi-channel push around the HN posting window, so you're not writing your Show HN body copy at 6am while also trying to queue up a Twitter thread.

A Simple Show HN Launch Checklist

Before you hit submit:

• Title is plain, descriptive, under 80 characters, no hype words
• Post body is under 200 words and covers what/why/how/limitations
• Product is usable without a signup wall, or the gate is disclosed upfront
• You have not asked anyone to upvote
• You're posting Tuesday, Wednesday, or Thursday, 7 to 9am Eastern
• You've blocked out the next 2 to 3 hours to answer comments personally
• You know your answer to "why not just use [obvious competitor]"
• You're ready to admit what's broken or unfinished

A Show HN launch is less about the perfect pitch and more about showing up as a credible builder in front of a skeptical, technical crowd. Get the format right, time it deliberately, and treat the comment thread as the real launch, and the flag queue stops being something to fear.

If you're coordinating a Show HN post alongside a broader launch week, welaunch.sh can help you draft the channel-specific copy and keep the timing straight across HN, Product Hunt, and everywhere else you're showing up.