TL;DR: 1000 words is the median dev.to article that compounds. Above 1500, dwell time drops. Below 600, search ignores it. I now stop at 1000 ± 200 even when I have more to say. Saves time, helps engagement, leaves room for follow-ups.
The data
After 60 days and 70 dev.to articles:
| Word count | Avg views (Day 1) | Avg views (Day 30) | Compound? |
|---|---|---|---|
| < 500 | 12 | 18 | No |
| 500-800 | 35 | 67 | Mild |
| 800-1200 | 58 | 134 | Yes |
| 1200-1800 | 71 | 156 | Yes |
| 1800-3000 | 68 | 142 | Plateau |
| > 3000 | 41 | 89 | Anti-compound (TLDR-skipped) |
The sweet spot is 1000-1500 words. Above 1800, articles get TLDR-ed. Below 800, Google ignores.
Why 1000 ± 200
1. dev.to readers skim
Avg reading time per article on dev.to is 2-3 min. 1000 words = 4 min reading. Already pushing the limit.
2. Google likes substantive but not bloated
1000 words is enough to rank for medium-tail keywords. 3000 words is enough to rank for short-tail but the dwell time data hurts you back.
3. Re-reads matter
Articles I keep coming back to are 1000 words. The 3000-word ones I bookmark and never re-read.
4. Follow-ups compound
3 articles of 1000 words each beat 1 article of 3000 words. Each follow-up gets its own URL, its own SEO, its own discussion.
How I enforce 1000 ± 200
1. Outline first, ~5 sections
- Hook (1 paragraph)
- Section A
- Section B
- Section C
- Closing + Source link
2. ~200 words per section
- 5 sections × 200 = 1000 words
3. If a section blows past 250 words
- Cut, or split into a follow-up article
4. After draft
- Read through, cut adjectives + transition phrases
- 95% of the time this gets me from 1100 to ~1000
Anti-pattern: kitchen sink
Don't:
- "I'm going to cover everything about X in one article"
- "By the end you'll know everything about Y"
- 3000-word "ultimate guide" articles
Do:
- "Here's the one thing about X that surprised me"
- "By the end you'll have a working Y skeleton"
- 1000-word "specific lesson" articles
The kitchen sink reads like a textbook. Indie content is best when it reads like a story or a tip.
What this lets me ship
In a 4-hour /autoiter session I can:
- Outline 5 articles (15 min)
- Write 5 first drafts (90 min, ~18 min each)
- Edit all 5 (60 min, ~12 min each)
- Publish 5 via API batch (4 min + rate limit waits)
That's 5 articles per ~3 hours. Sustainable for indie scale.
If I were writing 3000-word articles, I'd ship 1-2 per session. The compound is much weaker.
Source
The full /autoiter pattern + 60+ paste-ready 1000-word article examples:
AutoApp Dashboard ($39) — includes the article pacing template + dev.to API publisher.
If you write articles longer than 1500 words on average, you have a kitchen-sink-shaped problem. Stop at 1000. Let the follow-ups compound.
