Building got easy. Getting found didn't.
Most indie developers don't skip SEO because they think it's useless. They skip it because building feels real and content doesn't.
That's the whole problem in one sentence. Ship a feature, and you get a closed loop. You write the code, it runs, someone clicks the button, the fucking thing works, the reward lands the same day.
Write an article, and you get nothing back for months. You publish, you check the numbers, you see four visitors, and two of them were you. So you go back to the codebase where the feedback is instant and reliable.
I've built enough products to understand the pull. Shipping is the part that feels like progress. But feeling like progress and being progress are different things, and the gap between them is where most solo products quietly die.
Read also: Is Indie Hacking Dead?
The tangible trap
The excuses are always a variation on the same belief: build it, and they will come. Nobody says it out loud anymore because it sounds naive, but the behavior gives it away.
Founders spend weeks on a settings page that no one asked for and zero hours on being findable. They tell themselves SEO is for big companies with marketing teams.
They assume Google won't rank a small site. They decide their niche is too small to bother. They tried it once, published three posts, saw nothing, and quit before the compounding could start.
Underneath all of it is one honest reason most people won't admit: they don't enjoy writing, and building gives them a place to hide.
Every hour spent on the product is an hour not spent on the uncomfortable, slow, unglamorous work of getting discovered. The codebase becomes a very sophisticated form of procrastination.
The market doesn't care how good your product is if the market can't find it. A great product with no distribution isn't an underdog story. It's the default outcome.
What SEO is for one person
Forget the enterprise version of SEO. You're not building a content team. For a solo founder, SEO is one thing: turning work you already do into a permanent acquisition channel.
Every support question you answer is a page someone else is searching for right now. Every integration you build is a "how to connect X and Y" query with real intent behind it.
Your changelog can rank.
Your comparison pages can rank.
Your setup guides pull people in before they're ready to buy, so that when they are ready, you're already the name they know.
None of this requires talent for writing. It requires noticing that the answers you give in Discord and email are the same answers thousands of people are typing into a search bar.
The reason this matters more than a launch is the shape of the return. A Product Hunt day gives you a spike and a hangover.
A ranked article gives you a trickle that never stops. One is an event. The other is an asset.
Publish a hundred of them, and you own a piece of ground competitors have to spend years to take from you.
Search traffic keeps arriving while you sleep, while you're heads-down on the next feature, while X changes its algorithm again and cuts your reach in half overnight.
Anyone whose entire distribution lives on someone else's platform is renting an audience they don't control. SEO is the part you own.
It's also the cheapest customer you'll ever get. Someone searching "best invoicing tool for freelancers" has already decided they have the problem and they're looking for the solution. You don't have to interrupt them or convince them the problem exists. You just have to be there when they look.
AI didn't kill SEO. It raised the price of being ordinary.
The fashionable take is that AI search has made all of this pointless. I think the opposite is true, and I think the people repeating it haven't looked closely at how these systems actually work.
AI answer engines don't invent their answers. They pull from authoritative content on the open web and repackage it.
If your writing is the source, being cited is the new ranking, and firsthand experience is exactly what these models weight most heavily.
Indie founders have that experience by default. You've shipped the thing. You've hit the edge cases. You know why the obvious approach fails in the third week. That knowledge is rare, and it's hard to fake, which is precisely what makes it rank.
Here's the part that should change how you think about the next few years. AI has made building software dramatically easier. More people can ship a working product this month than at any point in history.
When building gets easy, building stops being the moat. Distribution becomes the moat. And while everyone rushes to ship more products faster, almost nobody is doing the patient, compounding work of becoming the authoritative answer in their niche.
The bar for a product dropped. The bar for being found went up. That's a gap, and gaps are where solo founders win.
Start before you need it
The best time to start was when you wrote your first line of code. The second best time is this week.
You don't need a strategy or a content calendar or a fancy keyword tool with a subscription. You need to spend two or three hours a week writing down what you already know, aimed at the questions your users are already asking.
It will feel slow. It will feel like nothing is happening. Then one day a stranger shows up in your analytics from a post you forgot you wrote eighteen months ago, and then another, and the trickle becomes the most predictable channel you have.
Most indie developers will spend the next year polishing products nobody discovers. A few will spend a fraction of that time building a machine that brings people in long after the last feature ships.
The difference isn't talent. It's a willingness to do the work that doesn't feel like work.
