At some point, I decided to test several hypotheses on a real project: whether organic traffic could be generated without an advertising budget, how far technical SEO could take a site, and whether articles would attract not only readers but clients as well.
The experiment exceeded my expectations. The site started receiving considerably more traffic than I anticipated, with almost no spending. The second part of the hypothesis was more interesting: readers arrived, but clients mostly did not.
What actually worked
The working combination was fairly simple:
- write for a specific search intent;
- cover the subject more deeply than most competing pages;
- keep the site technically healthy;
- connect related articles;
- avoid trying to purchase the result with advertising.
Search engines began bringing people to the articles. The hypothesis that meaningful organic traffic was possible without a significant budget was confirmed.
That is a useful result on its own. I did not build a theory from somebody else’s case study. I tested it on my own site and produced a working distribution channel.
Why traffic did not become clients
I made a fairly obvious product mistake: I optimized for attention without thinking enough about whose attention I was attracting.
Most articles covered networks, protocols, and censorship circumvention. People arrived with matching intent: configure something, choose a parameter, or ask a VPN-related question. The article solved their problem, but that did not mean they needed a product developer.
Traffic and demand for services are not the same thing. A useful article can solve a reader’s problem perfectly while giving them no reason to work with its author.
What I would do differently
I would separate three objectives earlier:
- Generate organic traffic.
- Show how I think and work as a developer.
- Give the right person a reason to contact me about a project.
Each objective needs different content. A technical deep dive works for search. A product story demonstrates a way of thinking. A review of decisions, constraints, and failures helps a team understand what working together might look like.
One article rarely solves all three jobs at once.
What comes next
I do not want the blog or channel to become a stream of “10 prompts that will change your life.”
I would rather write about:
- how AI can actually be used in development;
- what one person can build today;
- where AI shortens the path to a result;
- where it only creates the feeling of progress;
- how my projects evolve and what decisions appear along the way.
SEO is not going away. It is a useful distribution tool, and the experiment proved that I can make it work. But the subject matter will now begin with my real interests and experience, not only with existing search demand.
The main conclusion
Generating traffic is one engineering problem. Turning attention into trust and relevant opportunities is a product problem.
The first part of the experiment worked. I am rebuilding the second one now.