Hacker News Launch Guide 2026: How to Post on Show HN Without Getting Flagged or Ignored
To post a Show HN submission that survives, build something a stranger can try in under a minute from one link, write a title that describes what the thing does rather than why it matters, submit on a weekday morning in the 6am to 9am Pacific window, and reply to every comment within minutes of it appearing. Never ask friends to upvote or comment. Hacker News detects coordinated voting patterns fast, and that's the single quickest way to get flagged into oblivion.
Hacker News sends more qualified technical traffic per visitor than almost any other channel available to a small team, but it also punishes anything that smells like marketing. Most founders treat a Show HN post like a press release. That's the mistake. The people reading it are the same people who'd flag a post for being promotional, so the entire game is writing and behaving like an engineer sharing something interesting, not a founder selling something.
What Show HN Actually Is (and Isn't)
Show HN is a specific submission category on Hacker News meant for things people have built and can try directly. It is not a general product announcement board. The community norms, enforced informally by moderators and aggressively by users who flag posts, boil down to a few unwritten rules:
- The thing must be usable now, not a waitlist or a coming-soon page.
- The post should let the product speak, not the copywriting.
- Self-promotion is fine as long as it's transparent (you're expected to say "I built this").
- Overt sales language, growth-hacking tactics, and vote requests get you flagged fast.
If your product isn't ready for a stranger to click a link and use it in the next 30 seconds, you're not ready to post. A landing page with a signup form is not a Show HN. A working tool, even a rough one, is.
Before You Submit: The Pre-Launch Checklist
Most failed Show HN posts fail before they're even written, because the product or the page behind the link wasn't ready for the traffic pattern HN sends: a fast spike of skeptical, technical visitors who bounce in seconds if anything is confusing.
Run through this before you touch the submission form:
- The link works with zero friction. No forced signup, no email gate, no "request access." If you must gate something, offer a demo mode or sample data.
- The page loads fast and explains itself in one screen. Assume the reader will not scroll before deciding whether to keep reading.
- You've stress-tested the infrastructure. A well-received Show HN can send several thousand visitors in an hour. If your app falls over, that becomes the story in the comments.
- You have a support channel ready. Someone needs to be watching the comment thread, your inbox, and your error logs simultaneously for the first two hours.
- You've removed anything that looks like growth-hacking. No auto-follow prompts, no "invite 3 friends" walls, no cookie banners that block the demo.
- You know your one-sentence answer to "why did you build this." You will be asked this in the first ten comments. Have a real answer, not a marketing one.
If you're coordinating a launch across Hacker News, Product Hunt, and a few newsletters at once, a tool like welaunch.sh can help you schedule and track that multi-channel push, but the HN post itself should still be written and handled manually. Automation on the post or comments is exactly what gets detected and flagged.
Writing a Show HN Title That Doesn't Get Ignored
The title is doing almost all the work. HN readers scan the new page or the front page in seconds, and a vague or salesy title gets skipped before anyone even clicks.
The format that consistently works is:
Show HN: [Product name] – [what it does, in plain language]
No taglines. No adjectives like "revolutionary," "powerful," or "the best." No em-dash-heavy marketing rhythm. Just a factual description a developer would use to explain the tool to a colleague.
| Weak title | Why it fails | Stronger version |
|---|---|---|
| Show HN: The future of note-taking is here | Vague, hypey, says nothing | Show HN: A note app that auto-links related notes as you type |
| Show HN: Launching my AI startup | Announces the company, not the product | Show HN: I built a tool that turns SQL errors into plain-English explanations |
| Show HN: CoolApp 2.0 – now with more features | Assumes context readers don't have | Show HN: An open-source alternative to Postman built for gRPC |
| Show HN: Check out our new platform | No information at all | Show HN: A CLI that finds unused npm dependencies in seconds |
Keep it under about 80 characters. If you can't describe what the product does in one line, that's a signal to simplify the pitch before you simplify the title.
Timing Your Launch: When to Post on Hacker News in 2026
Timing matters more on HN than on almost any other platform because the front page is a live ranking that decays fast. A post needs early upvotes within the first 30 to 60 minutes to climb, and the pool of active readers at any given hour determines how likely that is.
Based on consistent patterns from founders who've launched repeatedly:
| Timing window (Pacific) | Why it works |
|---|---|
| Tuesday to Thursday, 6am to 9am PT | Overlaps with US morning coffee-and-HN browsing and European afternoon activity, giving you two overlapping audiences |
| Avoid Friday afternoon through Sunday | Traffic and engagement drop noticeably, and posts that would rank on a weekday get buried |
| Avoid US holidays and late December | Lower overall active user count means slower early votes, which matters most in that critical first hour |
| Early morning beats midday | Fewer competing new submissions means your post spends longer visible on the /newest page where early upvotes originate |
Monday mornings can work too, but Tuesday through Thursday tend to have the most consistent traffic without the Monday backlog of unread threads competing for attention.
Don't overthink this to the point of paralysis. A great product posted at a mediocre time will still get traction if the comments hold up. A mediocre product posted at a perfect time will still get picked apart.
The First 60 Minutes: Handling Comments Without Getting Flagged
The first hour decides everything. This is where most founders lose the post, not through bad timing or a bad title, but through how they handle the comment section.
Reply fast, but don't reply defensively. HN commenters, especially the ones who show up first, are often looking for technical weaknesses, unclear claims, or reasons to be skeptical. That's the culture, not an attack on you personally. Treat every critical comment as a chance to demonstrate you know your own product deeply.
Never argue about the flag itself. If a moderator or user flags the post, do not post a comment asking why or accusing anyone of unfairness. That reads as exactly the kind of promotional behavior that gets posts killed. If you think a flag was a mistake, email hn@ycombinator.com directly and briefly explain the situation.
Answer the "why did you build this" question honestly. This is almost always one of the first three comments. A real, specific origin story lands far better than a positioning statement pulled from your landing page.
Don't paste your pitch deck language into replies. Phrases like "seamless," "game-changing," or "we're excited to announce" are red flags for a community that prizes plain technical language.
Acknowledge real bugs immediately. If someone finds a bug in the first ten minutes, the worst response is silence or defensiveness. Say thanks, confirm you're looking at it, and if you fix it live during the thread, say so. That single interaction can turn a skeptical thread into a supportive one.
Don't ask anyone to upvote, share, or comment, anywhere. Not in a Slack channel, not in a tweet, not in a group chat. HN's ranking algorithm and moderation team both actively look for unusual voting patterns tied to external traffic sources, and a detected vote ring gets the post killed regardless of how good the product is.
Common Reasons Show HN Posts Get Flagged
Understanding what triggers flags helps you avoid them before they happen.
| Trigger | What it looks like | How to avoid it |
|---|---|---|
| Vote manipulation | Sudden spike of upvotes from new or inactive accounts | Never solicit votes outside HN, don't ask coworkers to upvote |
| Landing page instead of product | Link goes to marketing copy, not a usable tool | Link directly to the app, demo, or repo |
| Duplicate or repeated posting | Same product posted multiple times in short succession | Space out launches by weeks or months, don't repost after a flag without fixing the underlying issue |
| Excessive self-promotion in comments | Founder replies read like ad copy | Answer technically, skip the sales language entirely |
| Misleading title | Title oversells or hides what the product actually does | Describe the function plainly, no superlatives |
| Broken or slow product under load | Site crashes or times out once traffic arrives | Load test beforehand, use a CDN, have a fallback static page ready |
What to Do If You Get Flagged Anyway
Even careful launches sometimes get flagged, often for reasons unrelated to quality, like a moderator judgment call or a wave of unrelated flags from users who misread the post. If it happens:
- Don't post publicly complaining about it. That almost never helps and often makes things worse.
- Email hn@ycombinator.com with a short, factual note. The moderators (dang and the team) are known for actually reading these and occasionally reinstating posts.
- Wait before reposting. Posting the same link again shortly after a flag usually triggers a stronger penalty.
- Use the feedback. If the flag was about product readiness rather than a misunderstanding, fix the actual issue before trying again.
After the Launch: Turning HN Traffic Into Something Useful
A good Show HN thread can send a meaningful spike of technical, high-intent visitors, but the value is mostly in the first 48 hours unless you capture it. Track sign-ups, GitHub stars, or trial activations specifically from the HN referral so you know what actually converted. Save the thread itself, since detailed technical feedback from HN commenters is often more useful product research than anything you'll get from a survey.
If HN is one leg of a broader launch across Product Hunt, X, newsletters, and communities, keeping the messaging and timing coordinated without repeating the same promotional tone anywhere is the harder part. That's the kind of multi-channel coordination welaunch.sh is built for, while the actual HN post stays exactly what it should be: a founder sharing something real, and sticking around to answer for it.
Ready to Launch
Write the post like you're explaining your project to a sharp colleague, not pitching an investor. Get the timing right, keep the product link frictionless, and show up for every comment in that first hour. That combination is what separates a Show HN that dies in minutes from one that sits on the front page all day.