I published 100 articles in 13 days. Here is what it produced:
| Metric | Value |
|---|---|
| Articles published | 100 |
| Days | 13 |
| Reactions | 0 |
| Comments | 4 |
| Total page views | 820 |
| Median views per article | 10 |
| Articles with zero views | 43 |
| Best single article | 40 views |
Not a rounding error. Not a slow week. One hundred pieces of writing, thirteen days, zero reactions, and 43 of them were opened by literally nobody.
I want to write this down properly, because I think the mistake I made is a common one and it is easy to make quietly. Nobody tells you you're doing it wrong. The dashboard just stays flat and you keep publishing.
What I was actually optimizing for
I run four small products as a solo developer: a Next.js SaaS starter, a podcast metadata tool, an Etsy fee calculator, and a Shopify order-tracking app. My plan was simple. Each product has a set of keywords it should rank for. Dev.to has decent domain authority. So: write one article per product per day, rotate through four content angles, publish on a schedule, and let the volume compound.
Eight articles a day. Every day. For thirteen days.
On paper it looked like a content strategy. In practice it was a keyword coverage exercise, and I mistook coverage for usefulness.
The tell should have been obvious earlier: I was writing the same article five times and calling it five articles. When I go back through the titles by keyword, it breaks down like this:
- 26 articles about Shopify order tracking / WISMO
- 26 articles about Etsy fees and margins
- 24 articles about podcast metadata
- 24 articles about Next.js and edge deployment
Four topics. One hundred articles. That's twenty-five variations on each idea, published within two weeks, on the same account.
Why none of it worked
I've spent a few days pulling the data apart. Four things stand out.
1. The titles were all the same sentence
Twenty-five of the hundred started with "How I" or "Why I". Another twenty-five followed the "Building X: Taming Y" pattern. Four were "5 Best Practices" style listicles.
If you're scrolling a feed and you see "How I Built a Custom Shopify Tracking Widget" followed by "How I Built a Branded Shopify Tracking Widget From Scratch" followed by "Building a Custom Shopify Tracking Widget to Tame Post-Purchase Chaos" — you don't read any of them. You don't even register them as separate posts. Your brain files all three under "the same article, three times."
A title isn't a container for keywords. It's a promise about what the reader will learn. "How I built X" promises almost nothing, because everyone knows roughly how it went: you had an idea, you wrote some code, it worked out. There's no tension in it.
2. Every article was the same length, and it was the wrong length
The platform clocked 85 of the 100 articles at exactly 4 minutes. Five more at 3 minutes, ten at 5 minutes.
4 minutes is roughly 800-900 words. That's enough space to describe a problem and describe a solution. It is not enough space to show the actual engineering. There's no room for the failing test output, the diff that made it worse, the version of the fix I threw away. Without those, what's left is a summary of work — and summaries are what documentation is for.
3. I was writing for a search engine that wasn't reading
The whole bet was: publish enough keyword-shaped pages, and search traffic arrives. But a page with zero engagement doesn't get promoted by the platform, and a page with zero engagement also doesn't earn links, and without links it doesn't rank either. The volume strategy needs at least a few articles to break out and lift the rest. None broke out. So the entire pyramid sat on nothing.
Zero reactions across 100 articles is the platform telling me, politely and unambiguously, that it did not consider any of them worth distributing.
4. Nobody wants the fifth version of anything
This is the one that stings. Even if each article had been well-written, the fifth article about Etsy fee calculation published in the same week is not a new resource. It's noise. A reader who cared about Etsy fees would have read the first one. A reader who didn't care wouldn't read any of them.
I was competing with myself, and I won every time, and it was worth nothing.
The actual mistake
Here's the part I had to sit with for a while.
I wasn't writing articles. I was manufacturing ad slots and filling them with prose.
Every piece had the same shape: here's my product's problem space, here's roughly what I built, here's the link. The information was true. The code was real. But the purpose was placement, not explanation. And readers can smell that instantly, even if they can't articulate it. Nobody finishes an article and thinks "that was a well-targeted keyword" — they think "that taught me something" or they leave.
The other thing I got wrong: I assumed volume buys learning. It doesn't. Writing a hundred shallow articles taught me less about my own products than writing one deep one would have, because the shallow format forces you to stay at the level of summary. You never have to explain the thing that actually confused you, so you never work it out.
What I'm doing instead
I've stopped the daily schedule. The plan now is three articles a week, and the bar for each one is that it has to contain something a reader couldn't get from the docs:
- A real number from my own system — not a benchmark, an actual measurement
- A failure, with the error message and what it cost me
- A trade-off I had to make, and what I gave up
And the title has to describe a specific tension, not a category. "I published 100 articles and got zero reactions" is a title. "Content marketing best practices for indie developers" is not.
If that sounds like obvious advice, it is. I knew all of it thirteen days ago. What I didn't have was the discipline to apply it when the alternative was a publishing schedule that felt productive.
A question
If you've published at volume and watched it go nowhere, I'd genuinely like to know what the turning point was. Did you cut frequency, change format, change platform, or just keep going until something caught?
And if you're currently running a daily publishing schedule with flat engagement — how many articles in are you, and what would make you stop?
I'm not asking rhetorically. I'm at the beginning of the rebuild and I'd rather learn from someone who's further along than find out the same way again.
Top comments (0)