Multi-Location SEO: Location Pages That Don't Compete
A business with six locations builds one page per city, and every page reads the same. Same three paragraphs about the team. Same bullet list of services. Same closing line, with the city name swapped in. Six pages, one search intent behind each of them, and Google can't tell which page should win — so it ranks all six worse than one strong page would rank alone.
This is keyword cannibalization applied to a specific structure: location pages. The general mechanism is the same whether it's two blog posts on the same topic or six city pages built from one template. What differs is the fix. You can't merge six location pages into one — customers in six different cities need six different pages. The fix here is making each page genuinely distinct, not deleting the duplicates.
Quick Navigation
- Why Look-Alike Location Pages Compete With Each Other
- What Should Actually Differ Between Location Pages
- One Google Business Profile per Physical Location
- LocalBusiness Structured Data for Each Location Page
- How to Check Your Own Location Pages
- Frequently Asked Questions
Why Look-Alike Location Pages Compete With Each Other
A location page built by swapping the city name into a shared template gives Google no reason to treat it as a distinct page, because the actual content underneath the city name is identical across every location you serve. Google's ranking systems compare what's on the page, not the address in the URL or the H1.
Picture the plumbing company with six city pages again. A search for "plumber in [city]" is a hyperlocal query — the person searching wants a business that actually covers their neighborhood, not a business that happens to mention their city once. If all six of that company's pages describe the same generic service area in the same words, Google has six candidates that all look equally (ir)relevant to any one of those six searches. Splitting one company's ranking signal six ways is worse than concentrating it on one page, and it's worse again than what a competitor with one focused, specific page in that city gets to do.
There's a second problem sitting on top of the ranking issue: thin content. A location page that differs from its five siblings only by a find-and-replace on the city name doesn't clear the bar of "unique, valuable content" that Google's own helpful content guidance asks for. At a small scale, one or two thin pages rarely trigger a site-wide problem. At the scale of ten, twenty, or fifty near-identical location pages, the pattern reads as a template stamped across the site rather than content built for each place. That's a harder problem to walk back than fixing two competing blog posts, because the fix has to happen at every location, not just one.
What Should Actually Differ Between Location Pages
Two location pages stop competing once each one contains information that's true of that location and not the others — the same city name in different words doesn't count, and neither does swapping only that one variable while everything else stays fixed.
Four things are worth building out for each location, in order of how much they typically move the page:
A real service area, not the parent brand's full footprint. List the actual neighborhoods, ZIP codes, or towns that location covers — not the company's entire multi-state territory copied onto every page. A location page that claims to serve the same 40 towns as every other location page in the company isn't describing that location. It's describing the company.
The people who work there. A named manager, technician, or team roster tied to that address does two things a generic "our team" paragraph can't: it gives the page content no other page on the site has, and it gives a local searcher a reason to trust a specific human over an anonymous storefront.
Reviews or short case studies from that location's actual customers. A quote or a brief story from a customer served at that address is location-specific by definition — it can't be copy-pasted onto the sister page in the next city over without becoming false. This is one of the fastest ways to make a page unique, because the content doesn't have to be written from scratch; it has to be collected.
Actual driving directions and parking information. "Located off Exit 14, parking available in the rear lot" tells a real visitor something a phone number and a map embed don't. It's also, structurally, a sentence that cannot exist on any other location's page.
None of these require a copywriter. They require the operational information the business already has — who works there, who they've served, how to actually get there — moved onto the page instead of left in a spreadsheet.
One Google Business Profile per Physical Location
Google's guideline is direct: create one Business Profile for each physical location, and never combine multiple addresses into a single listing. A business with six locations needs six separate Google Business Profile listings, each with its own address, phone number, and hours — not one listing that tries to represent all six.
The mistake shows up in both directions. Cramming multiple addresses into a single profile is treated as an attempt to manipulate local rankings and risks suspension, according to Google's guidelines for representing your business. The opposite mistake — creating more than one profile for the same location — is explicitly against the same guidelines. One address, one profile. No exceptions for convenience, and no shortcuts for a business that would rather manage one dashboard instead of six.
There's a real operational reason to get this right beyond avoiding a suspension. Google's local pack results are matched to a specific profile at a specific address. A location without its own profile has no way to appear in the map pack for searches tied to that address, no matter how well its website page is written. The website page and the Business Profile are two separate ranking surfaces working toward the same goal — see the factors that actually move local pack rankings for what the profile side of that equation depends on.
Businesses managing more than a couple of locations don't have to do this by hand. Google's Business Profile groups let an owner manage multiple listings from one account without merging them into one profile — the listings stay separate at the data level, while the management stays centralized.
LocalBusiness Structured Data for Each Location Page
Every location page should carry its own LocalBusiness structured data (JSON-LD), because schema is how a search engine confirms which physical address a specific page is describing — the same signal a human reader gets instantly from a street address, made machine-readable.
Google's structured data documentation keeps the requirement short. Only two properties are required: name, and address written as a full PostalAddress object — separate street, city, region, and postal-code fields, not one line of plain text. Everything past those two is recommended rather than required: geo-coordinates and opening hours help the schema line up with the Business Profile for that same address, and a specific subtype (Restaurant or Dentist rather than the generic LocalBusiness type) helps whenever a closer match exists.
One property deserves a warning: aggregateRating and review. Google's guidance is explicit that these fields are meant for a third party reviewing a business, not for a business marking up its own self-authored ratings. A business that writes its own five-star reviews into its own structured data risks a manual action for review misuse — the fix is to pull ratings from an actual third-party review platform via that platform's own markup, or to leave the rating fields out entirely.
Six location pages, six sets of LocalBusiness markup, each with its own address block. Copying one page's schema onto five others and changing only the address is the same shortcut that creates duplicate content in the visible page copy — it just does it in a place most site owners never look.
Source: Local Business structured data, Google Search Central.
How to Check Your Own Location Pages
The fastest check for cannibalization between your own location pages is the same one used for any two competing pages: open Google Search Console, filter the Performance report to a query tied to one location, and check the Pages tab for how many of your URLs show up for it.
If a search like "[service] in [city]" pulls up two or three of your location pages instead of one, they're splitting the same ranking signal that a single page would concentrate. The full method — including how to decide whether to merge or set a canonical — is covered in the keyword cannibalization guide; for location pages specifically, canonical tags are rarely the right tool, since each city page needs to stay live and indexed on its own. The fix is closing the content gap between the pages, not choosing a winner and redirecting the rest.
A side-by-side read of your own pages catches most of the obvious cases before you ever open Search Console. Open two location pages in adjacent tabs and count the sentences that are identical apart from the city name. A handful of shared boilerplate — the company's founding story, a licensing statement — is normal and fine. Whole paragraphs of service description repeated word for word across every location is the pattern worth fixing first.
Brass-SEO reads Google Search Console data to surface exactly this pattern: which of your own URLs compete for the same query, location pages included. The complete local SEO framework covers where location pages fit alongside the Google Business Profile and review signals that also affect local rankings.
Frequently Asked Questions
How many location pages are too similar?
There's no fixed word-count threshold. The test is whether a page contains information specific to that address — a real service area, named staff, local reviews, or directions — that couldn't be copy-pasted onto a sister page without becoming false. A page that fails that test is too similar, whether it's 300 words or 3,000.
Should I use one page for all my locations instead of separate pages?
Only if you genuinely serve all those locations from a single searchable intent, which is rare once a business has distinct service areas or storefronts. Separate pages let each city or neighborhood rank for its own local searches. A single combined page can rank for broad, non-local searches, but it can't compete for "[service] in [specific city]" the way a dedicated page can. Most multi-location businesses need both: a combined locations overview page for site navigation, and individual pages for each address that can actually rank locally.
Can I use a canonical tag to fix location page cannibalization?
Usually not. A canonical tag tells Google to treat one page as the authoritative version and effectively drop the other from independent ranking — appropriate when two pages target the exact same intent and only one needs to stay indexed. Location pages need to stay independently indexed, because each one serves a real, different search. Closing the content gap between the pages is the right fix here, not picking one city to represent all of them.
Does Google Business Profile ranking depend on the website's location pages?
Partially. The Business Profile itself is a separate ranking surface from the website, driven by proximity, relevance, and profile signals like reviews and category. A well-built website location page doesn't directly boost the Business Profile's map pack position, but it does give that location a real page to rank in organic results below the map pack, and a consistent, specific address across both the website and the profile reinforces the same signal to Google.
What if my locations are service areas without a physical storefront?
Service-area businesses without a public-facing address still need a page per service area on the website, built around the real neighborhoods or towns each area covers. On the Google Business Profile side, a service-area business can hide its exact address and instead define the areas it serves within the profile itself — the one-profile-per-location rule still applies, but the profile is configured as a service-area business rather than a storefront.
Give Your Locations Room to Rank
Six templated pages fighting each other for the same search is a problem you can fix without deleting a single page. Brass-SEO reads your Google Search Console data and names the pages competing for the same query, location pages included, so you know exactly which ones need real local detail instead of a find-and-replace. Start a three-day free trial and ask which of your location pages are splitting the same search. The full framework lives in the Local SEO Playbook.