Target keyword: duplicate content city landing pages Secondary keywords: doorway pages seo, city landing pages, location pages duplicate content, multi city seo pages Suggested title tag: Avoiding Duplicate Content With One Landing Page Per City Suggested meta description: City landing pages built from a template risk being treated as doorway pages. How to build them so they rank instead of getting ignored. Suggested URL: /blog/avoiding-duplicate-content-city-landing-pages/ Schema: Article + FAQPage

---

Avoiding Duplicate Page Content When You Have One Landing Page Per City

Building a page for every city you serve is standard practice in local SEO, and it works, right up until the pages become near-identical copies of each other with the city name swapped in.

At that point they stop being an asset. They compete with each other, dilute the site, and in the worst cases attract the doorway page classification, which Google explicitly treats as low value regardless of how many you have built.

This is a technical problem with a content solution, which is why it catches out businesses treating it as a development task. It applies to any business doing local SEO across multiple locations, and becomes particularly acute for roofing companies covering several suburbs inside one metro, where the areas genuinely resemble each other.

What Google Considers a Doorway Page

The relevant question is not whether pages are literally identical. Most templated city pages are not, they differ by city name, perhaps a phone number, perhaps a map embed.

The question is whether each page provides genuine value specific to that location, or exists solely to capture a keyword variant. A page saying nothing a visitor could not have learned from the page for the neighbouring town falls into the second category, and containing a different place name does not change that.

 

The Cover-the-Name Test for City Pages

Cover the city name on one of your pages and hand it to someone. Could they tell you which city it is about?

If not, the page contains no genuinely local content, and no amount of technical adjustment will fix it. It is not a canonicalisation problem or an indexing problem, it is a content problem.

This test is uncomfortable to run on an existing set of city pages, which is why it is worth running.

 

What Makes a City Landing Page Genuinely Unique

Concretely, in rough order of value:

Completed work in that city: Photographs, project descriptions, and specifics from jobs actually done there, the approach behind each of our roofing city pages. No competitor can copy this and no template can produce it.

Reviews from customers in that city: Displayed on the relevant page, this is both distinct content and strong local proof.

Local specifics that actually affect the work: Housing stock and construction era, common property types, any recurring local issue, whether soil conditions, tree cover, a subdivision built in one year now reaching the same replacement point, or a local regulation affecting the trade.

Genuine service details for that area: Response times, whether the city is inside or outside a standard callout radius, which crews cover it.

References to real neighbourhoods and landmarks: Only where genuine, since inserting a list of neighbourhood names into otherwise identical text is exactly the pattern being described rather than a solution to it.

 

What City Pages Can Share Safely

Not everything needs to differ. Navigation, header, footer, contact information, brand messaging, and general service descriptions can reasonably appear across every page, and Google expects that.

The distinction is between shared structure and shared substance. A common template holding genuinely different content is fine. A common template holding cosmetically varied content is the problem.

A reasonable working target is that the genuinely unique portion should be the majority of the meaningful content, not a paragraph inserted into an otherwise identical body.

 

Why Canonical Tags Do Not Fix Thin City Pages

A common instinct when this problem is identified: canonicalise the city pages to a main services page.

This does not solve it, it eliminates the pages. A canonical tag tells Google to treat another page as authoritative, which means the city pages will not rank for the city searches they were built for. The problem is not that the pages exist, it is that they are thin, and the fix is making them substantial rather than hiding them.

 

How Many City Pages You Should Actually Build

Fewer pages, written properly, consistently outperform more pages produced from a template.

If you serve twenty cities and can write genuinely distinct content for six, build six. The remaining fourteen can be covered by a regional page listing the full service area, and built out individually as real work and reviews accumulate.

This is slower and produces better results, and avoids the situation where a site carrying twenty thin pages needs them removed later. It also explains a pattern businesses find baffling, showing up in one city but not the next despite having built pages for both.

 

Frequently Asked Questions About City Landing Pages

How different do city landing pages need to be?

Different enough that someone reading one without the city name could identify the location from the content alone. Cosmetic variation, a swapped town name and a different map embed, is not sufficient and rarely ranks, because the page offers a searcher nothing the neighbouring page did not. The page offers a searcher nothing the neighbouring page did not already provide.

 

Will Google penalise templated city pages?

Penalty is the wrong frame for what usually happens. More commonly the pages simply fail to rank, having been assessed as low value, which produces the same practical outcome without any manual action being taken against the site. The effort was spent and returned nothing. The effort was spent and returned nothing, which is arguably worse than a visible penalty.

 

Should city pages be canonicalised to a main services page?

No. That instruction tells Google to treat another page as authoritative, which means the city pages will not rank for the city searches they exist to capture. It eliminates the pages rather than fixing them. Improve the content instead, or remove pages you cannot make substantial. It eliminates the pages rather than fixing them, which is rarely what anyone intended.

 

Is it better to have fewer strong city pages or more weak ones?

Fewer, consistently. Weak pages dilute the site, rarely rank, and give visitors no reason to believe you actually know their area. Strong pages compound over time and more can be added as real work accumulates, which is a far better trajectory than pruning thin pages later. More can be added as real work accumulates, which is a better trajectory than pruning later.

 

What is a doorway page?

A page existing primarily to capture a keyword variant rather than to genuinely serve a visitor. Sets of near-identical location pages differing only by town name are the classic example in local SEO, and Google treats the pattern as low value regardless of how many you have built. Google treats the pattern as low value regardless of how many of them you have built.

 

Can I use AI to write city landing pages?

Only if you supply genuinely local input: real completed projects, real reviews, real detail about housing stock and local conditions. AI given nothing specific produces exactly the templated output that fails, simply at greater volume and lower cost, which makes the underlying problem worse rather than better. AI given nothing specific produces the templated output that fails, simply at greater volume.

 

How do I fix existing thin city pages?

Either add genuine local content, completed projects, photographs, reviews, and area specifics, or consolidate them into a single regional page covering the service area. Leaving thin pages live while building new ones simply repeats the original problem at larger scale. Leaving thin pages live while building new ones repeats the original problem at larger scale.

 

When should I build a page for a new city?

Once you have completed work there, ideally with photographs and at least one review from a customer in that area. Building ahead of the work is precisely what produces the thin page problem, since there is nothing genuine to write about and a template becomes the only option available. Building ahead of the work leaves a template as the only available option.

 

Build Them as You Earn Them

The most reliable way to avoid this problem is to let city pages follow the work rather than precede it.

A city where you have completed a dozen jobs, collected reviews, and photographed results has enough material for a genuinely distinct page, and writing it is straightforward because the substance already exists. A city where you have done nothing yet has no material, which is exactly why the template gets reached for.

Building pages ahead of the work is what creates the thin page problem. Building them as the work accumulates avoids it entirely, and produces pages both more convincing to a homeowner and more likely to rank.

We build city page structures around what a business can genuinely substantiate rather than around a list of target locations, which is how our own roofing pages are put together. Month to month, no lock-in, and rankings improve within 90 days or we keep working for free.

Book a free strategy call and we will run the cover-the-name test on your existing city pages.