How to Post on Indie Hackers Without Getting Ignored: A 2027 Guide

How to post on Indie Hackers comes down to a useful title, a short specific post and fast replies. These indie hackers post tips show how to get upvotes on Indie Hackers and keep your indie hackers engagement steady. If you want a longer series, build in public on Indie Hackers, compare product hunt vs hacker news for a launch, and browse other startup communities.

What Indie Hackers readers respond to

Indie Hackers describes itself on its about page as a place where founders share their stories and can submit posts to ask for help and feedback. It also says the community's upvotes decide which items appear in the weekly newsletter. That tells you what the platform rewards: posts other founders find useful enough to vote for.

The clearest guidance comes from the platform itself. In a 2020 post of tips for making successful posts, Courtland Allen advises starting interesting discussions, asking useful questions, teaching what you have learned and sharing relevant resources. He also advises writing descriptive titles, avoiding your company name in the title unless it is well known, and keeping posts readable with the key points first. The advice is his own opinion rather than research, but it sets a clear baseline.

A later community thread, what kinds of posts would you like to see more of, shows what members said they wanted. Commenters asked for more stories of real experiences and failures, more marketing and sales content, interviews, learning resources and stage based categories such as first customer or ten to a hundred. They asked for less self promotion, "drop your link" threads, clickbait titles and "how I made" posts with nothing a reader can reuse. It is one thread from 2022, so treat it as a snapshot of opinion, but the pattern matches the official advice.

How to post on Indie Hackers, step by step

You do not need a formula, but a repeatable routine helps. Here is one you can adapt.

1. Decide what the post gives the reader

Before you write, finish this sentence: "After reading this, someone will know how to ___." If you cannot, the post is probably an announcement. Announcements are fine occasionally, but a lesson, a number with context, a mistake or a question gives readers a reason to respond.

2. Write a descriptive title

Aim for a title that states the lesson, question or opinion in near full sentence form, as the platform's own tips suggest. Compare these:

The better versions promise something specific and sound like a person talking. Do not invent numbers to make a title stronger. Use real ones or none.

3. Open with the point

Courtland Allen's tips post says to write as if nobody will read past the first five sentences. Put the main result or question there, then explain. A good opening names the situation, the outcome and what you are asking:

"I spent six weeks on a feature nobody used. Here is how I found out, what it cost and what I would check first next time."

4. Structure it so it can be skimmed

Use short paragraphs, a few headings or bullets and one idea per section. The platform's tips also recommend Markdown headings and bullet lists. A skimmable post lets a reader get value in a minute and decide whether to reply.

5. End with one question

"Thoughts?" invites nothing. A specific question does: "Would you pay for this before seeing a demo?" One question per post keeps replies focused.

6. Put the post where the right people are

Courtland Allen's tips say members receive top posts from their groups in an email digest, so posting in the most relevant group can help it reach people who care about the topic. Pick the group that matches the subject, not the one with the most members. Indie Hackers is also only one of several founder communities, so adapt the same post for each place you share it.

7. Add the link last

If your product is relevant, link it near the end, once, and say what it is. Do not lead with it. A post that exists only to link to a product is the kind members said they wanted less of.

Indie hackers post tips for titles and structure

One member analysed 500 front page posts collected over a year and published the results in a study of what goes viral on Indie Hackers. He reportedly found that the top 50 posts had shorter titles on average (about 51 characters against 63 for the bottom 50), that 66 percent of top titles contained a number against 40 percent of the bottom group, and that announcements made up 20 percent of the bottom 50 and none of the top 50. Success stories were the most common top format, followed by guides.

Use those figures carefully. The sample came from the front page, so it skews toward posts that already did well, the dataset is not published, no statistical testing is described, and several comparisons rest on very small counts. The author also promotes his own product in the post. The useful takeaway is the direction, not the percentages: shorter, concrete titles, real numbers where you have them, and fewer pure announcements.

A few habits that follow from this:

• Keep titles under about 60 characters when you can. Short titles read cleanly in a feed.
• Use a real number or a clear outcome. "Lessons from 30 days" beats "Some thoughts".
• Pick a format that teaches. Stories, guides, post mortems and honest numbers travel better than "we launched".
• Skip clickbait. Members said in the thread above that it drives them away.
• Do not worry about the day of the week. The study's day of week differences rest on tiny counts.

How to get upvotes on Indie Hackers without asking

The honest answer is to earn them by being useful and visible. Hacker News says plainly in its guidelines not to solicit upvotes, comments or submissions. Indie Hackers does not list a rule like that on its about page, but the community thread above shows members dislike follow for follow and "drop your link" posts, so avoid asking for votes either way.

What works instead, according to founders who have tried it, is giving before you ask. One founder shared an eight week experiment in authentic engagement. The advice was to upvote five to ten relevant posts a week, leave specific comments rather than generic praise, comment early when a post has few replies, and publish an update every two to three weeks. He reports roughly 80 upvotes received and 20 substantive comments left after eight weeks, for two to three hours a week. That is one account's self reported experience with no comparison group, so treat it as a plan to test, not proof.

A practical version of that plan:

1. Spend ten minutes a day reading the newest posts in your group.
2. Upvote the ones that teach you something.
3. Leave one comment a day that adds an experience or asks a real follow up question.
4. Post your own piece once every two or three weeks.
5. When someone helps you, thank them and say what you changed.

People who see you helping tend to look at your profile and read your posts. That is slower than a one off push, but it is the version that does not feel like spam.

Indie hackers engagement after you hit publish

Posting is half the work. The first hour often decides whether a conversation starts, so be around to reply.

• Reply to every comment. Even a short thank you shows there is a person behind the post.
• Answer the question that was asked. If someone challenges your numbers, explain how you measured them.
• Update the post. Add a short note at the end when you learn something from the replies.
• Follow up. Two or three weeks later, post what happened after you acted on the feedback. Readers like seeing the next chapter, and the same habit is the core of how to build in public as a series.
• Do not argue. If a comment is hostile, reply once with facts or let it go.

Keep a note of which posts led to useful replies, signups or new contacts, and which led to nothing. After a month you will have your own data, which is better than anyone's rules of thumb.

A post template you can copy

Title: [Specific lesson or question, under about 60 characters]

Opening: [Situation, outcome and what you are asking, in 2 or 3 sentences]

What I did
- [Step or decision]
- [Step or decision]

What happened
[A real number or result, and one thing that surprised you]

What I would do differently
[One honest lesson]

Question for you
[One specific question]

Link (optional, once): [What it is, in one line]

Mistakes that get posts ignored

• A vague title. If the title does not say what the post offers, readers keep scrolling.
• An advert in disguise. Posts that exist only to point to a product are what members said they wanted less of.
• A wall of text. Without short paragraphs, headings or bullets, most readers will not start.
• No question. Without an invitation to respond, a post can end in silence.
• Disappearing after posting. If you do not reply, the thread dies, and future readers see a dead thread.
• Reciprocity tricks. Follow for follow and upvote swaps may bring numbers, but they do not bring useful feedback.

What about promotion and links?

The about page does not list posting rules for self promotion, and its terms of service cover things like removal of content and limits on commercial use, so read them before posting anything that reads as an advert. A safe approach is to make the post worth reading even if the link were removed. If you maintain a product, share your page or a relevant tool once, say what it is, and let readers decide.

If you are launching a product rather than telling a story, other venues may suit you better, and the trade offs in show hn vs product hunt are worth understanding first.

Frequently asked questions

Summary

Knowing how to post on Indie Hackers means teaching something, titling it clearly and replying fast. Reuse these indie hackers post tips, learn how to get upvotes on Indie Hackers by helping first, and review your indie hackers engagement monthly. Add build in public tips for a series, weigh product hunt vs indie hackers before launching, and decide where to share your startup. Not listed yet? Submit to circlesaasboard.com.