Skip to content
Codivine
Content

Why Random Blog Posts Don’t Work

The difference between publishing and having a content strategy, why unconnected posts fail, and how to fix a blog that’s already a graveyard.

Marta Szymczak3 min read

Most business blogs are a list of unrelated posts published whenever someone had time. They get almost no traffic, generate no enquiries, and eventually stop.

The problem isn’t effort. It’s that unconnected posts don’t accumulate into anything.

What "random" looks like in practice

  • A post about an industry event you attended.
  • A "top 10 trends" piece written from other people’s articles.
  • Something about company culture.
  • A product announcement.
  • A seasonal greeting.
  • Six months of nothing.
  • A post about AI, because everyone is writing about AI.

Each may be individually fine. Together they’re not a strategy, and they build nothing.

Why it fails

Nobody searches for it. Company news, event attendance and generic trend pieces have essentially no search demand. The audience is people who already know you — who are not the people you need to reach.

No page builds authority. Search engines assess topical authority across a site. Twenty posts on twenty subjects say you’re an expert in nothing. Twenty posts on four subjects say something quite different.

No internal linking. Unrelated posts have nothing to link to. Every article sits alone, carrying no authority anywhere.

No commercial connection. If an article doesn’t lead towards something you sell, even a reader who loved it has nowhere to go.

No compounding. Good content strategy compounds — each new piece strengthens the ones before it. Random posts start from zero every time.

What to do with the blog you already have

Don’t delete everything. Audit it.

1. Export every post with its traffic. Search Console, twelve months, impressions and clicks per URL.

2. Sort into four piles:

  • Working. Getting impressions for something relevant. Leave alone, then improve.
  • Nearly working. Relevant topic, but thin or outdated. These are your best opportunities — updating an existing page is faster than starting fresh.
  • Irrelevant but harmless. Company news, event posts. Leave them; they’re not doing damage.
  • Actively unhelpful. Thin, duplicated, or embarrassing. Merge or remove.

3. Find your accidental clusters. You probably have three or four posts circling the same subject already. Link them to each other and to the relevant service page. That takes an afternoon and is often the highest-return content work available.

4. Pick one topic to own. The one closest to your most profitable service. Plan five articles around it. Publish them over two months, linked properly.

That’s a cluster, and it will outperform the previous three years of the blog.

The rule that prevents relapse

Before writing anything, answer two questions:

  1. What would someone type into a search engine to find this?
  2. Which page that we sell from does this article lead towards?

If you can’t answer both, don’t write it. Publish it on LinkedIn instead — that’s the right home for company news, and it costs your site nothing.

What about content for existing customers?

Genuinely useful, and it’s a different job. Onboarding guides, release notes, how-tos. Keep them, ideally in a documentation or help section rather than in the blog that’s doing acquisition work.

Mixing the two is how a blog ends up serving neither audience.

The honest timeline

If you start doing this today, expect months rather than weeks before it shows. New articles take three to six months to settle; updates to existing pages can move faster.

That’s slow enough that most businesses give up at month three — which is precisely why the ones that don’t end up owning their topic.

If you’d rather hand the whole loop to someone — research, planning, writing, publishing, linking and updating — that’s what we do. And if you just want an opinion on the blog you already have, send us the URL.

Marta Szymczak

Sales & Key Account Manager

Your point of contact for everything commercial — scope, communication and making sure the project matches what the business actually needs.

More about the team

Want help with this?

This is the kind of work we do. These pages explain how.

Got a version of this problem?

Describe it in your own words. We'll tell you what we'd do about it — and whether it's worth doing at all.

No specification needed. A description of the problem is enough to start.