How Many Words Should a Web Page Have? Google Says There Is No Number

Stop counting the words on your website. The 300-word minimum that turns your SEO plugin's light green, the "thin content" warning in an audit report a stranger emailed you, the 1,500-word target someone swore by at a networking breakfast: none of those numbers come from Google. And padding your pages to reach them quietly costs you the customers who were already reading.

That is a strong claim, so let me earn it. The word-count question comes up in my conversations with business owners more than almost anything else about their websites. Usually it arrives with a bit of guilt attached, as if a short page were a sign of laziness. It is not. A short page that answers the right questions is doing its job. The long page that hides them is not.

Google Has Put It in Writing, Twice

You do not have to take my word for any of this. Google has answered the question directly, in two of its own documents.

Its guide to creating helpful, reliable, people-first content ^[1] includes a list of warning signs that a page is being written for search engines rather than for people. One of them asks whether you are writing to a particular word count because you have heard or read that Google has a preferred one. The answer sits right there in brackets: "No, we don't."

The SEO Starter Guide ^[2] goes further. Under a heading about minimum or maximum content length, it says the length of the content alone does not matter for ranking purposes, that there is no magical word count target, minimum or maximum, and, with a straight face, that you probably want to have at least one word.

That is about as plain as Google gets.

So why does the 300-word rule refuse to die?

Where the Number Actually Comes From

Mostly, it comes from a plugin. Yoast SEO, one of the most widely installed SEO plugins for WordPress, runs a text length check that shows a red light when a standard post or page falls under 300 words, according to Yoast's own guidance on text length ^[3]. Cornerstone pages get a 900-word threshold. Product descriptions get 200.

To be fair to Yoast, the same page says plainly that word count is not a ranking factor in itself, and that adding more words alone will not make a page rank. The check is meant as a guideline. Trouble is, a traffic light does not read like a guideline. It reads like a fail. Owners see red, and owners fix red.

The other source is the audit report. You have probably had one land in your inbox: a free scan from someone you have never met, listing your "thin content" pages in alarming colours. Those tools count words because counting is easy to automate. Judging whether a page answers a customer's question is not.

Neither a plugin nor a scanner knows what your customers ring you to ask. You do.

What Padding Does to the Person Holding the Phone

This is the part that costs money.

Long pages are not read. They are scanned. The Nielsen Norman Group, which has studied web reading for decades, analysed tens of thousands of real page views and concluded that visitors have time to read at most 28% of the words on an average page, with something nearer 20% the more likely figure ^[4]. That research is old, the participants were above-average readers and it predates the smartphone era, so treat it as a rough shape rather than a precise measure.

The shape has not got kinder since. When the same group tested reading on phones in 2016, they found difficult passages took longer to read on mobile than on a computer, and they still advised prioritising brevity and cutting unnecessary content ^[5].

So every paragraph of filler does something specific. It pushes the answer the customer came for further down a small screen.

A stairlift page, rewritten for the wrong reader

Consider a hypothetical that will feel familiar to plenty of trades. A stairlift installer in Kildare gets an audit email warning that his curved stairlifts page is thin at 180 words. He takes it to heart. Over a weekend he grows it to 1,200: a history of the stairlift, a paragraph on independent living, three paragraphs on safety standards, a stock photo of a smiling couple.

The original 180 words said, near the top, that curved stairs are his speciality, gave a typical price range and promised a survey within a week. After the rewrite, those three facts sit somewhere below the second photo.

Now think about who searches for that page. Very often it is an adult son or daughter, on a phone, on a lunch break, trying to sort something out for a parent who has just come home from hospital. They want three answers. Can it be done on our stairs? Roughly what does it cost? How fast?

They scroll past the history, past the reassurance, past the stock photo, and give up before the price. The next result on Google has the price in its second line. That competitor gets the call.

Nobody tells you about the enquiry that never happened. There is no error message. It shows up as a quiet month.

Thin Content Means Something Is Missing, Not That It Is Short

Thin is a real idea in Google's world. It just is not a word count.

The same people-first guidance ^[1] asks a far better question than any plugin: does your content leave readers feeling they need to search again to get better information from other sources? A 150-word page that states the price, the area you cover, how long the job takes and how to book passes that test. Meanwhile, a 1,500-word page that never mentions a price fails it, however long it runs.

That gives you a more useful test than counting. Read your page as the customer would. Ask what they would still have to ring you, or search again, to find out. Whatever lands on that list is what the page is missing.

Where extra words genuinely help

This is the honest caveat, and it matters. Google's starter guide ^[2] adds a line that the 300-word crowd likes to quote out of context: if you vary your words naturally, you have more chances to show up in Search simply because you are using more of them.

That is true, and it is the only real case for length. If customers search for a stairlift for narrow curved stairs and your page never mentions narrow stairs, you will not match that search. Writing a paragraph about narrow stairs helps. But notice what helped. A new answer to a real question, which happened to add words. Not the words themselves.

Add answers. Never add filler. If the extra words would not help a customer decide, they will not help Google decide either.

When a Long Page Is the Right Page

I would be selling you something if I said short always wins. It does not.

Some decisions need detail. A solicitor explaining what a probate application involves, a financial adviser setting out pension options, an engineer describing what a structural survey covers: people facing those decisions want to read before they ring, and a 200-word page can feel like the firm is hiding something. Nielsen Norman made the same distinction in its mobile research, suggesting that anyone publishing high-complexity material in areas like finance or medicine test it with real users rather than follow a blanket rule about brevity ^[5].

Long works when it is organised. Google's own advice is to break long content into paragraphs and sections, with headings to help people navigate ^[2]. The customer who only wants the price should find it in seconds. Anyone who wants the detail should be able to keep reading.

Sometimes the honest answer to "does this page need more words?" is that you need more pages. One page trying to cover five services will be too long for every one of them. We made the case for splitting services out in our piece on why a one-page website gives Google exactly one page to rank.

How to Set the Right Length for Every Page

You do not need a target. You need a method. It works for a service page, a product page or a contact page, and it takes about twenty minutes per page.

1. List the questions. Write down the five or six things customers ask you on the phone about this service, in their words rather than yours.
2. Answer in order of urgency. Put the answers a customer needs to decide, such as price, area, timescale and how to book, in the first screen, and the nice-to-know detail lower down.
3. Cut what nobody asked. Delete any paragraph that does not answer a question on your list, even if it took you an evening to write.
4. Verify on a phone. Open the page on your own phone, on mobile data, and time how long it takes to find the price and the phone number.
5. Deploy, then measure. Push the new version to production, then watch which pages visitors arrive on and whether enquiries change over the following weeks.

If a page ends up at 140 words and answers everything, it is finished. A page that runs to 1,400 because the service is genuinely complicated is finished too. The number is an outcome, not a goal.

The home page deserves its own mention, because it has a different job. It has seconds, not minutes, to tell a visitor they are in the right place, which is why most small business sites fail the three-second home page test. Wording decides that one, not word count.

Why You Will Write a Better Page Than an Agency Would

There is a reason the person who answers the phone writes the best service page. They know the questions.

The old model ran the other way round. You briefed an agency, a copywriter who had never met one of your customers produced a polished 800 words to fill the template, and every later change went back through them as a billable request. Pages got long because long looked like value for money. All along, the answers customers wanted were in your head.

AI has flipped that order. A good AI website builder starts from your own description of the business, drafts every page, and hands you the keys to edit them yourself. You can see how that works by watching an AI builder write the first draft of a business website from a short description in under a minute. Then you sharpen it with the questions only you know customers ask. No agency and no plugin can do that part for you.

Because it is full WordPress, the platform behind roughly four in ten of all websites according to W3Techs ^[6], the editing never stops being yours. When a customer asks something new on Tuesday, the answer can be on the page by Tuesday evening.

The Speed Cost Nobody Counts

Padding rarely arrives as words alone. It brings company: the stock photo to break up the text, the embedded video, the image carousel that makes the page look fuller. Each of those adds weight, and weight costs load time, which is exactly what a customer on a patchy rural signal does not have.

A sensible hosting setup should absorb some of that cost. The criteria are simple enough. Pages should be served from a ready-made cached copy rather than rebuilt for every visitor. Repeated database lookups should be held in memory so busy pages do not grind. The server should be tuned for WordPress specifically, not shared out generically across every kind of site.

Web60 is built to that standard, with Nginx, FastCGI page caching and Redis object caching on Irish infrastructure. In practice, the customer who taps your result on a phone gets the page in front of them quickly enough to start reading, rather than staring at a blank screen and hitting back. All of it sits inside the €60 a year, with nightly backups and free SSL alongside.

Hosting cannot rescue a page that buries the answer, though. Fast delivery of the wrong 1,200 words is still the wrong 1,200 words. Cut first. Then let the infrastructure do its part.

Conclusion

Google has no word count target, and it has said so in writing. Your SEO plugin is counting, but even its makers say the count is not a ranking factor. The reader whose verdict matters is the one holding a phone, looking for a price and a reason to ring you.

Give every page one job: answer what that customer came to find, in the order they need it. Some pages will come out short and some will come out long, and both are fine. Pick your three busiest pages, run each through the five steps, and let the next month of enquiries tell you whether the new length is right.

Frequently Asked Questions

How many words should a web page have for SEO?

There is no target. Google's SEO Starter Guide says the length of content alone does not matter for ranking and that there is no magical word count, minimum or maximum. A page should be as long as it takes to answer the questions a visitor arrives with, clearly and in a sensible order. For a simple service that might be 150 words. For a complex professional service it might be well over 1,000.

Is 300 words enough for a page to rank on Google?

The 300-word figure comes from SEO plugin checks, not from Google. Yoast, for example, shows a red light below 300 words on a standard page, while also saying word count is not a ranking factor in itself. A shorter page can rank perfectly well if it is the best answer to the search. A page well over 300 words can fail if it does not answer the question.

Does Google penalise short pages or thin content?

Google does not penalise pages for being short. What its guidance warns against is content that leaves people needing to search again elsewhere, or content written to hit a word count. A short page that states your price, area, timescale and how to book is useful. A long page that never mentions those things is the one that falls short.

Should I ignore the red text length light in my SEO plugin?

Treat it as a prompt, not a verdict. When it goes red, read the page as a customer and ask whether anything they would need to know is missing. If something is, add it and the count will rise naturally. If nothing is missing, leave the page alone. Padding it just to turn the light green makes the page worse for the people reading it.

How long should a blog post be for a small business website?

As long as the question needs. A post explaining how to choose between two services might need 800 words. A detailed guide to a regulated process might need 2,000. Use headings and short paragraphs so a reader can skip to the part they need, and stop writing when the question is answered rather than when you hit a number.

Do longer pages load more slowly?

Words themselves add very little weight to a page. The slowdown usually comes from what gets added alongside them to fill space: large photos, image carousels and embedded videos. If you lengthen a page, keep an eye on those extras, and use hosting with proper page caching so the page reaches visitors quickly.

Sources