FishingSEO
SEO Strategies

Multi-Location SEO: When City Pages Help or Hurt Rankings

By FishingSEO••11 min read

City pages help when each one stands for a real place your business works from or serves, and when it gives local searchers information they can't get on your other pages. They hurt when they're near-copies with the city name swapped in, made mainly to rank for "[service] + [city]" searches. Google's spam policies call that pattern doorway abuse.

In practice, the deciding question is not how many city pages you have. It's whether each page would still be worth having if search engines didn't exist.

This guide covers what Google's documentation says, where the line usually falls, and how to build, audit or consolidate location pages.

What Google's documentation actually says

Several Google sources bear on multi-location SEO. These are documented facts, separate from the analysis later in this post.

Doorway abuse. Google's spam policies define doorways as sites or pages "created to rank for specific, similar search queries" that "lead users to intermediate pages that aren't as useful as the final destination." Two of the listed examples matter most here:

  • Having many domains or pages aimed at specific cities or regions that all send users to one page
  • Building near-duplicate pages that look more like search results than a clear, browsable hierarchy

Scaled content abuse. The same policy page describes scaled content abuse as "many pages are generated for the primary purpose of manipulating search rankings and not helping users," regardless of how the pages are made. That includes AI or template tools, and it covers mass-produced pages that add little value.

Helpful content guidance. Google's guide to creating helpful, people-first content lists warning signs. One is: "Is the content primarily made to attract visits from search engines?" Another asks whether you're "using extensive automation to produce content on many topics." The guide also says Google has no preferred word count.

Local ranking factors. Google says local results are based mainly on relevance, distance, and prominence. Prominence is partly "based on info like how many websites link to your business and how many reviews you have." Google keeps the details of its algorithm private.

Business Profile rules. Google's Business Profile guidelines say:

  • Each location should link to "a website that represents your individual business location."
  • Businesses shouldn't create more than one profile per location.
  • Virtual offices aren't eligible for a profile.
  • Service-area businesses should hide their address, and their service area shouldn't extend beyond about two hours' drive from where they're based.

The separate business links policy says action links for multi-location businesses must go to a site for the specific location, not a general landing page or another location's page.

Structured data. Google's LocalBusiness structured data documentation says to mark up each location as its own LocalBusiness, with a url pointing to that specific location.

Taken together, Google expects one real location to have one profile and one dedicated page. It treats many near-identical pages aimed at different places as a spam pattern.

When city pages help rankings

The points below are analysis based on the documentation above, not confirmed ranking factors.

You have physical locations customers can visit

This is the clearest case. If you run stores, clinics or offices in several cities, a page for each location:

  • Gives each Google Business Profile the location-specific page it's supposed to link to
  • Gives you a canonical place for that location's address, hours, phone number, staff and services
  • Supports relevance, because the page confirms what that location actually offers

For a chain, a single "Locations" page with a list of addresses usually does less work than individual pages. It can't hold location-specific details like hours, parking, staff or services that differ by branch.

You serve distinct areas with genuinely different offers

Service-area businesses, such as plumbers, cleaners or HVAC companies, can justify area pages when the substance differs from one area to the next. For example:

  • Different service teams, response times or opening hours
  • Different services offered (for example, commercial work only in one metro area)
  • Real projects completed in that area, with photos and details you have permission to share
  • Local rules or conditions that genuinely affect the work, if you can document them accurately

The page answers a local question better than any other page on your site

A good test: would a customer in that city find this page more useful than your general service page? If yes, the page earns its place. If the only difference is the city name, it doesn't.

When city pages hurt rankings

The pages differ only in the city name

This is the classic doorway pattern: dozens or hundreds of pages that read like "Best [Service] in [City]," with the same body text, a swapped place name and a few paragraphs of generic local trivia. Google's spam policy describes exactly this kind of page. The risks are:

  • A manual action or algorithmic demotion under the spam policies
  • Pages that get crawled but not indexed, or indexed but never ranked
  • Wasted effort that could have gone into stronger core pages

You target cities you don't actually serve

A page for a city two hours past your real service area, with no team or customers there, gives searchers nothing they can act on. It also clashes with the Business Profile rule on service-area limits. Even if the page ranks, it can frustrate visitors who can't buy from you.

The pages compete with each other

Overlapping pages, like "plumber in Springfield," "Springfield plumbing services" and "emergency plumber Springfield," can split signals across URLs that serve the same intent. Google's documentation on consolidating duplicate URLs explains how to point duplicate or near-duplicate content to one preferred version. Before you create several pages for one city, check whether the search results actually treat those queries as different intents. Our guide on How to Validate AI Keyword Clusters Before Publishing covers that process.

They were mass-produced with AI or templates and never reviewed

Templates and AI aren't the problem in themselves. Google's scaled content policy applies "no matter how it's created." The problem is publishing many pages that add nothing. If an AI tool drafts 200 city pages and nobody adds real location data, that's the pattern the policy describes. The checks in Stop Publishing AI Content Without These SEO Checks apply here too.

A quick decision framework

Use these questions before you create (or keep) a city page:

  1. Is there a real location or a real, staffed service presence for this area? If no, don't create the page.
  2. Does the page include at least several facts that are unique to this location? Examples: address, hours, staff, services, prices, projects, reviews or directions. If no, add them or merge the page.
  3. Would a customer in this city prefer this page to your main service page? If no, the main page probably serves them better.
  4. Does it link to (and from) the right Business Profile, if one exists? If a profile links to your homepage, the location page may not be doing its main job.
  5. Can you keep it accurate? Wrong hours or old phone numbers on 50 pages are a trust problem. Only publish what you can maintain.

What a useful location page includes

There's no required template, and Google says it has no preferred word count. Think of this as a menu of useful content, not a checklist to pad pages:

  • Name, address and phone number matching the Business Profile
  • Opening hours, including holiday or seasonal changes
  • Directions, parking and accessibility details from people who actually know the site
  • Services available at this location, especially where they differ from other branches
  • Staff or team information, with real names and roles if staff agree
  • Local proof: reviews from customers of that location, project examples or case details you're allowed to publish
  • An embedded map or clear location context
  • Location-specific FAQs based on questions that branch actually gets

For service-area pages, swap the street address for the area served, the team that covers it, typical response times and real local work.

What to leave out: generic city history, population stats and landmark lists that have nothing to do with your service. They make a page longer but no more useful.

For more on adding verifiable expertise, see 7 Ways to Build Trust Signals Into AI Content.

Technical setup for multi-location sites

URL structure. A predictable hierarchy like /locations/city-name/ (or /locations/state/city/ for large chains) keeps pages organized and browsable. That's the opposite of the "search results-like" pattern Google's doorway policy describes.

Internal links. Link location pages from a locations hub, and link relevant service pages to the locations that offer them. Avoid sitewide footer blocks listing 100 city links. Our walkthrough on How to Build AI-Driven Internal Links in 30 Minutes covers a manual-review workflow for this.

Structured data. Mark up each location page with the most specific LocalBusiness subtype that fits. Include name and address (both required by Google), and add recommended properties like geo, telephone, url and openingHoursSpecification, as described in Google's documentation. Validate with the Rich Results Test. Structured data helps Google understand the page. It doesn't guarantee rich results or better rankings.

Business Profile links. Point each profile's website field to its own location page, not the homepage, in line with the Business Profile guidelines.

Crawl access. Make sure location pages aren't accidentally blocked. A How to Audit Robots.txt With AI in 30 Minutes can catch this quickly.

How to fix an existing set of thin city pages

Hypothetical example: a home-services company has 120 city pages, but it has staff based in only three metro areas and actually takes jobs in about 30 towns.

A reasonable cleanup process:

  1. Inventory. List every city page with its clicks, impressions, indexing status (from Search Console), leads and backlinks.
  2. Sort into three groups.
    • Keep and improve: areas you really serve, where you can add unique, accurate details
    • Merge: overlapping pages for the same area or intent. Consolidate them and use 301 redirects to the strongest URL.
    • Remove: areas you don't serve. Redirect to a relevant regional or service page if one truly fits. Otherwise let the page return a 404 or 410.
  3. Improve the keepers with the location-specific content listed above.
  4. Update internal links so nothing points to removed URLs.
  5. Monitor indexing and performance in Search Console over the following weeks. If rankings shift unexpectedly, the method in How to Audit Search Intent Drift With AI in 45 Minutes can help you tell whether the search results changed or your pages did.

Cutting pages can feel risky. But pages that get no impressions and cover areas you don't serve weren't contributing, and removing them makes the site easier for people and crawlers to understand. This is a judgment call, not a guaranteed outcome, so track results.

How to measure whether city pages are working

  • Search Console: impressions and clicks for location-modified queries, plus indexing status per page
  • Business Profile performance: website clicks, calls and direction requests per location
  • Conversions: calls, form fills or bookings attributed to each location page
  • Engagement: whether visitors move from the location page to booking, contact or directions

If a page has been live for months, is indexed and gets no impressions, ask whether it serves a real search need. Don't just add more text.

Conclusion

City pages aren't good or bad for SEO in themselves. Google's documentation supports one dedicated page per real location, linked from that location's Business Profile and marked up as its own LocalBusiness. The same documentation describes swapped-name pages aimed at many cities as doorway abuse, and large batches of low-value pages as scaled content abuse.

The practical line is simple: build a page when you have a real presence and real local information to share, and merge or remove pages that exist only to catch searches. Fewer, more useful location pages are usually easier to rank, easier to maintain and more honest with customers.

References

Back to all posts