How Long Should a Blog Post Be in 2026

I have about 2,000 articles across Medium and Substack. Some are 500 words. Some are 3,500. A few crossed the 5,000-word mark because I thought thoroughness equaled value.

It doesn't.

How long should a blog post be? That question has followed writers around for years, and the answer keeps shifting. Not because the rules changed. Because readers did.

The Honest Answer

There isn't a magic number. But there's a range that works better than others, and it's probably shorter than what most writing advice tells you.

For opinion pieces, personal essays, and takes on trends, 800 to 1,200 words tends to be the sweet spot. Long enough to make a point. Short enough that people actually finish reading.

For tutorials, SEO guides, and how-to content, longer works. 1,500 to 2,500 words. Sometimes more. Because the reader came for the steps, and cutting steps would be doing them a disservice.

The standard SEO advice has always been the same: longer is better. And for a while, that was mostly true. Google rewarded comprehensive content. Word count was a proxy for depth.

But 2026 is different. Google's algorithms got smarter about distinguishing depth from padding. And readers got less patient with articles that take 3,000 words to say what 900 words could handle.

What My Own Stats Say

I went through my last 100 or so Medium stories. Roughly. Looking at read ratios, claps, engagement relative to views.

Articles under 1,000 words had higher read ratios on average. Not always. But consistently enough to notice.

Articles over 2,000 words performed better in total views when they hit. The keyword there is "when." They hit less often. And when they missed, they really missed. Low read ratios, high bounce rates, mediocre engagement.

On Substack, the pattern was similar but shifted toward shorter. Newsletter emails especially. Nobody wants a 3,000-word email dropping into their inbox on a Tuesday morning. I don't want that. You don't want that.

The pieces that got the most replies, the most shares, the most "this was exactly what I needed" feedback? Mostly between 800 and 1,200 words.

That's not a universal truth. That's my experience across about 2,000 articles. Take it for what it is.

One thing I noticed: the topic matters more than the length. A 600-word personal essay about a specific experience outperformed a 2,200-word general guide on the same subject. The short one had a voice. The long one had sections. Readers chose the voice.

That happened enough times to change how I think about drafts.

Why Writers Default to Long

There are good reasons to write long. And then there are the real reasons most of us write long.

The good reasons: some topics need depth. You can't explain how Substack SEO works in 600 words. I tried. It ended up being one of my longer pieces for a reason.

The "real" reasons are less flattering. We think longer equals more valuable. We pad sections because the draft feels "thin." We add a third example when two already made the point. We write an entire paragraph explaining why something matters when the reader already knows it matters because they clicked on the article.

I've done all of that. Many times.

There's also this old Medium belief that longer stories earn more because read time affects Partner Program earnings. That may have been true at some point. I'm not sure it still is. And even if it is, an article nobody finishes doesn't earn much regardless of word count.

Then there's the comparison trap. You see someone publish a 4,000-word deep dive that gets 50,000 views, and you think "that's what works." What you don't see is the twenty 4,000-word articles they published that got 200 views each. Survivorship bias is real in the writing world.

Too short is also problematic. A 300-word post about a complex topic feels lazy, not focused. There's a floor. I'd say it's somewhere around 600 words for most topics. Below that, you're probably writing a social media post, not a blog article.

How to Figure Out Your Ideal Length

Instead of treating article length as a general question, ask it per article. Before you write.

One question helps more than anything: what's the ONE point of this piece?

If you can state it in a sentence, you probably don't need 2,000 words to make it. If you can't state it in a sentence, you probably need to think more before you start writing.

For a tutorial on setting up Google Search Console, the point is "here are the steps." That needs length. Each step is a section.

For a piece like "shorter articles perform better," the point fits in the title. It needs enough words to make the case and share some evidence. Not 3,000 words. Not 500 either.

Having a content strategy helps here. When you plan ahead, you know what each piece needs to accomplish. Less wandering. More focus. Fewer 2,500-word drafts that should have been 1,000.

I also keep a running list of article ideas with estimated lengths. "Opinion on new Medium feature, 800 words." "Full guide to cross-posting, 2,000 words." It sounds mechanical, but it prevents the thing where you sit down to write a quick take and emerge three hours later with 3,500 words on a topic that didn't need them.

What Padding Actually Looks Like

I've gotten better at spotting it in my own drafts. It usually shows up as:

A third example when two already made the point.

A section that restates the introduction in slightly different words.

Qualifying statements that add nothing. ("It goes without saying that..." Then why are you saying it?)

An entire closing section that summarizes what the reader just read. They just read it. They know.

Cutting padding is a skill. It's not about writing less. It's about recognizing when you've already made the point and moving on. That's harder than it sounds, because padding often feels like thoroughness when you're the one writing it.

One thing that helps: writing faster. When you write quickly, you tend to write more directly. The padding creeps in during slow, overthinking sessions where you feel the need to fill space.

Another trick: read your draft out loud. If you start getting bored with your own words, the reader already bounced. That's your signal to cut.

I've also started asking myself after each section: "Does this earn its space?" If I can remove it and the article still makes sense, it probably wasn't essential. That question alone cut about 20% from my recent drafts.

The SEO Angle

SEO is where the "how long should a blog post be" question gets complicated.

Google still likes comprehensive content. A 500-word post about a broad topic won't rank for much. That's true.

But comprehensive doesn't mean long. It means complete. An 1,100-word article that fully answers the question can outrank a 3,000-word article that buries the answer in padding and tangents.

Google's helpful content updates have been pushing in this direction. Content that answers the query well, loads fast, keeps readers engaged. Not content that's long for the sake of ranking signals.

For Medium SEO specifically, this matters even more. Medium articles don't get the same on-page SEO control as a self-hosted blog. Your content has to do the heavy lifting. And content that gets read to the end sends better signals than content that gets abandoned at the 40% mark.

My approach now: I write until the topic is covered. If that's 800 words, great. If it's 2,000, fine. But I don't stretch to hit a word count target. Ever.

One more thing about SEO and length. Internal linking matters more than word count for ranking. A 1,200-word article that's well-connected to other relevant content on your site can outperform a 3,000-word orphan page. Structure and context beat raw length.

Platform Differences

Where you publish matters for ideal length.

Medium: 800 to 1,500 words works best for most topics. The read ratio metric is visible, and shorter pieces consistently score higher there. Listicles and opinion pieces can be even shorter. Tutorials and guides can go longer.

Substack: Similar range for newsletter posts. But web-only posts (the ones you publish without emailing subscribers) can run longer because readers choose to visit. They're not getting a long email they didn't expect.

Your own blog: This is where longer SEO content makes the most sense. Blog posts live forever. They get search traffic for years. A 2,000-word guide that ranks well is an asset. But even here, padding hurts. Google can tell.

Social media teasers: Obviously short. But the article they link to doesn't need to be a novel either.

The platform context matters because a lot of writers ask how long should a blog post be without considering where it's going. A 2,000-word article is fine for a self-hosted blog. The same article as a Substack email might lose half the readers before they scroll past the fold.

Match the length to the platform. Not the other way around.

The Downsides of Going Short

Shorter articles are harder to monetize on Medium. Read time still factors into earnings somehow. A 3-minute read pays less than a 7-minute read if both get similar engagement. I think.

They're also harder to rank for competitive keywords. If you're targeting a broad search term, a 900-word piece probably won't beat a well-written 2,000-word guide. For competitive SEO, length still matters.

There's a perception issue too. Some readers equate length with effort. A short article can feel "light" even when it took the same amount of thinking and editing. Maybe even more editing. Cutting is hard.

And not every idea fits in 800 words. Some of my favorite pieces are longer because the topic demanded it. Forcing those into a shorter format would have made them worse.

There's also the consistency angle. If you publish shorter pieces, you can publish more often. And frequency matters for audience building. One 800-word article per week for a year is 52 articles. One 3,000-word article per month is 12. The writer with 52 articles has more surface area, more chances to be discovered, more opportunities to find what resonates.

That math doesn't mean shorter is always the move. But it's worth considering when you're deciding where to invest your writing time.

The point isn't "always write short." The point is "stop defaulting to long."

A Simple Framework

Here's what I do now. It's not complicated.

Before writing, I state the one point in a sentence. Then I estimate: is this a 800-word point or a 2,000-word point?

Opinion pieces and personal takes: 800 to 1,200 words.

How-to guides and tutorials: 1,500 to 2,500 words.

Comparisons and reviews: 1,200 to 2,000 words.

Newsletter emails: Under 1,000 words. Usually closer to 700.

After the first draft, I look for padding. Third examples. Restated introductions. Sections that don't earn their space. I cut them. Tools like WriteStack* can help with the publishing workflow, but the editing eye is something you build over time.

If you're planning content across multiple formats and platforms, a system helps. I use Superwriter to plan and track what I'm writing, which keeps individual pieces focused instead of trying to cram every idea into one article.

The question "how long should a blog post be" doesn't have one answer. But the instinct to write longer than necessary is almost universal among writers. Myself included.

The Bottom Line

Word count is not a quality signal.

More words don't mean more value. They often mean less focus, more padding, and a reader who leaves halfway through.

The best compliment I get on a story isn't "that was detailed." It's "that was exactly what I needed."

That usually comes from the shorter ones.

A writer is nothing without a reader. If you found this helpful, consider becoming my dear email friend. Nothing would make me happier.