Building a separate page for every city you serve is standard local SEO advice, and it works — right up until the pages stop being different from each other. Then it stops working, and often does damage.
Why the Template Approach Breaks Down
The usual pattern is one well-written service page duplicated across twenty locations with the city name swapped in the title, the H1, and a handful of sentences. Ninety percent of the body text is identical.
Google has been explicit for years that this kind of thin, near-duplicate content adds no value. In practice the pages either fail to index at all, index but never rank, or compete with each other and with the parent service page.
How to Tell If Yours Are Too Thin
Two quick checks. First, open two of your location pages side by side and read them. If you could swap the city names and neither page would read strangely, they are templates rather than pages.
Second, check Search Console coverage. Location pages that are crawled but not indexed, or that show almost no impressions after several months live, are telling you something clear.
What Makes a Location Page Worth Indexing
The differentiator is information that only applies to that location. Depending on the business, that might be:
- Named neighbourhoods, landmarks and adjacent areas actually served
- Local regulations, permits, or requirements that differ by jurisdiction
- Travel time or service radius specifics
- Work completed in that area, described concretely
- Local pricing or availability differences where they genuinely exist
If you cannot write three hundred words that are true only of that location, the page probably should not exist as a separate URL.
Fewer, Better Pages
For most small businesses, five substantial location pages outperform thirty thin ones. Concentrating the effort also concentrates internal links and authority rather than spreading them across pages that individually rank for nothing.
Where a location genuinely matters to the business, treat it as a real page and give it real content — the way a proper service-area page should read.
What to Do With the Ones You Already Have
Do not mass-delete. Work out which pages have impressions or links, keep and improve those, and 301 the rest into the nearest meaningful page — usually the parent service page or a regional page that covers the area.
Redirect rather than remove, so whatever equity exists is preserved. Then check a month later whether the surviving pages picked up the impressions the removed ones were leaking.
Where Google Stands on Thin Local Pages
Google’s search essentials address scaled content abuse and thin affiliate-style pages directly, and the local business documentation sets out what genuinely helps a location page rank. The gap between those two documents is where most templated city pages sit.
Consolidation Is Usually the Right Move
Where pages are thin and duplicative, merging them into fewer substantial pages and redirecting the rest concentrates signals instead of splitting them. Search Console documentation covers how to monitor the effect of a consolidation, and it is worth measuring rather than assuming.
Our approach to service-area pages builds each one around information that is only true of that area.
The Trade-off Worth Understanding
There is a real argument for volume in some competitive local markets, and some businesses do rank thin pages, particularly in low-competition areas. But that tends to be fragile, and each core algorithm update puts it at risk. Building fewer pages that deserve to rank is slower and holds up better.
