You have built something. You have tested it. You have shipped it. Now you need people to see it. Hacker News is one of the best places to get that first wave of attention, but the community has sharp instincts. One wrong move and your post gets flagged, downvoted, or ignored. The good news is that the rules are clear. If you follow them, the community will reward you.
Hacker News rewards genuine projects, honest titles, and respectful engagement. To launch without getting flagged, you need a clear Show HN post, a descriptive title, a founder comment that adds context, and a willingness to answer every question. Avoid asking for upvotes, using clickbait, or posting unfinished products.
What belongs on Show HN
Show HN is the section for sharing something you have built. It is not a press release. It is not a landing page for a product that does not exist yet. The community wants to see a working thing they can interact with. If your project is a demo, a beta behind a waitlist, or a tool that requires a login, that is fine as long as the core experience is accessible.
Before you post, ask yourself these questions:
- Can someone try the product right now without jumping through hoops?
- Is the project interesting to developers, designers, or technical founders?
- Does the post explain what the product does in one sentence?
If the answer to any of those is no, you might not be ready for Show HN yet.
How to write a title that does not get flagged
The title is the first thing people see. It is also the first thing the moderation system checks. A bad title can get your post killed before anyone reads a single word.
Follow these rules for your title:
- Start with “Show HN:” followed by the name of your project.
- Add a short description that explains what it does.
- Do not use marketing language, hype words, or exclamation points.
- Keep it under 80 characters.
Here are examples of good and bad titles:
| Good Title | Bad Title |
|---|---|
| Show HN: LogSnap – A lightweight log viewer for Docker containers | Show HN: LogSnap – The best log viewer ever made! |
| Show HN: TaskForge – Turn GitHub issues into sprint boards | Show HN: TaskForge – Revolutionize your workflow |
| Show HN: MailMoat – Block spam before it hits your inbox | Show HN: MailMoat – You won’t believe how much spam this stops |
The difference is clear. The good titles describe the product in plain terms. The bad titles try to sell too hard. Hacker News readers can smell a sales pitch from a mile away.
When to post for the best results
Timing matters on Hacker News. The front page is driven by upvotes over time, so you want to post when the most people are online and active.
The best time to post on Hacker News is between 8:00 AM and 10:00 AM Eastern Time on weekdays. This gives your post the full day to gain traction. Posting on weekends usually results in less visibility. Avoid posting late at night because your post will fall off the “new” page before enough people see it.
If you want to be more precise, aim for 9:00 AM Eastern on a Tuesday, Wednesday, or Thursday. Those days tend to have the highest engagement for technical content.
The first comment is your secret weapon
When you submit a Show HN post, you get one chance to write a comment that appears right below your submission. This is your opportunity to add context, share your motivation, and answer questions before they are asked.
Your first comment should:
- Explain why you built the project.
- Mention the tech stack if it is relevant.
- Highlight one or two features that are not obvious from the title.
- Ask for feedback.
Here is an example of a strong first comment:
I built this because I was tired of switching between three different tools to manage my Docker logs. It uses Go for the backend and a simple React frontend. The key feature is the real-time filtering, which I could not find in any existing tool. Would love to hear what you think about the search performance.
Do not ask for upvotes in your comment. That is a direct violation of the rules and will get your post flagged. Let the quality of your project and your engagement speak for themselves.
How to handle criticism
Hacker News is not a gentle place. People will tell you what they think, and sometimes it will be harsh. That is part of the value. If someone points out a flaw, thank them and explain how you plan to address it.
Here is a simple framework for responding to negative comments:
- Acknowledge the feedback.
- Thank the person for taking the time.
- Provide your reasoning or admit the limitation.
- Ask for more details if needed.
For example, if someone says “This is just a wrapper around an existing tool,” you could respond with:
You are right that it builds on top of Docker’s existing logging. The value I wanted to add was the real-time filtering and the ability to save filter presets. Those features are not available in the default Docker logs. What would make this more useful for your workflow?
This approach shows that you are listening and that you care about improving the product. It also encourages more constructive conversation.
What gets posts flagged or killed
The moderation system on Hacker News is automated in many ways. Certain behaviors will trigger a flag almost instantly.
Here is a list of things that will get your post killed:
- Asking for upvotes directly or indirectly.
- Posting the same link multiple times.
- Using a URL shortener.
- Posting a project that is behind a login wall with no demo.
- Writing a title that is misleading or exaggerated.
- Submitting a post that is clearly an ad for a service you do not own.
If your post gets flagged, do not resubmit the same link. That will make things worse. Instead, fix the issue and wait at least a few days before trying again.
A step-by-step launch process
Here is the exact process you should follow when you are ready to launch on Hacker News:
- Prepare your landing page or app. Make sure it loads fast and works on mobile.
- Write your title following the rules above.
- Prepare your first comment with context and a call for feedback.
- Post at 9:00 AM Eastern on a Tuesday, Wednesday, or Thursday.
- Stay online for the next two hours to respond to every comment.
- Answer every question, even the tough ones.
- After the first day, check your analytics to see where traffic came from and what people did on your site.
If you follow these steps, you give yourself the best chance of a successful launch.
What to do if you hit the front page
Getting to the front page is exciting, but it can also break your server. Make sure your infrastructure can handle a spike in traffic. If you are not sure, use a service like Cloudflare or put a static version of your landing page behind your app.
Once you are on the front page, the comments will come faster. Do your best to keep up. People notice when a founder disappears after posting. Stay engaged for at least a few hours.
Also, watch for duplicate submissions. Sometimes other people will submit your link to the main feed. That can split the discussion. If you see that happen, ask the moderators to merge the threads.
Common mistakes and how to avoid them
Here are the most common mistakes indie founders make when launching on Hacker News:
- Posting too early. Wait until your product is polished enough that the core experience works without bugs.
- Ignoring the comments. Every comment is a chance to learn something or win over a potential user.
- Using a generic title. “Show HN: My new SaaS” tells nobody anything.
- Asking for upvotes. This is the fastest way to get flagged.
- Not having a clear call to action. What do you want people to do after they read your post?
Avoid these mistakes and you will be ahead of most first-time launchers.
How this fits into your broader launch strategy
A Hacker News launch is just one part of a larger plan. It works best when combined with other channels. For example, you might want to coordinate your Hacker News post with a launch on Product Hunt or a post on Indie Hackers. If you are looking for a structured approach to your entire launch week, check out our launch week checklist with 23 tasks every indie developer must complete.
You should also think about what happens after the traffic arrives. If people click through to your site and see a confusing landing page, they will leave. Make sure your landing page is clear and that your signup flow works without friction. Our guide on why your SaaS landing page is not converting can help you optimize that page before you post.
The best Hacker News launches feel like a conversation, not a pitch. The community can tell the difference instantly.
Your first launch is a learning experience
Very few founders get it perfect on the first try. That is okay. Every launch teaches you something about your product, your audience, and your messaging. The goal is not to hit the front page on your first attempt. The goal is to learn what works so you can do better next time.
If your post gets a few upvotes and a handful of comments, that is a win. You got feedback. You made connections. You learned what resonates. Use that information to improve your product and try again.
Keep building and keep shipping
Hacker News is a tool in your toolbox. It is not the only way to grow, and it is not the end goal. The real goal is to build something people want and to keep improving it. A successful launch is just the beginning of that journey.
Now go post your Show HN. Stay humble. Answer the comments. And keep building.
