How to Manage Duplicate Content Across Location Pages

Open any contractor's site and you will find the pattern: "Plumber in Cedar Park," "Plumber in Georgetown," "Plumber in Leander," twenty pages of near-identical text with the city name swapped out. Some agency charged by the page for it. And then the owner wonders why only two of them get traffic, why none of them rank, and why the site feels like a house with too many empty rooms.

Here is what the research actually says, and it is better news than most guides admit. Google has no duplicate-content penalty, and John Mueller has said on the record that localized pages with largely similar content are generally fine (Search Engine Journal's coverage of his comments). The real danger is a different policy with a different name: doorway abuse, plus its younger sibling, scaled content abuse. If your city pages exist mainly to capture search traffic and offer nothing a resident of that city could not find elsewhere, that is the policy they trip. This guide gives you the contractor's decision framework for every page you own: keep, rewrite, merge, or delete.

The Real Risk Is Not A Penalty

Get this straight first, because it changes every decision below. There is no "duplicate content penalty" box that Google checks on your site. What exists is a set of spam policies, and two of them reach directly for templated city pages:

• Doorway abuse: pages created to rank for specific queries that funnel visitors to a single destination without offering unique value. A city page whose only content is swapped city names on the same 400 words is the textbook shape.
• Scaled content abuse: generating large numbers of pages primarily for search traffic rather than to help users. The fifty-page city blitz your last agency sold you lives here.

The distinction Google draws is not word count, it is substance. Two pages can say similar things about your drain cleaning service. What separates a legitimate city page from a doorway is whether a resident of that city finds something on the page that could only exist for their city. That is the entire game, and contractors are better positioned to win it than almost anyone, because your proof lives in trucks, techs, and jobs, not in adjectives.

Why Contractor Location Pages Go Wrong

The template problem starts innocently. An agency builds one good service page, clones it for every town in the service area, runs find-and-replace on the city name, and invoices per page. The result:

• Pages for towns the trucks rarely reach, with no jobs, no reviews, and no photos from that town.
• Local "facts" invented by a copywriter three states away, or worse, copy-pasted Wikipedia intros that belong to nobody.
• Site architectures where the city pages are orphaned: not linked from anywhere except a footer list, signaling to Google that even the site owner does not value them.
• Service-area sprawl, where a plumber based in one county claims thirty cities, some two hours out.

The fix is not better copywriting on the same architecture. It is fewer pages, each one anchored to proof. Walk through the framework below for every city page you have, and be honest about which ones your business could defend to an actual resident of that city.

The Keep, Rewrite, Merge, Delete Framework

Audit every location page against two questions: does it get traffic or links, and does it carry genuine local proof? The answers place each page in one quadrant:

• KEEP: the page has traffic or rankings AND real local substance. Leave it alone, keep improving it.
• REWRITE: the page ranks or could rank but reads like a template. Rebuild it with the proof stack below.
• MERGE: the page has thin content and no traffic, but the town is genuinely served. Fold it into the nearest strong page with a 301 redirect, and give the surviving page a section about that town.
• DELETE: the page has thin content, no traffic, no links, and the town is marginal. Remove it. A smaller site with real pages outranks a bigger site with empty rooms.

Run this in Search Console and Analytics: pull the last six months of traffic per city page, note which ones hold any rankings, then apply the verdicts. For merged pages, the 301 redirect passes the surviving page whatever equity existed, and consolidating weak pages into strong ones is one of the highest-ROI cleanup moves on a trades site. If a page is not showing up at all, our visibility troubleshooting guide helps you separate indexing problems from content problems first.

The Proof Stack That Makes Each Page Unique

A rewritten city page is not "the same template with more synonyms." It is a page that could only be about that city. Contractors have an unfair advantage here, because local proof is lying in your trucks and camera rolls. For every city page you keep or rewrite, stack as many of these as you genuinely have:

• Jobs completed in that city. Real numbers, real addresses kept private, real dates. "47 water heater installs in Cedar Park since 2023" is substance no template can fake.
• Named technicians and crew photos from local jobs. Faces and names beat stock photos for both trust and uniqueness.
• Area-specific problems and codes. Hard water in this county, hail damage in that one, the permit process in this municipality, the neighborhoods with 1970s galvanized plumbing. This is the content a copywriter cannot invent honestly.
• Reviews from customers in that city, quoted with the work described. One review naming the town outperforms a paragraph of SEO copy.
• Local service specifics: response times, which techs cover the area, the office or shop that dispatches there.

Notice what is missing from the list: longer paragraphs about the city itself. Nobody hiring a plumber needs the town's founding history. They need to know you work there, you know its quirks, and your neighbors say so. Keep the page's service content consistent with your main service pages, vary everything that is local.

How Many Location Pages Should You Have?

The honest answer is: as many as you can support with real proof, and not one more. Practitioner consensus in the local SEO community puts the working range at roughly 10 to 15 city pages for a typical service-area business, going higher only when every additional page carries genuine local substance. The pages are also only for towns your trucks actually reach. Claiming a city two counties over because the search volume looked good is how service areas become spam signals.

A practical rule: if you cannot name three jobs you did in a city this year, you do not have a page for that city, you have a wish. Cut the wish list, and put the effort into the towns where the proof is real. Ten strong pages will outperform forty thin ones in rankings, in conversion, and, as the next section shows, in AI answers.

The AI-Search Layer: Substance Is What Gets Cited

Here is where the doorway debate gets a second life. When someone asks ChatGPT, Gemini, or Perplexity "who is the best plumber in Cedar Park," the system looks for pages it can confidently quote: distinct facts, named people, specific local details. A templated city page with swapped names gives the system nothing quotable, so it cites whoever had the real substance. Your competitor's proof-rich page gets named; your forty template pages get skipped entirely.

The same inputs serve both masters. The job counts, tech names, local code specifics, and area reviews that keep you on the right side of Google's spam policies are exactly the citable facts AI answers need. Add LocalBusiness schema with accurate areaServed data so machines can resolve which pages belong to which towns, and make sure key facts are written in clear, direct sentences rather than buried in marketing fluff. The professional version of this, monthly prompt testing with real homeowner questions, is our AEO and LLM optimization service. But the foundation is free: substance on every page you keep.