I Wrote 138 Blog Posts in Six Months. Here's What Actually Worked.
This is post 139. The previous 138 went up over about six months, which is roughly one every working day. I want to be honest about what that produced, because the "publish a ton and win SEO" advice is everywhere and the reality is more lopsided than people admit.
The honest distribution
Most of the posts did nothing. That's not false modesty, it's just how a long tail works. A big chunk of them get a handful of visits a month, some get zero, and a few months from now I'll probably prune the deadweight.
Then there's a small group that carries everything. The setup guides for connecting specific tools to specific databases — the "Postgres MCP server for Cursor" type posts — those rank, because they match exactly what someone types into Google when they're mid-task and stuck. And a couple of opinion posts got shared around and brought in more qualified visitors in a week than the quiet ones did in a quarter.
If you'd told me up front which 15 posts would matter, I could have written 15 posts. But I couldn't have told you, and neither could you. That's the actual argument for volume, and it's not the argument people make.
Volume isn't a strategy, it's a search
The pitch for content volume is usually "more posts, more keywords, more traffic, it compounds." That framing makes it sound like every post is a brick in a wall. It's not. Most posts are lottery tickets, and the volume is how you afford enough tickets to hit.
The useful reframe: you are not building a library, you are running a search. Each post is a probe into "does anyone want this." Publishing a lot is how you find the few topics that have real pull, fast, without guessing. The posts that hit then tell you what to write more of. I learned more about what my audience actually searches for from two months of publishing than from any amount of keyword-tool planning beforehand.
What I'd actually keep
If I did it again, I'd still write a lot, but I'd be more deliberate about the split.
The setup and how-to posts are worth it even when individually small, because together they cover the long tail of "how do I connect X to Y," and that's exactly the moment someone is looking for a tool like mine. They're not glamorous. They convert.
The opinion posts are worth it for a completely different reason: they're the only ones anyone shares. Nobody forwards a setup guide to a coworker. People forward "your data team is a ticket queue" because it puts words to something they already felt. Those posts don't rank for much, but they travel, and traveling reaches people search never will.
What I'd cut is the muddy middle. The generic "5 SQL tips" posts that are too broad to rank and too dull to share. They felt productive to write and did neither job. If a post isn't precise enough to win a specific search or spicy enough to get shared, it's probably not earning its slot.
The part nobody tells you
Writing 138 posts is mostly a question of not stopping. The quality bar matters, but consistency matters more than any single post being great, because you're running a search and the search needs samples. The hard part wasn't writing well. It was writing post 70 with the same care as post 7, on a day when the last ten posts got no traffic and the feedback loop was telling me to quit.
That's the real cost, and it's why most people who start this don't finish. Not because they can't write. Because the payoff is backloaded and lumpy, and you have to keep going through the flat part on faith that a few of these tickets are going to hit.
A lot of them did. Just not the ones I expected, which is the whole lesson.