KeelenAnswer · distribution
How do I get people to see my project?
Updated 11 September 2026
Do four things in order. First, make the project easy to read. A landing page should say what it does in one line. Add a screenshot and working links. Second, get it listed where people look: the registries and awesome lists for your stack, plus the big lists like Product Hunt, AlternativeTo, and the review sites for your niche. Third, join the talk where it already happens. Bring something useful. Do not just post a launch note. Fourth, keep shipping where people can see it. Changelogs and release notes give you a reason to show up again.
Some of those steps are build work. The landing page, the meta tags, the screenshots, the changelog, the onboarding fix after you spot a problem. Keelen can ship a change you spell out. It does not make a plan for reach. It does not promise visitors.
What to do, in order
Fix the first ten seconds
One sentence saying what it does and for whom, a screenshot or a short demo, and an obvious next action. Traffic to a page that does not explain itself is wasted twice.
Get the basics indexable
Add a title and a description, and keep both under the length limits. Add an OG image and a sitemap, along with pages that answer the questions people type. This gives search systems useful facts. Where you land in the results is a separate thing.
List it everywhere it belongs
Your ecosystem's registry can be a start. So can the relevant awesome lists, Product Hunt, AlternativeTo, and the review sites for your category. Pick the places your real audience goes. Follow their rules. Track the referrals you get, and do not assume a listing will bring first users.
Be useful in public
Answer questions in the groups where your users are. Write the post you wish you could find. Posts that only sell get skipped. Posts that help get saved and linked.
Ship visibly, on a rhythm
A public changelog gives you reasons to show up again. It also shows the one thing every new user checks in silence. Is the project still alive?
Most distribution advice is a backlog in disguise
Ask any assistant how to get people to see your project. You get a good list. List it in directories. Improve onboarding. Add SEO. Publish a changelog. Build in public. All of it is correct, and all of it is work. Most projects sit in the gap between knowing the list and doing the list. That is a throughput problem. Knowing the list is easy.
Shipping velocity is itself a distribution strategy
Everything you ship is a reason to post and a line in a changelog. It is also proof that the project is alive. Teams that ship weekly have something to say every week. Teams that ship twice a year have to invent reasons to be seen. That is much harder, and it works much less well.
How the loop helps with the list
A loop is good at the build half of reach. Landing page edits. Meta tags and structured data. An OG image. A public changelog page. Analytics events. Onboarding fixes. You write each one as a request, then check the pull request. Connect GitHub through the official app and pick a repository. Add a model key. Write your first request in plain language, then press play. Plans start at $29 a month.
What stays yours
Positioning. The actual writing. Which communities to join. The judgement about what is worth building, and for whom. A loop supplies hours. It does not supply taste, and distribution is very sensitive to taste.
When Keelen is not the answer
- You want a marketing plan, ad copy, or paid ads. Keelen does build work. It does not run ads.
- Your product does not work yet. Reach grows what you have. If you have nothing, it grows nothing.
- You are looking for growth hacks. There are none here, only a list somebody has to execute.
Hand the work to a loop
Connect a repository and write what you want in plain language. Review the tested pull requests that come back.
FAQ
Where should I list my project first?
Go where your users already look. Start with the registry or awesome list for your stack. Then try the big lists. A small list that reaches the right hundred people beats a broad one that reaches the wrong thousand.
Can AI do my marketing?
It can do the build work that reach depends on. Pages, meta tags, changelogs, analytics, onboarding fixes. Positioning and the real group presence still need a person. The gap shows fast when nobody owns them.
How do I get AI assistants to recommend my product?
Be findable. Be clear. Publish pages that answer the questions people actually ask. Keep them accurate and dated. Let the search crawlers in through your robots.txt. Get listed on the third party sites that assistants tend to cite. Assistants recommend what they can retrieve and verify.