Most sites with city pages have several competing for the same query without anyone noticing. Here is how to assign cities deliberately, spot pages fighting each other, and fix it without losing what they built.
A site with twelve city pages and one services page usually has a problem nobody has noticed: several of those pages are trying to rank for the same thing, Google has picked a favourite, and the rest are quietly doing nothing. Meanwhile the services page ranks for the city the business is actually in, competing with the city page written for exactly that purpose.
Deciding which page targets which city sounds like a technical exercise. It is really a question of what you can genuinely write about, and most sites get it wrong by building pages first and thinking about it afterwards.
This guide covers how to assign cities to pages deliberately, how to spot pages competing with each other, and what to do when you have already built too many.
We break down how to rank in a second city without a second address in our guide to serving two cities from one location.
Assign a city its own page only when you can write several hundred words about your work in that specific market, because that is the practical test of whether the page can rank.
This is the filter that prevents most of the problems that follow.
A city earns a page when you have:
A city does not earn a page when:
If a city fails the test, it belongs on a service page as part of a service area rather than as a page of its own.
🛠️ Action Step: List your city pages and note how many real jobs you have done in each. Any page with zero is a candidate for removal.
For more on this, see our guide to local keyword cannibalization, which covers how to find and fix pages competing for the same local keyword.
Let your main service pages target your home city and build separate city pages only for the surrounding markets, because your primary location is already reinforced by your address, profile and citations.
This is where the most common conflict arises. A business in Columbus writes a services page and also a "Columbus" city page, and the two compete.
How to divide it:
Your home city already has the strongest possible signal in the form of your address and profile. A separate page adds a competitor rather than reinforcement.
⚠️ Common Mistake: Building a city page for your own city because a template suggested it. It is the single most common source of two pages competing for the same query.
Ensure only one page targets each city-and-service combination, because two pages chasing the same query split signals and Google will choose one arbitrarily.
The rule is simple to state and routinely broken.
Where the overlaps typically occur:
How to check: search your own site for the target term using a site-restricted search and see how many of your pages appear. More than one is a problem worth resolving.
Groundwork on structuring this properly is in the multi-location local SEO guide.
Where two towns share one search market, build one page for the larger and mention the smaller within it, rather than building a thin page for each.
Small adjacent towns frequently do not warrant separate pages, and building them creates near-duplicates.
Combine when:
Separate when:
The service-area page is the alternative. One well-built page covering a region, naming the towns within it, outperforms six thin pages every time.
Where two pages compete, consolidate into the stronger one and redirect the weaker rather than trying to differentiate them after the fact.
Rewriting two thin pages into two distinct ones rarely works, because the underlying problem is that there was only ever enough material for one.
The consolidation process:
Do not simply delete the weaker page. Redirect it, so whatever value it accumulated transfers rather than being discarded.
📊 Flento Data: Across multi-location profiles, sites with fewer substantive location pages consistently outperform those with many thin ones, because thin pages dilute rather than accumulate.
Judge the number by how many you can genuinely maintain and differentiate, not by how many towns are within driving distance.
There is no fixed limit. There is a practical one.
Signs you have too many:
Signs the number is right:
🔥 Quick Win: Find your weakest city page and check whether you have ever completed a job there. If not, redirect it into a service-area page this week. Removing it will help the rest.
Flento shows which of your pages and locations actually rank, which is how you identify competition between your own pages.
Local Keyword Rank Tracker tracks per-city visibility, so you can see which page Google is actually surfacing for each market.
Local Competitor Analysis Tool shows the competitive depth of each town, which informs whether a separate page is worth building.
Google Review Management Software builds the location-specific reviews that make city pages genuinely distinct.
✅ Done? See which of your pages Google is actually surfacing per city. Get started free
Q: Should I build a city page for the city my business is in? A: Generally no. Your address, profile and citations already provide the strongest possible signal for your home city, and a separate page tends to compete with your service pages rather than reinforce them.
Q: How do I know if two of my pages are competing? A: Run a site-restricted search for the target term and see how many of your own pages appear. More than one indicates a split, and Google will pick between them arbitrarily.
Q: How many city pages should a local business have? A: As many as you can genuinely differentiate and maintain. The test is whether you can write several hundred words of real local content per page, not how many towns are within range.
Q: Should adjacent towns get separate pages? A: Only when each has meaningful search demand and you have distinct customers and content for each. Otherwise combine them into one page for the larger town or a service-area page.
Q: What do I do with a page that is competing with a stronger one? A: Move any unique content into the stronger page, then 301 redirect the weaker one to it. Redirect rather than delete, so accumulated value transfers.
Q: Is it better to have fewer, longer pages? A: Generally yes for location content. Fewer substantive pages outperform many thin ones, because thin pages dilute the site rather than adding to it.
The question is not how many cities you would like to rank in. It is how many you can write something true and specific about.
Take your city page list, note the jobs you have actually completed in each, and be honest about the ones with a zero. Redirect those into a service-area page.
You will end up with fewer pages that work rather than more that do not. Try Flento free.
