Help your Indie Hackers posts reach founders who read the feed

Posts appear in the newest feed and in group feeds, and strong ones can reach the homepage, where far more founders see them. The site's founder has described a sorting system that gives weight to early upvotes and to discussion, and that favors reactions from longer-standing members slightly. Good titles and a clear question help it along. The site also lists every post newest first on one page, which is where many members look for threads to answer.

Sound method, proper tool: Upvote.club exists to get this right. Early votes give a post the signal the feed responds to, and replies turn it into a discussion. A post that offers nothing to a founder will still be passed over, so the writing comes first, and support gets good writing in front of readers sooner.

Profile growth, delivered by the right tool, which here is Upvote.club. Founders who get votes and replies on their first posts build a name others notice, and that name makes later posts easier to launch. Read the upvote page and the comment page to choose where to begin.

Choose votes when the post is good and needs a visible start. Choose comments when you asked a question and want answers, such as feedback on a landing page. Many founders use votes for a launch post and comments for a feedback post. You can also run both on the same post using two separate requests, since votes make the thread look worth joining and replies make it worth staying in.

Posts that teach something from your own work, describe a result or ask a specific question tend to fit. The site's guidance suggests descriptive titles, helpfulness to others and a post short enough to answer. A post that only repeats a product name rarely does well. Add a screenshot link only if it helps the reader answer.

State the topic as a plain sentence a founder would click: the question you ask, the lesson you learned or the result you got. Avoid vague titles such as 'My app' or 'Progress report', and avoid putting a company name in the title unless it is widely known. A title that makes the benefit clear lets readers decide in a second.

Pick the group closest to your subject, such as a marketing, SaaS or bootstrapping group. Members of a group receive the best posts of the day by email, so a post inside the right one reaches people who care about the subject. Read a few recent threads in the group first, then match the tone, length and kind of question that gets answered.

Describe the product in two sentences, say who it is for and ask one concrete question, such as which headline reads clearer. Make it easy to reply by keeping the post short and ending on the question. Then answer every comment, because a thread where the author takes part attracts more replies, and say thanks to people who give you something you can use.

Yes, and it pays back. Specific comments on posts with few replies get noticed by the author, and many founders visit the profile of a thoughtful commenter. That visibility prepares the ground for your own posts and builds goodwill. Aim for a couple of useful comments every week, and ask a follow-up question each time so the author has a reason to answer you.

As early as possible. The site's own notes link early upvotes to better placement, and new comments are shown first for a short window. Support at publication time gives the post its strongest chance to be seen while the feed is still deciding.

Slow and steady works better than constant. Founders who document their progress report that one post every two or three weeks, plus a handful of votes and comments on other people's posts each week, builds recognition over time. Post when you have a lesson or a result, not to fill a calendar.

It can. MCP connectors and the API let a script or an AI assistant place the same requests you would place by hand, and the API page covers Indie Hackers. Write each post yourself, in your own voice, since founders can tell when a post was mass-produced and tend to ignore it.

Starting is free, and login is through Apple or Google. Your post has to be public so people can open it from the link. Drafts and private notes cannot receive reactions, since nobody else can read them. Paste the address of the post itself, not your profile or product page.

Your product page takes progress updates, such as a first customer, a revenue figure or a lesson from a launch. The site's founder has encouraged members to create a product page and post updates regularly, sharing what they learned as well as what they achieved. These updates appear on the product page and can reach a leaderboard, where other members read, encourage and give feedback. Write each update as a short story with a number and a lesson, and link the product page from your posts so readers can follow the whole journey.

Yes. A study of 500 front-page posts found that you do not need to win before sharing something readers find worth reading, and the examples that did well came from the first steps: a first one hundred dollars, a first batch of beta testers, a first hundred users from Reddit. Early-stage posts work when they show a specific process that another founder can copy. Describe what you did, what it produced and what you would change, then use upvote.club to bring the first reactions to the post.