We Published 600 Blog Posts Nobody Read. Here Is the Data.

We audited every post we'd ever published. Traffic, time-on-page, backlinks, conversions. The results were uncomfortable, and we think they're worth sharing.

What the Data Actually Showed

We pulled 24 months of Google Search Console data, cross-referenced it with GA4 session logs and Ahrefs' backlink index. The distribution was brutal.

The top 8% of posts drove 71% of organic traffic. The bottom 60% of posts received fewer than 50 sessions over their entire lifetime. Many had zero backlinks, no featured snippets, and ranked for keywords with monthly search volumes in the single digits.

We'd written about topics we found interesting. Topics we thought we were well-positioned to cover. Topics that felt timely when we published them. None of that correlated with traffic. The only things that did correlate: search volume, keyword difficulty relative to our domain authority (DR 28 at the time), and whether the post covered one specific, answerable question rather than a broad subject area.

The median post had 847 words. The top-performing posts averaged 1,640 words. That's not because length itself is a ranking signal. It's because the posts that answered narrower questions well happened to require more space to do it properly.

Why Do Most Technical Blog Posts Fail to Get Traffic?

There are a few structural reasons, and most of them are fixable before you write a single word.

Keyword targeting by intuition. Engineers write about what they know. What they know tends to be specialised. Specialised topics often have low search volume, and if the volume is there, the intent behind the searches is frequently informational in a way that doesn't match what the post actually does. A post titled "How We Architected Our Event-Driven Microservices System" is useful to exactly one kind of reader, at exactly one moment in their project. That's a narrow window.

Competing with established domains on their home turf. A DR 28 site should not be targeting "what is machine learning." The keyword difficulty on that phrase is above 80 in Ahrefs. You will not appear on page one. You'll appear on page seven, where nobody goes.

Publishing and forgetting. Content decays. Google's "freshness" signal isn't just about publication date. It's about whether a page is being updated, gaining links, and continuing to be clicked. A post published in 2021 with no updates and no new backlinks is a post actively losing ground.

No internal link structure. We had 600 posts sitting in relative isolation. A reader who landed on one had no obvious path to another. This hurts both time-on-site metrics and PageRank distribution.

What We Changed and What Actually Moved the Numbers

We ran the audit in Q3 2023 and started implementing changes immediately. Here's a honest account of what worked and what didn't.

Consolidation

We merged 74 posts that covered overlapping subtopics into 18 longer, more authoritative pieces. In each case, the surviving URL was whichever had the most existing backlinks. We 301-redirected everything else.

Within three months, 11 of those 18 consolidated posts had improved rankings. Average position improved by 6.3 places for consolidated posts versus 0.8 places for a control group of untouched posts over the same period.

Keyword-Led Brief Writing

We stopped writing posts and then figuring out what they were about. We started with Ahrefs keyword explorer, filtered for KD under 30 and volume above 200, and built a content calendar from that list. Every brief specified the target keyword, the secondary keywords, the search intent, and the word count derived from the average of the top five ranking results.

It felt mechanical at first. The output was better.

Topic Cluster Architecture

We picked eight core topics where we have genuine depth: custom software, AI integration, blockchain development, mobile apps, fintech, healthtech, edtech, and e-commerce systems. Every new post maps to one cluster. Each cluster has one pillar page that links out to all the supporting posts, and each supporting post links back to the pillar.

Metric	Pre-Cluster (Q3 2023)	Post-Cluster (Q1 2024)
Pages with >100 monthly sessions	31	67
Average session duration	1m 42s	2m 19s
Crawl depth (avg clicks from homepage)	4.7	3.1
Posts with at least 1 backlink	18%	29%

What Didn't Work

Publishing frequency. We tried increasing output from 4 posts/month to 10 posts/month for a 6-week period. Traffic didn't increase proportionally. The higher-frequency posts were thinner, ranked poorly, and created more consolidation work later. Quality per post matters more than volume.

We also tried repurposing posts as LinkedIn articles. Zero measurable impact on search traffic, minimal social engagement. LinkedIn's algorithm doesn't favour outbound links, so the posts got suppressed anyway.

How Should a Technical Company Think About Content ROI?

Content is a long-cycle investment. The average age of a top-10 Google result is over two years, according to an Ahrefs study of two billion pages. You're not competing for this month's traffic. You're building an asset that compounds.

That framing changes the resource allocation question. Spending 12 hours on one well-researched, well-targeted post beats spending 12 hours on four thin ones. The thin posts dilute your crawl budget, fragment your authority, and eventually need to be cleaned up anyway.

The honest trade-off: this approach is slower. If you need traffic in 30 days, content is the wrong channel. Paid search is the right channel. Content starts paying out at the 6-12 month mark for a domain in the DR 20-40 range, assuming consistent publishing and active link acquisition.

Conclusion

If your blog looks like ours did in 2022, the fix isn't writing more. It's auditing what you have, cutting or consolidating the dead weight, and building a tight cluster architecture before publishing anything new.

Start with a Search Console export filtered to pages with fewer than 10 clicks in the last 12 months. That list is your problem. Decide for each post: consolidate, update, or delete. Then build your content calendar from keyword research, not from topic ideas.

The 600 posts taught us something useful. It just took a while to read the lesson correctly.

---

FAQ

How long does it take to see results after consolidating old blog posts? Expect 6-12 weeks before rankings shift meaningfully after a consolidation and 301 redirect. Google needs to recrawl and reprocess the pages. In our case, 11 of 18 consolidated posts showed ranking improvements within three months. Results vary with domain authority and how competitive the target keywords are.

What keyword difficulty should a domain with DR under 40 target? Keep keyword difficulty below 30-35 in Ahrefs for most posts. At that range, you can rank on topical authority and content quality without needing hundreds of referring domains. For pillar pages where you're actively building links, you can push to KD 40-45. Anything above 50 is likely a waste of effort at sub-DR 40.

Is it better to update an old post or write a new one on the same topic? Update the old one if it has any backlinks, indexed age, or existing impressions in Search Console. A post with two years of history and a handful of backlinks starts with a significant advantage over a blank URL. Only write fresh when the old post is so structurally different that rewriting it would be faster than editing.

Does publishing frequency matter for SEO? Less than most people assume. Consistency matters more than volume. Google's crawl budget allocation does respond to regular publishing, but publishing thin content to increase frequency actively harms you. Four well-researched posts a month outperforms ten shallow ones, both in rankings and in the consolidation debt you avoid creating.

How do you measure whether a blog post is actually working? Track three things: organic sessions from Search Console (not GA4, which undercounts), average position for the target keyword, and whether the post appears in any featured snippets or People Also Ask boxes. Conversions from content are hard to attribute directly. If you need a proxy, track email signups or demo requests from users whose first session was a blog page.

Have a project in mind? Contact Sodio Technologies to discuss your requirements and explore the right technology solution for your business.