Local SEO pages: how to avoid cloned city-by-city pages

In brief: A "service + city" page is only risky if it reuses an identical template without offering anything specific to the area; Google then treats it as doorway page abuse, resulting in lower rankings or outright removal from search results. This article explains how to audit your existing city pages, decide which to keep, merge or redirect, and then check the outcome technically in Search Console.

Prerequisites before fixing your city-by-city pages

Before you touch a single page, you need to know exactly what already exists. An audit carried out without an overall view almost always leads to partial fixes, which can sometimes backfire.

• List all published local URLs, ideally from a sitemap export or a crawling tool, then note for each one the target city, the main content and its indexing status in Google Search Console.

• Check that you have access to Search Console (page indexing report, URL Inspection tool) and to the site's admin interface, which you will need in order to publish redirects.

• Gather the local evidence actually available for each city (area served, team or point of contact, completed projects, access constraints, availability), without ever making anything up.

• Allow time for a manual, page-by-page audit: an automated bulk fix risks treating pages in the same way when they don't all deserve it.

This approach addresses one specific issue, duplicate city pages, within a broader method for local search optimisation on Google which also covers business listings, reviews and the consistency of company information.

Step 1: identify pages that look like doorway pages

Start by identifying pages that work as gateways rather than destinations. Check whether pages targeting different cities or regions actually redirect to the same page, or whether their main content is almost identical from one URL to the next.

Next, compare each city page with its neighbours. Substantially similar pages placed ahead of a clear navigation hierarchy match what Google calls a doorway page abuse: pages targeting similar queries that act as low-value intermediaries before the destination that is actually useful. Google's own examples include pages targeting different cities that redirect to the same destination, or near-identical pages positioned closer to search results than to a clearly navigable hierarchy.

Bear in mind that this type of pattern can be detected automatically, then followed up by human review or manual action. The consequences range from lower rankings to outright removal from search results.

Step 2: assess whether each city page offers unique, verifiable value

For each page you kept after the previous step, ask a simple question: what does it offer that no other page on the site already does? The main content must provide original, complete information, analysis or description, not a reworded version with the city name swapped. Google looks for notable value compared with other results and demonstrable first-hand experience or expertise, without setting a word count or a percentage of unique text.

In practical terms, document precise details specific to the area: genuinely different ways of working, the area served, a local team or contact, access constraints, availability and local projects. This list is not an official scale; it is a practical application of Google's helpful content principle. The page must also answer a local question that genuinely changes the user's decision: a response time specific to the neighbourhood, a parking constraint, a feature of the area.

Keep the page indexable only if this difference can be demonstrated. Otherwise, route it towards the consolidation covered in the next step.

Key takeaway

A city page deserves to stand alone if it answers a local question that would change a user's decision (response time, access, area served) and if that difference can be backed by something verifiable, not just asserted in the text.

Step 3: decide which pages to keep separate and which to consolidate

Now compare the remaining pages with one another. If the difference in content is not clear and significant, Google tends to group them as duplicates and select a single canonical page to represent the whole set. Also check which page makes the most sense for a user arriving from Google Search before choosing the one to keep.

Organise the pages you retain by service, area or location, within a navigation hierarchy that users can genuinely browse. Multiplying near-interchangeable URLs, positioned closer to search results than to a clear site architecture, remains an explicit example of doorway page abuse.

Pages to merge

Two cities very close to each other geographically, served by the same team, with the same lead times and the same offer, and nothing specific to either: this is the clearest sign that merging is needed rather than coexistence.

Pages to keep separate

Two locations with distinct teams, different opening hours, a specific local offer or regulatory constraint, or a catchment area differentiated enough to change the answer given to the user.

Step 4: apply the right technical fix, canonical or redirect

Once the decision has been made, the technical choice follows directly. The rel="canonical" tag does not make cloned pages unique: it merely designates one representative URL among identical or very similar pages. If the old city page needs to disappear in favour of a destination that is relevant to the user, use a permanent redirect rather than a simple canonical tag.

Avoid using the robots.txt file to try to canonicalise a page, and avoid the noindex as a way of influencing the choice of canonical page.

Watch out

A declared canonical remains a preference, not a guarantee: Google may select another URL in the group if it considers it more representative, based on various crawling and popularity signals.

Step 5: audit indexing and verify the truthfulness of your local presence

After any fix, go back to Search Console to check that Google has understood your intent. The URL Inspection tool shows the canonical declared by the site and the one Google has actually selected: the two don't always match.

Also check the page indexing report, in particular the "Duplicate, Google chose different canonical than user" status, which flags pages still being handled incorrectly after a redesign.

Local accuracy matters as much as technical set-up. Never claim a business location or a virtual address in a city where the company is not actually based. For a business that travels to customers, use a profile with an office or central location combined with a service area, rather than a fake local address: a virtual office with no staff on site during opening hours is not eligible.

Good to know

Separate locations can justify separate profiles, but each must correspond to a real, verifiable presence, not merely an address mentioned on a city page.

Pages generated with AI: where is the line?

Producing many city pages with an automation or generative AI tool is not a problem in itself, whatever the tool used. What turns the practice into abuse is not the tool but the goal: if the main aim is to manipulate rankings rather than help users, and no real value is added, Google classifies this as scaled content abuse.

In November 2025, Google clarified that its spam policies also apply to responses generated by Search, which explicitly extends their scope beyond traditional ranking. This clarification reinforces the value of local pages that are genuinely useful, not merely optimised to appear.

In practice, treat AI as an assisted-writing tool drawing on local information that has already been verified, never as a generator of city-by-city variants: the text can be reworded automatically, but the facts it reports must remain accurate and specific to each area.

Common mistakes that turn a local page into a cloned page

Some mistakes come up almost every time in audits, whatever the industry.

• Simply swapping the city name in an identical template, without adding any information specific to the area.

• Creating a page for every town in the area without first checking whether real search demand exists.

• Multiplying pages without a clear navigation hierarchy, relying solely on URLs designed for search engines.

• Using noindex or robots.txt as a canonicalisation solution, instead of a proper redirect or genuinely differentiated content.

• Displaying a local address or business location that does not correspond to any real presence on the ground.

Practical tips for keeping local pages useful over time

• Prioritise a small number of dense, verified city pages over broad, generic coverage.

• Update your local evidence (projects, availability, access constraints) at the same pace as real activity on the ground.

• Periodically recheck in Search Console the canonical chosen by Google after every redesign or addition of pages.

• Extend coverage to new cities only when your existing pages are already delivering concrete results.

A city page that stands the test of time is never the one that ticks off the most towns: it is the one that stays true to what the business actually does, city after city.

Related reading: Local rank tracking by city: how do you measure your local ranking?.