I've compiled a few basic tips below. If you have any questions or suggestions, leave them in the comments. I'll try to keep this post updated regularly.
Making a successful forum post isn't any different than making a successful product. You have to give people what they want. Otherwise they have a million other things they could be doing.
Indie hackers are tech founders who come here primarily to learn, talk shop, be inspired, discover new things, and (occasionally) lend a helping hand.
Does your post help them do that?
Start interesting discussions, ask useful questions, teach people what you've learned, and share links to relevant resources.
Nobody's going to read your post unless they first decide to click your title, so it needs to be enticing. Luckily, that's easier than it sounds. Some rules of thumb:
People don't click links they don't understand. Describe your post in the title using something close to a full sentence. You don't have have to be clever here.
If you're asking a question, put your question in the title. If you're giving an opinion, put that in the title. If you're sharing advice, state the advice. If you're looking for feedback, say so.
👍 GOOD: "Tips for prioritizing your tasks effectively", "How can I get more views on YouTube?", "Should indie hackers care more about security?"
👎 BAD: "Hello!", "Task management app", "Promo", "My app"
The vast majority of people on IH are merely reading and upvoting. As I said earlier, they want to read interesting and useful things. Your title should make it clear how they'll get that:
👍 GOOD: "How I figured out direct sales"
👎 BAD: "Progress report #2933"
Even if you're asking for help, you can often ask in a way that's useful to everyone, not just you:
👍 GOOD: "What are the best tips for converting blog readers into subscribers?"
👎 BAD: "I need to get more subscribers for NameOfMySpecificBlog"
By the way, unless you have an extremely popular company with a recognizable name, it's almost never helpful to put your company's name in the title of your post.
Indie hackers are busy people. They have things to do, and they'll click the back button if your post is too long or rambling. If possible, keep it short.
If you're writing a long post, put the important, interesting stuff up top. Write as if nobody's going to read past the first 5 sentences, because in many cases, they won't.
You should also make long posts easy to skim. Indie Hackers supports Markdown, so you can use headings (##, ###, etc.) to break your posts into sections, as well as images and bullet lists to break up the monotony.
If you absolutely must write paragraph after paragraph, please, please, please put blank lines between them. Nobody will attempt read a bunch of paragraphs smashed together.
Indie Hackers rewards posts that generate the most discussion, because we want more people to see the best stuff.
One way to get more comments is to post inside the relevant group, as group members will the best posts for the day in their email digest.
Also, don't be shy about sharing posts on Twitter or with colleagues.
From the forum homepage, it's easy to click to navigate to the top posts on Indie Hackers for the week, the month, and all time. Spend a few minutes browsing for inspiration if you'd like to see what other IHers find helpful.