Hacker News Launch Guide 2026: How to Post to Show HN Without Getting Flagged or Ignored

To post a successful Show HN in 2026, submit a working product (not a landing page), use a title that starts with "Show HN:" and describes what the thing does in plain language, add a first comment explaining what you built and why, submit on a weekday morning US Eastern time, and reply to every comment within minutes. Avoid asking anyone to upvote or vote-ring, since Hacker News's ranking system detects coordinated activity almost immediately and kills the post.

Hacker News sends more qualified, technical traffic per visitor than almost any other channel, but it also has the least tolerance for anything that smells like marketing. Founders who treat it like Product Hunt or Twitter get flagged, buried, or ignored within an hour. Founders who understand the culture can get 50,000+ visits, real signups, and honest product feedback from the exact audience that later becomes their loudest advocates.

What Show HN Actually Is (and Isn't)

Show HN is a submission category for things people can try right now. It is not a category for announcements, funding news, or "we're building X, thoughts?" posts. The community enforces this distinction ruthlessly.

If your product isn't usable without a signup wall, a demo video, or "email us for access," it's not ready for Show HN yet. Get it to a state where a stranger can click a link and do something meaningful in under 60 seconds.

Before You Submit: The Pre-Launch Checklist

Most Show HN failures happen before the post ever goes live. Run through this before you hit submit:

1. The product loads fast and works without an account, or the signup flow takes under 30 seconds.

2. You've stress-tested the server. A front-page HN spike can send 5,000 to 20,000 visitors in a few hours. If you're on a $5 droplet with no caching, it will fall over.

3. You've removed anything that looks like a marketing funnel on the landing page: no fake urgency, no "limited spots," no auto-playing video with sound.

4. You have a changelog or roadmap page ready, because commenters will ask what's next.

5. You know your own tech stack cold, because the top comment will likely be a technical question about it.

6. You're not launching the same week as a major HN-favorite competitor or a big tech event. Check the front page history for context.

Crafting the Perfect Show HN Title

The title is doing almost all the work of getting someone to click. HN titles that perform well share a pattern: plain description, no adjectives, no hype.

Formula that works: "Show HN: [Product name], [what it does in 8-12 words]"

Examples of titles that actually did well on HN:

• "Show HN: I built a tool that turns SQL queries into REST APIs"
• "Show HN: Postgres migrations without downtime"
• "Show HN: A CLI that finds unused dependencies in your repo"

Examples that get flagged or buried fast:

• "Show HN: The future of productivity is here"
• "Show HN: We're disrupting the $50B project management market"
• "Show HN: My revolutionary AI-powered everything app"

Avoid superlatives ("best," "revolutionary," "game-changing"), avoid market-size claims, and avoid emoji. HN's audience is allergic to language that sounds like it was written by a growth marketer instead of the person who wrote the code.

Writing the First Comment

Immediately after submitting, post a comment on your own thread. This is not optional. It's the single highest-leverage piece of copy in the entire launch.

A strong first comment does four things in under 200 words:

1. States what the product does and who it's for.
2. Explains the origin story briefly (why you built it, what problem you hit).
3. Names the stack or technical approach, since HN readers want to evaluate the engineering, not just the pitch.
4. Invites specific feedback ("I'd love to know if the onboarding flow makes sense" beats "let me know what you think!").

Here's a structure that consistently works:

Hey HN, I'm [name], solo founder of [product]. I built this after running into [specific problem] while working on [context]. It's a [one-line description]. Stack is [languages/frameworks]. The trickiest part was [one honest technical challenge]. Happy to answer anything about the architecture or the decision to [specific tradeoff]. Feedback on [specific area] especially welcome.

Skip the corporate tone entirely. Write it the way you'd explain the project to another engineer at a meetup, not the way you'd write a press release.

Timing Your Submission

Timing affects visibility more than almost any other variable you control, because Show HN's "new" queue moves fast and only a fraction of submissions ever get enough early upvotes to reach the front page.

The early morning window matters because Show HN ranks partly on upvote velocity in the first 30 to 60 minutes. If you post at 7 AM Eastern, you catch the US East Coast waking up, followed by the West Coast a few hours later, followed by a secondary wave from Europe the next morning if you're still on the front page.

Avoid posting during major tech news cycles (a big acquisition, an OpenAI announcement, a large outage) since those stories will dominate the front page and bury everything else.

How HN's Ranking and Flagging Works

Hacker News uses a modified version of a gravity-based ranking algorithm: newer posts with high upvote velocity rank higher, but the score decays over time. Flags work as a counterweight. Enough flags, or a moderator's own judgment, can remove a post from listings entirely even if it has positive upvotes.

Posts get flagged for:

• Vote manipulation. Asking friends, Slack groups, or Twitter followers to upvote is detectable and gets posts killed within minutes. HN's software specifically watches for clusters of new accounts voting on one thread.
• Marketing language in the title or first comment.
• Reposting the same product within a short window without material updates.
• Off-topic self-promotion buried inside an unrelated thread.
• Duplicate accounts posting supportive comments on your own launch.

If your post gets flagged, do not create a new account and resubmit. That pattern gets accounts banned. Instead, email hn@ycombinator.com, explain the situation honestly, and ask what happened. Moderators do respond, and they do reinstate posts that were flagged in error.

Engaging in Comments Without Sounding Defensive

The comment section is where launches actually get won or lost. HN commenters are disproportionately experienced engineers, and they will find your product's weak points fast. How you respond matters more than the criticism itself.

Do:

• Thank people for specific, substantive criticism, even sharp criticism.
• Answer technical questions with real detail, including tradeoffs you made and regret.
• Concede points when someone is right. "Yeah, that's a fair criticism, we're addressing it in the next release" reads far better than a defense.
• Reply fast, ideally within 10 to 15 minutes, especially in the first two hours.

Don't:

• Argue with someone calling your pricing or positioning wrong. Ask what they'd do differently instead.
• Post from a second account to defend yourself. This is easy to spot and gets both accounts flagged.
• Disappear after the first hour. Threads that go quiet from the founder lose momentum and credibility.
• Copy-paste the same response to multiple similar comments. People notice and call it out.

A useful mental model: every comment is a chance to demonstrate competence and humility at the same time. HN forgives a mediocre product with an honest, engaged founder far more than it forgives a great product with a defensive one.

Common Mistakes That Get Show HN Posts Flagged or Ignored

• Submitting a landing page instead of a working product
• Using the word "disrupt," "revolutionary," or "game-changing" anywhere in the title or comment
• Asking for upvotes in any channel, public or private
• Launching a product that's a thin wrapper around an existing API with no differentiation explained
• Ignoring the first hour of comments while you're "getting coffee"
• Posting the exact same submission twice in a short window after low traction the first time
• Having a broken signup flow or a server that can't handle the traffic spike

What Happens After: Turning Traffic Into Signups

A front-page Show HN post can send tens of thousands of visitors in a single day, but HN traffic converts differently than paid traffic. Expect lower signup conversion rates than a targeted ad campaign, because a large share of visitors are there to read the thread and evaluate the engineering, not necessarily to become customers immediately.

To capture value from the spike:

1. Add lightweight analytics before you launch so you can see where people drop off.
2. Make the core action (signup, install, first API call) require the fewest possible steps.
3. Have a simple email capture as a fallback for people who like the product but aren't ready to commit.
4. Cross-post the momentum. A strong Show HN thread is good evidence to reuse on Product Hunt, relevant subreddits, and niche newsletters in the days that follow, since a positive HN reception adds credibility elsewhere.

If you're coordinating a Show HN post alongside a broader multi-channel launch (Product Hunt, Twitter/X, newsletters, relevant subreddits), a tool like welaunch.sh can help you sequence and track those channels so the HN spike doesn't happen in isolation from the rest of your launch push.

Final Pre-Submission Checklist

• Product works without friction for a first-time visitor
• Server can handle a traffic spike
• Title follows the plain-description formula, no hype words
• First comment drafted and ready to post immediately
• Submission scheduled for Tuesday, Wednesday, or Thursday morning, US Eastern
• You've cleared your calendar for the next 4 to 6 hours to reply to comments
• No requests for upvotes sent anywhere, to anyone

Hacker News rewards honesty and punishes anything that reads like a pitch deck. Build something real, describe it plainly, show up in the comments, and let the thread do what it does best: tell you, in public, exactly what to fix next.

If you want help lining up your Show HN post with the rest of your launch calendar, welaunch.sh can handle the multi-channel scheduling so you can focus on the comment thread when it matters most.