Thin Content: How Long Should a Service Page Be?

Someone told you your service pages are thin. So you did what every SEO blog says: you padded them. A 300-word page about drain cleaning became 1,500 words about the history of plumbing. Rankings did not move. You were solving the wrong problem.

Thin is not a length. Thin is a coverage failure. This post gives you an operational definition, a checklist you can run in ten minutes per page, and an honest answer to the other half of the panic: the near-identical city pages you have been told are a duplicate content penalty.

What actually counts as thin content?

A page is thin when it fails to answer the questions its target query implies — regardless of length. A 320-word page that names a fixed price, a two-day turnaround, the ZIP codes served, and the license number is not thin. A 1,800-word page that says 'we are passionate about quality service' fourteen different ways is.

Google's helpful content guidance asks whether a page provides 'a substantial, complete, or comprehensive description of the topic' and whether readers 'leave feeling they've learned enough about a topic to help achieve their goal.' Neither test mentions a number. Both are coverage tests.

The practical version: open the SERP for your keyword. Every question the top results answer that yours does not is a coverage gap. Stack up enough gaps and the page is thin — a searcher has to go somewhere else to finish the job.

How long should a service page be?

Long enough to cover the buying decision — for most US service businesses that lands between 600 and 1,200 words, but the range is an output, not a target. Google says it outright in its own guidance: 'Are you writing to a particular word count because you've heard or read that Google has a preferred word count? (No, we don't.)' That sentence sits in the list of warning signs you are writing search-engine-first content.

Word count correlates with rankings because thorough pages tend to be longer, not because length causes ranking. Copy the correlation without the cause and you get 1,500 words of filler. That is why so many 'we expanded the page' projects produce nothing.

Set the length by page type instead:

Notice the emergency page is the shortest and it is not thin. A panicking homeowner at 2am needs a phone number, a response window, and a price. Padding that page is actively harmful.

Which questions must a service page answer before it stops being thin?

Six entities decide it. If your page omits any of them, a buyer has to leave to find the answer — and that is the definition of incomplete coverage. Run this checklist against your page right now:

• Price range. A number or a bounded range with what changes it. 'Contact us for a quote' is a coverage gap, and buyers read it as a red flag.
• Process. What happens after they call, step by step, with who shows up and when.
• Timeline. How long the job takes and how soon you can start. 'Fast' is not a timeline.
• Service area. The actual towns and ZIP codes, plus what happens at the edge of them.
• Credentials. License number, insurance, manufacturer certifications, years in business — the specifics that make E-E-A-T real for a service business.
• Objections. The three things people worry about before booking, answered out loud: hidden fees, damage to the property, whether the warranty covers it.

Cover those six with real specifics and the page will land somewhere in the 600-1,200 range on its own. You never counted a word. That is the point. Our on-page approach for service pages builds the same skeleton in a different order.

Why does padding a 300-word page to 1,500 words change nothing?

Because you added zero new answers. The filler that gets bolted onto short service pages — company history, the importance of professional service, a generic FAQ that repeats the body copy — resolves none of the six entities. The page is exactly as incomplete at 1,500 words as it was at 300, only slower to read.

Google's self-assessment list asks whether content is 'mass-produced' and whether it provides 'substantial value when compared to other pages in search results.' Volume of text is not value. A padded page can score worse than the short one it replaced, because now the useful sentences are buried under 1,200 words of throat-clearing and users bounce faster.

If you are adding words and cannot name the specific buyer question each new paragraph answers, delete the paragraph. Cutting is a legitimate fix. A service page almost never suffers from having its fluff removed.

Are your eight near-identical city pages a duplicate content penalty?

No — there is no duplicate content penalty, and Google has said so since 2008. The Search Central post Demystifying the duplicate content penalty states: 'There's no such thing as a duplicate content penalty.' It adds that duplicate content on a site 'is not grounds for action on that site unless it appears that the intent of the duplicate content is to be deceptive and manipulate search engine results.'

What actually happens is duller and more expensive. Google clusters the near-identical URLs, picks one to represent the cluster, and consolidates the signals into it. Your seven other city pages get filtered out of results. No penalty, no manual action, no email — just seven pages that quietly do nothing while you pay to maintain them.

There is a second cost the same post names: crawl waste. Googlebot has to fetch all eight URLs before it can tell they are the same, which is time it is not spending on the pages you actually want indexed. If half your site sits in 'Crawled — currently not indexed,' that report is where the symptom shows up.

The fix is not a canonical tag. A rel=canonical annotation pointed at your main service page just formalizes the surrender — you are telling Google those city pages should not rank. If you want them to rank, they need genuinely different content, which is a build problem, not a tag problem. We cover the build in location pages for service-area businesses.

Where does the real risk live — doorway pages and scaled content?

Two named policies in Google's spam policies can actually get pages demoted or removed, and neither is called 'duplicate content.' Doorway abuse covers 'having multiple domain names or pages targeted at specific regions or cities that funnel users to one page' and 'creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy.' Scaled content abuse is 'when many pages are generated for the primary purpose of manipulating search rankings and not helping users.'

Read those definitions against your city pages honestly. Eight pages that are identical except for the city name, all funnelling to the same contact form, are the textbook example of doorway abuse — not because they are duplicates, but because they exist to catch queries rather than serve the person behind them.

The dividing line is whether the page has anything real to say about that place. Different crews, different drive times, different permit rules, different housing stock, different pricing — that is a legitimate page. City name swapped in eight places is not. The spam policy explicitly says scaled content abuse applies 'no matter how it's created,' so hand-writing the filler does not save you.

Our honest advice to most owners: run three real city pages instead of eight fake ones. If you cannot say anything specific about a town, do not publish a page for it.

How do you tell whether a page is thin or just unlucky?

Check impressions before you touch the copy. Three diagnoses look identical from the outside and have completely different fixes:

Only the first two rows are thin-content problems. Row three is a title-tag and meta-description job, not a content job. Rewriting body copy on rows three and four is wasted money — and it is the standard outcome when someone is hired to fix thin content site-wide without diagnosing it first.

One more honest caveat: a fresh domain with no links will sit at position 40 with a perfect page. That is an authority problem, not a coverage problem. Do not rewrite a good page because a new site is behaving like a new site.

What should you do this week?

Pull your top five service pages. Score each against the six entities — price, process, timeline, area, credentials, objections. Any page missing three or more is genuinely thin, and it is missing answers, not words. Fill the gaps with specifics only you can write, then stop. Do not add a single sentence you cannot attach to a buyer question.

If the eight-city-pages problem is yours and you would rather have someone else make the call on what to keep, cut, or consolidate, that is exactly what our SEO service starts with — a coverage audit before a single word gets rewritten. Get my free audit and we will tell you which of your pages are thin and which are just waiting on authority.