How Long Should a Blog Post Be? Why Google Has No Ideal Word Count

Almost every writer asks the same thing before starting a post: how many words do I need? Search for it and you will find confident numbers, usually presented as the length that "ranks". Those come from third parties and describe what some pages look like, not what Google asks for.

So how long should a blog post be? Long enough to finish the job the reader came for, and no longer. That is a method, not a dodge: decide the length from the question, not from a number. This guide is for bloggers, small business owners and editors who want a defensible way to size every post and a routine for cutting padding. You will finish with a planning worksheet, a set of tests for "is this long enough?", an edit pass for removing filler, and a clear picture of what Google does and does not say about length.

Short answer: Google says there is no preferred word count and that content length alone does not matter for ranking. Write as many words as the reader's question needs. A simple definition may take a few hundred words; a how-to with steps, examples and cautions may take far more. Judge length by completeness and clarity, not by a number.

Before you begin

You need the working title or question for the post, a note of who it is for, and a list of the points a reader must come away with. If the post targets a topic already covered on your site, open that page too. Search Console helps if the site has been live for a while, because it shows which queries a page already receives; see Read the Search Console Performance Report: Clicks, CTR and Position. Allow thirty minutes to plan and a little time after drafting to cut. If you are editing a live post, keep a copy of the old version.

What does Google say about blog post length?

Two Google pages answer this directly.

The helpful content guidance lists writing to a particular word count among the signs of content written for search engines first, and asks: "Are you writing to a particular word count because you've heard or read that Google has a preferred word count?" The answer given is no, Google does not have one.
The SEO starter guide says in its list of things not to focus on that the length of content alone does not matter for ranking purposes, and that there is no word count target, minimum or maximum, though a page should have at least some words.

The same helpful content page asks questions that are about substance: does the content give a substantial, complete or comprehensive description of the topic? Does it offer more value than other pages in the results? Do readers have to go back to search again to find better information? Those questions are where length comes from. A post that fully answers a broad question will be longer than one that answers a narrow question. That is a consequence of the topic, not a target.

None of this predicts what a page will earn. Google's overview of how Search works says it does not promise to crawl, index or show any page.

Why do word-count studies mislead?

Surveys of top results often report that the pages shown are fairly long. That may simply mean pages for broad questions need detail. It does not show that adding words made them appear, and it says nothing about your question. An average also hides short pages that appear too, and copying it encourages padding. We quote no study here, because none of the Google pages we read relies on one.

Step-by-step instructions

Step 1: State the question and the reader's job

Write the question in one line, then write what the reader should be able to do or know afterward. "What is a canonical tag?" ends with a definition and one example. "How do I move my blog to a new domain?" ends with a checklist the reader can work through. The job decides the shape. If you are unsure what searchers expect, look at the search results themselves, as described in Search Intent: How to Match Each Page to What Searchers Want.

What success looks like: A sentence of the form "After reading, the reader can ___".

Step 2: List what the reader must get

Write a bullet list of every point a reader needs to succeed: the answer, the steps, the warnings, a worked example, the situations where the answer changes. Mark each point as must have, useful or nice to have. The must-haves define the minimum length of an honest post; the rest are optional. This list replaces a word-count target.

What success looks like: A short list of must-haves that any reader would miss if it were absent.

Step 3: Compare with what already exists, for gaps and not for length

Search the question and read three or four of the pages that appear. Do not count words. Note what each covers, what it gets wrong, what it leaves out and what you can add from your own experience, data or photos. Google's helpful content questions ask whether your page adds value beyond what others say and does not simply rewrite them. Your plan should include at least one thing a reader cannot get from the pages you read.

What success looks like: A written note of two or three gaps your post will fill.

Step 4: Build an outline and give each section a purpose

Turn the must-haves into headings, preferably as questions a reader would ask, and set a rough size per section. This is a planning tool for you, not a number for Google. Example for a post on example.com, "How do I change a bike tyre?":

Section	Purpose	Rough size
Intro and short answer	Say it takes about the same tools and one flat tyre	100 words
Tools you need	List with one line on each	80 words
Steps 1 to 6	One short paragraph and a result check per step	450 words
Common mistakes	Pinched tube, wrong pressure, missed debris	200 words
FAQ	Four real questions	200 words

The total is about 1,000 words because the job needs it. If the same post were "What is a tubeless tyre?", the outline would be much shorter.

What success looks like: Every heading has a purpose, and no section exists only to add bulk.

Step 5: Write until the job is done, then stop

Draft without watching the count. State the answer early, keep paragraphs short and add detail only where a reader would otherwise get stuck. The W3C Web Accessibility Initiative also recommends short sentences and common words, which make a longer post easier to scan. Use lists and tables where they replace prose. How to write the answer itself is covered in SEO Copywriting: How to Write Pages That Answer the Search Query.

What success looks like: The post covers every must-have and ends when the last one is covered.

Step 6: Cut the padding

Read the draft once with a single question: would a reader miss this? Remove or rewrite anything they would not.

Padding pattern	Fix
A long opening about why the topic matters	Delete it, or reduce it to one sentence before the answer
Restating the question before answering	Start with the answer
The same point made again in a conclusion	Keep a short checklist at most
Synonym piles ("quick, fast and speedy")	Pick one word
Generic advice that fits any topic	Replace it with a specific detail or cut
Repeated keyword phrases	Rewrite in natural language; repetition is keyword stuffing, which Google's spam policies name
Sections created to "cover a keyword"	Merge into the post that answers it or delete

Padding also appears as extra pages. If you have several short posts on near-identical questions, merge them as described in Thin Content and Duplicate Pages: How to Find and Fix Them.

What success looks like: The edited draft is shorter and more useful, with no loss of must-haves.

Step 7: Test the length by outcome

Check the finished post against four tests instead of a word count:

Completeness: can the reader finish the job from this page alone?
Return-to-search test: would they need to go back to search for something obvious that you left out?
Skim test: can someone find the answer in under a minute by reading headings and the first paragraph?
Duplication test: does another page on your site already answer this question?

If it passes all four, its length is right, whatever the number. Failing the first or second means adding material; the third, restructuring; the fourth, merging.

What success looks like: The post passes all four tests and you can name what each section is for.

Step 8: Revisit using real data

After the post has been live for a while, open Search Console and look at the queries and pages for it. If a post is not performing, look for an intent mismatch, a missing answer or an unclear title before adding words. Google lists changing page dates without substantial content changes as a warning sign, and says adding or removing large amounts of content only to seem fresh will not help. Update posts when facts change; see Content Pruning: Decide What to Update, Merge or Remove.

What success looks like: You change posts for a reason you can state, not to reach a number.

Is a short post bad for SEO?

No. Google's documentation says length alone does not matter for ranking, and the right length depends on the question. A short, accurate answer to a narrow question can be exactly right. A short page can be a problem only when it does not answer the question or has almost no content at all. Crawvix's thin-page check, for example, reports pages with almost no visible text (fewer than 100 characters), because those pages give the reader and the crawler nothing to work with. That is a very different thing from a concise post that does its job.

Is a long post better for SEO?

Not by itself. A long post can serve readers well when the topic is broad and each section earns its place. It can also bury the answer. The question for every long post is whether a reader can find the part they need quickly, which is why headings, a short answer near the top and a contents list on very long pages matter. Google's ranking systems guide also describes a system that can identify individual sections of a page, so a clear section can be useful even within a long post. Do not stretch a post to compete on size.

Final verification checklist

The post answers one clearly stated question, and the reader's job is written down.
Every must-have point from Step 2 appears in the post.
You compared existing pages for gaps and not for word counts.
Each heading has a purpose, and none was added only for volume.
The answer appears early, and the text uses short sentences and plain words.
Padding patterns were checked and cut.
The post passes the completeness, return-to-search, skim and duplication tests.
No promise is made about how a given length will perform in search.

Common mistakes to avoid

Copying a "best length" from a blog post. Third-party averages are not Google guidance. Use the question.
Padding to reach a target. Extra words dilute the answer. Cut them.
Cutting a post below what the job needs. If a reader must go elsewhere for an obvious step, the post is too short.
Splitting one topic across several thin posts. Merge them into one useful page, with redirects.
Burying the answer under a long introduction. Put it in the first paragraph.
Updating just to refresh dates. Change the content for a reason, or leave it.
Ignoring structure. A long post without headings, lists or a short answer is hard to use. Review Heading Structure for SEO: Use H1 to H6 for Meaning, Not Style.

Frequently asked questions

Is there a minimum word count for a blog post to be indexed?

Google's documentation names none. The starter guide says there is no minimum or maximum, though a page needs some words. Whether a page is indexed depends on many factors; see How Long Does Google Take to Index a Page?.

Do longer blog posts rank better?

Google says length alone does not matter for ranking. Pages that rank well are often detailed because the topics need detail, but adding words does not add quality.

Should a blog post be 1,000 words or 2,000 words?

Neither number is a rule. Plan from the must-haves for the question. A procedural guide with examples will usually be longer than a definition, and the outline will tell you which one you are writing.

What is a good length for a post that answers a simple question?

As short as the complete answer allows, often a few paragraphs plus an example. Add a short answer at the top and stop when the reader's question is answered.

Should I rewrite old short posts to make them longer?

Only if they are missing something readers need, or fail the completeness test. Otherwise consider merging near-duplicates or leaving a good short post alone. The review steps in Helpful Content Checklist: Review Your Pages Against Google's Advice help you decide.

Official references

Next step: Try the free website sample to see how your own site does on a few of these checks. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.