I Would Rather Publish 600 Useful Words

The problem with chasing 1,000+ words

I used to have a simple rule for publishing: if a post was under 1,000 words, it was not done. Longer meant more authoritative, more “in-depth,” more likely to rank. That was the story I told myself.

When I read back through those posts now, I can see the point where the useful part ends and the vanity metric begins. It is usually somewhere around the 500-word mark. After that, the signal drops and the padding starts.

The extra words were not extra depth. They were throat-clearing, bonus anecdotes, and slightly different ways of saying the same thing. The reader was paying with attention for my decision to optimize for a number instead of their time.

How the “SEO sweet spot” bent the writing

The “SEO sweet spot” is a neat story: Google likes 1,200–1,500 word posts, so if you want traffic, you should write 1,200–1,500 word posts. I believed it, so I engineered my structure to hit that range.

On paper, it worked. Traffic ticked up. The problem showed up one layer deeper. Engagement time per word went down. People were skimming, not reading.

Heatmaps made the pattern obvious. There was always a drop-off cliff in the same place: right after the article had actually answered the question. Everything after that was written for an algorithm, not a human being.

That is the trap with fixed word counts. You start from the number and build out, instead of starting from the idea and cutting back. You may get more visitors, but you train them to treat your work like something to mine, not something to read.

What changed: write the idea, then cut until it hurts

I eventually flipped the rule. Instead of “hit 1,000+ words,” it became: write the idea, then cut until it hurts.

The editing test is simple: if I can remove a sentence without breaking the logic chain, it goes. If the paragraph is only there to make the post feel more substantial, it goes. If an anecdote repeats a point I have already made, it goes, even if it is a good story.

What survives that process is usually around 500–700 words. Not because I am aiming for short, but because the fluff cannot defend itself. A 600-word post that survives this kind of editing is denser than a 1,300-word post that survives padding.

My best-performing post this year was about 580 words. It got more saves, more shares, and more return visits than any 1,500-word explainer I have written.

Word counts create fake “done” signals

There is a very particular satisfaction in watching a counter tick past 1,000. It feels like a level-up animation. You hit the target, so your brain labels the task complete.

The problem is that the counter is lying. I started noticing that many of my “finished” long posts were essentially extended introductions. I had spent hundreds of words setting context nobody asked for, then finally squeezed the actual argument into the last third.

Fixed word counts are good at one thing: creating the illusion of completion. They tell you that you have done enough, whether or not the reader has what they came for. The real question is simpler: can someone act on this, or think differently because of it? If the answer is yes at 450 words, then the post is finished at 450 words. If the answer is no at 1,800 words, then the post is not finished, it is just long.

The padding tax and reader trust

Padding is not free. There is a tax, and it is paid in reader trust.

When someone opens your article about a simple idea and sees a solid wall of text, they make a quick judgment: this is going to be work. If they push through and discover that the core idea could have fit on a single screen, they remember that too.

I was training my audience to expect bloat, which meant they stopped opening my emails. After switching to shorter, tighter pieces, my open rates climbed and unsubscribes dropped. The lesson was brutal: respect for a reader’s time compounds faster than keyword density.

Shorter posts expose fuzzy thinking

The dirty secret of padded writing is that it hides fuzzy thinking. If you are not sure what you believe yet, it is easy to wander around the topic for 1,200 words and hope the point emerges somewhere in the middle.

A 600-word limit removes that hiding place. You have to know your thesis, your supporting evidence, and your landing point before you start shaping sentences. The meandering draft still happens, but it stays in your notes, not in front of the reader.

The trade-off is simple: writing gets harder and reading gets easier. You spend more effort deciding what actually matters, and the path through the idea gets shorter and clearer.

If a paragraph cannot justify its existence, it does not get a spot. That pressure improves the thinking as much as the prose.

Measuring “insight per scroll” instead of length

I now think about posts in terms of “insight per scroll.” How much value does a reader get before they have to flick their finger again?

A useful 600-word piece delivers its core value quickly. A padded 1,300-word piece makes the reader work for the same reward. One respects that people have other things to do. The other assumes they are happy to sit through a monologue because you formatted it nicely.

My favorite compliment on an article is not “this is comprehensive.” It is “read this, it is quick.” That sentence means the sender trusts me not to waste their colleague’s time. It means the recipient is more likely to actually read the thing instead of parking it in a “later” folder that never gets opened.

I would rather be the writer people are glad they clicked than the one they keep meaning to get around to.

The new rule

The rule now is simple: I would rather publish 600 useful words than pad them to 1,300. I still draft long. I still wander in private. But what ships is the version where every paragraph has a job.

If the idea is done at 380 words, it goes out at 380. If it genuinely needs 2,000, it gets 2,000, but it has to fight for every line. The metric is no longer word count. The metric is whether someone can read the piece once and feel their time was well spent.

The internet does not need more long posts. It needs more finished ideas.