← Back to blog

I publish a blog, but I build my audience on LinkedIn. Here's why.

Three weeks after launching ivanpin.com, I checked the traffic sources. LinkedIn sent orders of magnitude more visits than organic search. The site was three weeks old — that's normal. Young domains don't rank. But I kept thinking: what happens when indexing stabilizes?

Then I framed the question more precisely. Say in six months, an article lands in Google's top 3. Good. But the search engine shows a featured snippet, and the reader gets the answer right there in the SERP. No click needed. They got what they wanted.

That's not a bug. It's how search engines work now. But it means search traffic is rented. A LinkedIn follower is owned.

Search organic is someone else's infrastructure

Vendor lock-in is a real thing in engineering. You tie yourself to one cloud provider without a fallback, the pricing or API changes, and you're stuck. That's bad architecture.

Content distribution is the same problem. Developers just don't usually apply the same thinking to it.

Organic search depends on:

  • Algorithms that change several times per year
  • Platform decisions about how to show results (Featured Snippets, Knowledge Panels, People Also Ask)
  • Competition in your niche that you can't control
  • Domain age — a new site waits months before it ranks

This doesn't mean SEO is useless. It means SEO isn't the channel to build your only audience entry point on. The same way cache warming through a single cron job without fallback is a bad idea for a 28,000-SKU catalog.

Search traffic is a bonus. A good, reliable, welcome bonus. But a bonus.

What direct contact gives you

When someone follows you on LinkedIn, they chose to receive your content in their feed. The algorithm can cut reach, but the connection is already there. A Telegram subscriber is even more direct — no algorithm, just a subscription.

Email is the most direct and the hardest to build. Grows slowly, but nobody can take it away.

In terms of control: email gives maximum closeness with minimum platform interference. Telegram is close to that. LinkedIn has wider reach but the algorithm has its own agenda.

For a technical author in 2022, the real audience lives on LinkedIn and Telegram. Not in RSS readers, not primarily on Twitter — on LinkedIn, where Russian-speaking engineers who've relocated to EU, US, Israel, and UAE read professional content in their native language. That's my target: that specific community.

ivanpin.com is the canonical long-form layer. It works as an SEO buffer and a CV link. LinkedIn is where the real-time contact happens.

How I structured distribution

The setup is simple: a full article goes to ivanpin.com as the canonical version. A shorter LinkedIn post goes out the same day. Telegram gets a more personal take — quicker, no academic framework.

This isn't a "multi-platform content strategy" in the marketing sense. It's an engineering call: don't put all state in one place, give each layer a job.

ivanpin.com — full text, RU + EN, SEO-optimized. An archive: for recruiters, for context, for profile links. LinkedIn — main reach channel, with EN-keyword formatting for the professional diaspora. Telegram — thinking out loud, testing ideas, more personal. Email I'm building slowly. When it exists, it'll be mine and nobody can deprecate it.

None of these channels depends entirely on SEO.

What to do with SEO

Don't throw it out.

Proper on-page SEO for an article takes 20–30 minutes: title, description, H2 structure, keyword distribution. Not expensive. And when organic traffic shows up in 3–6 months, it's a nice extra.

But SEO isn't a strategy. It's one layer. Like caching in an application: useful, but you can't build the only way to read data on top of it.

What I see a lot: write for keywords first, optimize for the algorithm, and think about the audience last. Then Google ships an update, traffic drops 40%, and suddenly the whole content channel was built on a foundation you don't own.

I write for the audience. I optimize for SEO along the way. I distribute through what I control.

Conclusion

Search traffic is rented. A LinkedIn follower, a Telegram reader, an email address — those are owned.

Any developer who adds a fallback to an external API already gets this. It's the same principle. The difference is that most people don't apply it to their content until after the traffic drop.

Developer personal brand isn't about going viral. It's architecture: who reads you, through what channel, and what stays with you when the algorithm changes. I wrote about a similar framing for engineering work itself — same principle, different layer.

I'm betting on LinkedIn. Not because LinkedIn is the best platform. Because that's where my audience is, and that's where I talk to them directly.