Multi-location businesses: a location-page architecture that holds up
Twelve pages generated from the same template, where only the city name and the phone number change, are not twelve pages. Google handles duplicate pages through deduplication and keeps only one. Three elements specific to each location change the outcome completely.
- Google describes canonical URL selection, that is, the address chosen as the official version of a page, as deduplication: it selects the most representative page from a set of duplicates and shows only that one.
- A location page becomes distinct through three elements that can’t be copied from another page: local completed work, field information specific to the territory, and service conditions of its own.
- The Business Profile and the location page don’t do the same job. The first decides your presence on the map, the second your presence in regular search results.
- Google states that each business may only have one profile, and that any detected duplicate is automatically hidden.
- Twelve pages maintained four hours each per year come to $3,900. Across forty pages produced without location-specific content, the spending becomes a liability.
Contents
What is location-specific content
Location-specific content is information that only one location page can present, because it stems from the real activity of that location. An address and a phone number don’t qualify: they can be swapped in as variables in a template. Work completed in that territory, a local constraint known to that team and service conditions specific to that location do qualify. It is what separates a location page from a duplicated page.
The duplicated-template trap
We are writing here for businesses operating several service locations: branches, depots, showrooms, workshops, clinics. It covers the pages of your website, not Business Profiles, which are covered elsewhere in our corpus.
The usual approach is logical and produces a bad result. You build a template, insert variables for the city name, the address, the phone number and the hours, and generate twelve pages in a few minutes.
Except those pages are identical apart from four variables. They present the same services, the same introduction text, the same photos, and they target the same search intent give or take a city name.
Google treats this case the way it treats any set of duplicate pages: through deduplication. It selects the URL it judges most representative and shows only that one. Your other eleven pages exist, but they don’t work.
The bill, meanwhile, is commercial. Eleven locations out of twelve stay invisible in their own market, and each one has to buy back through local advertising the visibility its page should have produced. On a budget of $800 per month per location, compensating for that design error comes to $105,600 a year.
The symptom is misleading. Your pages are indexed, that is, known and recorded by Google, they show up in your reports, and yet only one receives traffic. Management that looks at the number of indexed pages concludes everything is fine, while eleven pages out of twelve consume maintenance without bringing in a single customer.
The three location-specific elements
A location page becomes distinct when it contains at least three things no other page on your site can contain. It is the only investment in this file that produces a durable advantage, because it can’t be bought.
Work completed in that territory. Real photos, a description of the project, constraints encountered. It is the most costly element to produce and the hardest to copy, which makes it the most useful.
Field information only that team has. A municipal regulatory particularity, an access constraint, a supply lead time specific to the region, a season that starts earlier.
Service conditions specific to the location. Actual lead time, delivery zone from that point, languages spoken, services offered here and nowhere else, named staff.
These three elements share one trait: they can’t be generated. They require someone at each location to supply raw material, which explains why most businesses never produce them. That internal cost is real, about one hour per quarter per location, and no budget can outsource it.
It is also what makes it a durable advantage. A competitor can copy your template in a day. They can’t copy your job sites in Saint-Jérôme.
How many pages, and which ones
The rule is simple: one page per real service location, never one page per city served. It directly decides the budget you commit and the revenue you get back.
A real service location is a place where staff work and where the service departs from, so where your business carries a fixed cost. A city you deliver to isn’t a service location, it is a territory, and it belongs on the page of the location that serves it.
That distinction avoids the most expensive mistake in this field: producing forty city pages around three locations. Those thirty-seven extra pages have no possible location-specific content, cannibalize each other, in other words compete for the same customer searches while weakening one another, and cost maintenance every year without producing a single customer.
If a territory seems to deserve its page without you having a location there, ask the location-specific content question: do you have completed work there, field information, distinct service conditions? If so, the page is justified and its maintenance cost pays for itself in inquiries. If not, it is filler, and every year of maintenance is pure expense.
The profile and the page do different jobs
Confusing the two leads to neglecting one or the other.
The Business Profile decides your presence on the map and in local results. It is governed by strict rules: Google states that each business may only have one profile, and that any detected duplicate is automatically hidden on Maps and in Search results.
The location page on your site decides your presence in regular search results, where a good share of customer inquiries plays out, and it anchors the profile. It doesn’t have the same constraints and doesn’t follow the same rules.
The two reinforce each other when they are consistent: the profile points to the right location’s page, never to the homepage, and the information matches. They weaken each other when the profile points to a generic page or when the hours differ between the two. Every inconsistency is paid for in customers who travel for nothing and inquiries that never reach the right location.
The rules for profiles, especially for businesses without a storefront open to the public, are covered in our article on local SEO without a storefront.
Data consistency at scale
From five or six locations up, the problem stops being editorial and becomes organizational. It also stops being free: every piece of wrong information costs a customer who travels for nothing or an inquiry that never arrives.
Hours change for a statutory holiday, a location moves, a phone number is replaced. Each piece of information lives in several places: the page, the profile, the structured data, that markup describing each location to search engines, sometimes a directory or a store locator.
To hold at scale, you need a single source: a table maintained by one accountable person, feeding the pages and serving as the reference for the profiles. Without that source, the gap widens within months and nobody knows which version is right.
The classic symptom is a customer who shows up on a statutory holiday trusting wrong hours. The reputation cost far exceeds the cost of the table that would have prevented the error, and it repeats at every holiday.
What a poorly designed architecture costs
The math is direct and it settles the question of page count.
A properly maintained location page takes about four hours a year: updating completed work, checking information, adjusting service conditions. Twelve pages therefore represent 48 hours, or $3,900 at $82 an hour.
That amount is perfectly justifiable for twelve real locations, because each page can carry location-specific content and generate local inquiries.
It becomes a liability across forty city pages without location-specific content. You pay $13,000 a year to maintain pages that cannibalize each other, or, more often, you don’t maintain them at all and they age while displaying wrong information.
The third option, the one we see most often, is the worst: produce the forty pages, never maintain them, and rediscover them three years later with outdated phone numbers.
What to settle before generating location pages
These five questions get settled in one meeting and determine whether your pages will produce customers or maintenance.
- How many real service locations do you have, with staff on site?
- For each one, do you have local completed work, field information and service conditions of its own?
- Who, at each location, will supply that material, and how often?
- Who maintains the single source for hours, addresses and phone numbers, and where does it live?
- If a location page generates no inquiries after twelve months, does it get removed, and who decides?
A solid answer names one accountable person per location and a single data source. A vague answer talks about covering every city in the region. A vendor who proposes generating forty location pages from a template is selling you volume that Google will deduplicate and that you will maintain for years.
Determining how many pages are justified in your case and what each one must contain is part of what we establish in a paid audit.
What you keep in house: the local material, which comes from each location’s team, and the decision on page count. What can be delegated: page structure, setting up the single data source, editorial production from the material supplied, consistency with the profiles and measurement by location. A business that gets three job-site photos and two local particularities per location per quarter has pages no competitor can copy. A business that counts on a template gets twelve pages of which only one works, and pays to maintain the other eleven.
The distinction between organic search and paid search is clarified in the difference between SEO and SEM.
The general framework for search is set out in a complete guide for SMBs and large companies.
Building a local presence that produces inquiries in every territory is at the heart of the Attract customers with SEO and AI goal.
Is your challenge mostly search and content? See our work in organic search.
Beyond a handful of addresses, managing profiles becomes a risk of its own: the method is in our article on managing a hundred Business Profiles.
Frequently asked questions about location pages
Do you need a page per city served?
No. One page per real service location, where staff work and where the service departs from. A city you deliver to is a territory, not a service location, and it belongs on the page of the location that serves it. Producing forty city pages around three locations creates thirty-seven pages with no possible location-specific content.
Why are our location pages producing nothing?
Probably because they are identical apart from a few variables. Google handles duplicate pages through deduplication: it picks the most representative one and shows only that one. Your pages are indexed, they appear in your reports, and only one receives traffic. Check how many of them actually receive visits, and weigh that number against the maintenance cost you pay for the whole set.
What content makes a location page distinct?
Three elements no other page on your site can contain: work completed in that territory with photos, field information only that team has, and service conditions specific to that location. The address and the phone number don’t count: they can be swapped in as variables in a template.
How much time does maintenance take?
Count about four hours per page per year for a serious update. Twelve pages therefore represent about fifty hours, or close to $4,000 at the going rate. That cost is justifiable for real locations, each producing local inquiries, and becomes a liability on city pages without location-specific content, which age while displaying wrong information without bringing in a dollar.
Who should supply the local material?
Each location’s team, and that is the real bottleneck of this file. Three job-site photos and two local particularities per quarter are enough, at an internal cost of about one hour per location. Without that contribution, no outside vendor can produce genuinely location-specific content, whatever the budget, and you fall back on the template.
How do you keep data current across ten locations?
Through a single source, a table maintained by one accountable person, feeding the pages and serving as the reference for the profiles. Without it, hours, addresses and phone numbers drift apart within months between the site, the profiles and the directories, and nobody knows which version is right.
- Google Search Central, What is canonicalization, official documentation, accessed July 2026. Source for the deduplication process and the display of a single version of the content.
- Google, Business Profile Help, Guidelines for representing your business on Google, accessed July 2026. Source for the one-profile-per-business rule and the automatic hiding of duplicates.
- Falia framework, arithmetic of location-page maintenance costs. Amounts are explicit worked examples, to be redone with your location count and your rate.
Geneviève puts the strategy for your engagement into action. She leads all our web development projects: Shopify, WordPress and the new ways of building a site with AI. She manages our team of developers and translates your business needs into technical language. She runs your organic search (SEO), your visibility in AI answers (GEO) and your site's conversion rate optimization (CRO). Her work is at the heart of three goals: Attract customers with SEO and AI, Improve your site's conversion, and Strengthen your visibility in AI answers. With Gabriel, she also builds the landing pages for your advertising campaigns. She writes mainly about SEO, AI visibility and web design.
About Falia →
SEO
Paid advertising
Conversion
AI visibility
Web design