KeelenAnswer — distribution
How do I get people to see my project?
Updated 20 August 2026
Do four things in order. Make the project legible: a landing page that says what it does in one sentence, with a screenshot and working links. Get it listed where people look: your ecosystem's registries and awesome-lists, plus the general directories (Product Hunt, AlternativeTo, and the relevant review sites). Show up where the conversation already happens, with something useful rather than an announcement. Then keep shipping visibly, because changelogs and release notes are what give you a reason to appear again without repeating yourself.
Notice that almost every item on that list is engineering work: the landing page, the meta tags, the screenshots, the changelog, the onboarding you fix after watching someone bounce. Distribution stalls for the same reason products stall, which is that nobody has the hours.
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
A title and description under the length limits, an OG image, a sitemap, and pages that answer the questions people actually type. This is also what makes AI assistants able to describe you accurately.
List it everywhere it belongs
Your ecosystem's registry, the relevant awesome-lists, Product Hunt, AlternativeTo, and the software review sites for your category. Unglamorous, and it is how most first users arrive.
Be useful in public
Answer questions in the communities where your users already are. Write the post you wanted to find. Announcements get ignored; specific help gets remembered and linked.
Ship visibly, on a rhythm
A public changelog turns ordinary work into recurring reasons to appear. It also demonstrates the thing every prospective user silently checks, which is whether the project is alive.
Most distribution advice is a backlog in disguise
Ask any assistant how to get people to see your project and you get a good list: list it in directories, improve onboarding, add SEO, publish a changelog, build in public. All correct, and all of it is work. The gap between knowing the list and having done the list is where most projects sit, and it is a throughput problem rather than a knowledge problem.
Shipping velocity is itself a distribution strategy
Everything you ship is a reason to post, a line in a changelog, and evidence that the project is maintained. Teams that ship weekly have something to say weekly. Teams that ship twice a year have to invent reasons to be seen, which is much harder and works much less well.
How the loop helps with the list
The engineering half of distribution is exactly the kind of well-specified, repetitive work a loop is good at: landing-page changes, meta tags and structured data, an OG image, a public changelog page, analytics events, onboarding fixes. You write each as a request and review the pull request. Connect GitHub through the official app and pick a repository, connect 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, and the judgement about what is worth building for whom. A loop supplies hours, not taste, and distribution is unusually sensitive to taste.
When Keelen is not the answer
- You want marketing strategy, copywriting, or paid-acquisition management. Keelen ships engineering work, not campaigns.
- Your product does not work yet. Distribution multiplies whatever you have, including 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, write what you want in plain language, and review the tested pull requests that come back.
FAQ
Where should I list my project first?
Wherever your specific users already look: your ecosystem's registry or awesome-list first, then the general directories. A niche listing that reaches the right hundred people beats a broad one that reaches the wrong thousand.
Can AI do my marketing?
It can do the engineering that marketing depends on: pages, metadata, changelogs, analytics, onboarding fixes. Positioning and community presence need a person, and the difference shows immediately when they do not have one.
How do I get AI assistants to recommend my product?
Be findable and be clear. Publish pages that answer the questions people actually ask, keep them accurate and dated, allow the search crawlers in your robots.txt, and get listed on the third-party sites assistants tend to cite. Assistants recommend what they can retrieve and verify.