SEO for Indie Developers: How to Get Your First 100 Organic Visitors

Most indie developers ship a product and then wait. The app works, the landing page is live, and nothing happens — because nobody is looking for it yet. SEO is the slowest-feeling and cheapest way out of that, and for a solo developer with no ad budget it is usually the only one that compounds. Here is the method, with no shortcuts and no promises about how fast it will work for you.

Why SEO Is Worth It When You Have No Budget

Paid ads buy attention for exactly as long as you keep paying. The moment the card stops, so does the traffic. A page that ranks keeps working — not forever, and not without maintenance, but on a completely different cost curve.

The second reason matters more for indie developers specifically: search traffic arrives with intent. Someone typing "how to lock an Android tablet to one app" has the problem already. They are not being interrupted by you; they are looking for you. That is a fundamentally better conversation than an ad impression, and it is the one place where a one-person product can compete with a company that has a marketing department.

The honest caveat, up front: SEO is slow. A new page on a new domain can take weeks to months to rank for anything, and plenty of pages never rank at all. If you need users this month, SEO is not the lever. If you are building something you intend to still be running in a year, start now, because the clock only runs once you publish.

Keyword Research: Find the Terms You Can Actually Win

The instinct is to target the obvious phrase in your category. That phrase is also the one every funded competitor has been working on for years, so it is the one you will not win.

What works instead is going long and specific. "SEO tools" is unwinnable. "How to track keyword rankings for a side project" is a real question, asked by a real person, that a well-written page can answer better than anything currently ranking for it. Fewer people search it — but the ones who do are exactly your users, and you can actually reach page one.

The free research stack. Google's own autocomplete is the most underrated keyword tool there is: start typing your problem category and read what it offers to finish. Those completions are real queries real people type. The "People also ask" and "Related searches" blocks on any results page do the same job. Google Keyword Planner gives you volume ranges with a Google account. Ubersuggest and similar tools will give you a difficulty score on a limited free tier.

How to judge whether you can win a term. Search it and read the first page as a competitor, not as a user. If the top results are thin, generic, obviously AI-spun, or five years out of date, there is an opening. If the first page is all established domains with genuinely thorough pages, pick a different term. This eyeball test is cruder than a difficulty score and it is usually enough.

Prioritise terms where your product is the honest answer. Not where you can bend the post around to mentioning it — where someone finding that page and then finding your product would think "yes, that is what I needed". Anything else ranks and then bounces, and a page people bounce off does not keep ranking.

On-Page Basics That Actually Move Something

None of this requires code, and it is most of what on-page SEO is for a small site.

One page, one search intent. Decide the single question a page answers before you write it. A page that tries to cover five related topics ranks for none of them.

Put the target phrase where it counts: the H1, the page title, the meta description, and the first paragraph — written naturally, as a sentence a human would say. Keyword stuffing has been actively penalised for a very long time; the point is to confirm to a reader in the first two seconds that they landed in the right place.

Write the meta description as ad copy for the click, not as a summary. It rarely affects ranking directly, and it heavily affects whether anyone chooses your result over the one above it.

Link your own pages to each other. This is the step indie developers skip most, and it is free. When you publish something new, go back to the two or three older posts it relates to and link forward to it. Internal links help search engines understand which of your pages belong together, and they keep a reader who liked one page on your site for a second.

Make sure the page can actually be indexed: it loads fast, it works on a phone, it is not blocked in robots.txt, and it is in your sitemap. Google Search Console tells you all of this for free.

Track It, Then Do More of Whatever Worked

Publishing without measuring is how people conclude "SEO does not work" while sitting on one page that was slowly starting to rank.

Set up Google Search Console before you publish anything. It is free and it is the only place that tells you the truth about which queries actually put you in front of someone. Its most useful screen is the one showing queries you are ranking for that you never targeted — those are handed-to-you topics for your next page.

Four things are worth watching in the early months: impressions (are you being shown at all), clicks, average position for your target terms, and which pages are pulling the most. Impressions moving before clicks is normal and is a good sign, not a bad one.

Give it a real window before judging. Checking rankings daily in week one will only make you miserable. Look properly at 30 days, and make decisions at 90.

Then concentrate. When one page starts to move, write two more around the same topic and link all three together. A cluster of related pages tends to lift each other in a way that three unrelated pages never will. When a page has had three months and shows nothing at all, the term was too competitive or the intent was wrong — leave it up and put your time into the cluster that is working.

If you are running more than one project and struggling to keep this going on all of them, How to Manage Multiple Indie Projects Without Losing Your Mind is about exactly that allocation problem. For the wider content side of this — what to publish, not just how to optimise it — see Content Marketing for Indie Developers: How to Get Your First 1,000 Visitors.

What to Expect

Your first hundred organic visitors are not one big win. They are usually a handful of pages each quietly bringing a few people a week, accumulating over a couple of months, from search terms specific enough that nobody else bothered to write a good page for them.

That is the whole game at this stage: find the questions your users are actually typing, answer one of them properly per page, link your pages to each other, and keep a record of what moved so you can do more of it.

---

IndieBob pulls your projects' analytics, content and keyword tracking into one dashboard, so you can see which pages are earning traffic without stitching it together from five browser tabs. → indiebob.com