Should each location have its own Google Business Profile?

Yes. Every location with a physical address customers can visit, or a defined service area, needs its own verified profile. Never consolidate several branches into one listing — you lose the map pack in every catchment except the one the listing is registered in. Manage them under a single organisation account so permissions and reporting stay sane.

Do I need a separate page for every location?

Yes, but only if each page can justify its existence. A location page that differs from the others by a town name and a phone number is a duplicate with a substitution, and Google treats it as one. If you cannot say something genuinely specific about a location — its team, its stock, its parking, its catchment — the honest answer is that you have a content problem to solve before you have a page to publish.

How do I stop location pages competing with each other?

Give each one a distinct geographic target and genuinely distinct content, and link them through a proper hierarchy rather than a flat list. Cannibalisation between location pages usually shows up as several branch pages rotating for the same city query, none ranking well. The fix is clearer targeting and better differentiation, not more pages.

How important is NAP consistency for multi-location SEO?

It matters, and at scale it is an operations problem rather than a marketing one. Name, address and phone number must match across your site, your profiles and the major directories. The realistic goal is not perfection everywhere but consistency in the sources that matter, plus a single internal record that is the agreed truth and a process for propagating changes when a branch moves or a number changes.

How do I track local rankings across many locations?

By location, not as an average. Local results are computed from where the searcher is standing, so a national average position is a number that describes nobody. Track rank per branch from within its own catchment, ideally on a grid of points around each location, so you can see how far the visibility extends rather than just whether it exists at one spot.

Is there a minimum number of locations before Google's bulk verification tool applies?

Yes. Google's own requirement is a spreadsheet with ten or more profiles from the same business, submitted through Business Profile Manager's Verifications tab rather than left as an upload. The spreadsheet must list every location the business manages, not a shortlist, and service-area businesses aren't eligible for the bulk path at all. Below ten locations, verification happens individually, the same way it does for a single-location business.

What is a location group in Google Business Profile, and is it worth setting one up?

A location group is Google's mechanism for running bulk tasks, such as verification or permission changes, across many profiles at once, organised however suits the business: by chain, by region or by category. A single location can sit inside more than one group. Below roughly ten locations the overhead of setting one up rarely pays for itself. Above that, an organisation account built around location groups and user groups, rather than adding individual people to each profile one at a time, is how Google itself recommends managing access at scale.

With twenty locations and limited time, should effort go into profile completeness or into content?

Completeness first, on the current evidence. Whitespark's 2026 practitioner survey shows the factors that rose most between 2023 and 2026 are Business Profile completeness signals, such as predefined services, keywords in the services field and accurate hours, while generic content volume and outbound linking fell. At one location that already argues for finishing the profile before writing another page. At twenty locations the same hour is spent once and repeated across the whole estate for free, which makes the case stronger, not weaker.

Is there research on how many location pages is too many before a flat structure stops working?

No substantial study measuring a specific numeric threshold was identified in the sources reviewed on 8 September 2026. What is well established is the mechanism rather than the number: search engines need a way to understand how pages relate to each other, and a flat list of fifty near-identical URLs gives them none. In practice the trigger is a symptom, not a count. Once several location pages start rotating for the same query, or a whole region has no page able to rank for the city-wide search, that is the signal to introduce a hierarchy, whatever the location count happens to be at that point.

How is NAP consistency at scale different from a one-off listings clean-up?

It is a different kind of problem, not a bigger version of the same one. A single-location business fixes its listings once. A multi-location business generates new inconsistencies continuously, as branches open, close, move and change numbers, which turns the work into an ongoing operational process rather than a project with an end date. Which directories and aggregators are actually worth that ongoing effort is a separate question, covered in the site's citation-building guide.

Local SEO when you have more than one location

Everything that works for a single-location business still works when you have twelve. It just gets harder in ways that are structural rather than tactical, and the usual failure is not lack of effort. It is fifty location pages that read like one page repeated with the town name swapped, reporting that averages away the branch in trouble, and an update process that nobody owns.

Multi-location local SEO is mostly a systems problem wearing a marketing costume.

Local results are geographic, and your reporting probably isn’t

Start here, because it changes what you can see.

A local search result is computed relative to where the searcher is standing. There is no single ranking for “dentist” — there is a ranking at the corner of one street, a different one four blocks away, and a different one again in the next suburb. Proximity is a heavy factor, and it means your visibility has a shape, not a position. The mechanics of how the map pack is assembled are covered in the Google Maps SEO guide; what follows assumes them.

It is worth knowing that most of what circulates as settled fact here rests on local SEO statistics whose provenance does not survive a trace — including the ranking-factor lists, which are surveys of practitioner opinion rather than measurements.

Most multi-location reporting flattens this into an average. That number is worse than useless: it describes no real person’s experience, and it hides the two things you most need to know — which branches are invisible, and how far each branch’s visibility actually extends.

Two changes fix it.

Track per location, from within its catchment. A branch’s rankings should be measured from the area it serves, not from your head office and not from a national average.

Use a grid, not a point. Sample rankings from a spread of points around each location. What you are looking for is the radius at which you stop appearing.

Figure 1

Branch A — real coverage

4 3 2 3 5 3 2 1 2 4 2 1 1 1 3 3 2 1 2 4 5 4 3 3 6

Branch B — doorstep only

– – – – – – – 14 – – – 12 1 11 – – – 13 – – – – – – –

Two branches, both reporting an average position of roughly three. The one on the left owns its catchment. The one on the right ranks on its own doorstep and nowhere else, and needs completely different work. An average hides the difference entirely.

A branch that ranks first at its own front door and vanishes half a mile away has a very different problem from one that ranks fourth everywhere across its catchment — and an average position of “third” would describe both identically.

Once you can see the shape, the priorities become obvious. Before that, you are guessing.

The same average can describe two completely different businesses

Figure 1 shows what that looks like for two branches. Multiply the same problem across twenty, and the arithmetic gets more interesting, not less.

Take a hypothetical business with twenty branches, currently reported as a single number: a national average local pack position of 4.1.

Read as one figure, that sounds like a business performing consistently in the low-to-mid pack. Worth a general polish, nothing urgent.

Re-run the same twenty branches through a catchment grid instead of a single point, and a plausible breakdown looks like this. Eleven branches show real coverage across their catchment, the shape Branch A takes above. Six rank only at their own front door, Branch B’s shape. Three do not clear the local pack from anywhere in their catchment, including the address itself.

Eleven strong, six doorstep-only, three invisible. Depending on exactly where those individual numbers land, the average across all twenty can still read as “4.1.”

That is not a flaw in averaging as arithmetic. It is a description of what averaging does. It collapses many numbers into one, which is precisely the operation that destroys the information a multi-location business needs in order to act.

A branch ranking fourth everywhere and a branch ranking first at its own door and nowhere else are not the same problem in different clothing. One typically needs broader authority-building across the catchment.

The other needs someone to work out what is different about its own five streets that the rest of its catchment does not share. Usually a stronger local competitor, or a genuine mismatch between the business’s real service area and the one its profile claims.

The three invisible branches are the ones a national average hides most effectively. They contribute almost nothing to the number and get outweighed by branches doing fine.

They are also usually where the next month’s effort should go. Not necessarily the three most commercially important, but the three with the largest gap between commercial importance and visibility — which the grid is the only view that ever shows as a problem at all.

Twenty branches collapsed into one number is a systems problem wearing a marketing costume, in miniature. The costume is the average. What it is hiding is the actual work.

The business profile is the asset, not the website

For local results specifically, the Google Business Profile does more work than the website does. Treat it as a primary asset with an owner, not as a directory listing someone claimed in 2019.

One verified profile per location. No consolidation. A single listing covering several branches loses you the map pack in every catchment but one. Manage them all under one organisation account so access, permissions and reporting are centralised.

Verification takes longer than you expect at scale. Submitting a large batch of new locations at once tends to slow the process rather than speed it up. Plan for it in phases rather than assuming a launch date. There is a real threshold, ten locations, where the process changes shape entirely.

Categories are the highest-leverage field. Primary category more than any other — the profile optimisation guide works through how to choose one, and the profile statistics show what the measured evidence actually supports. Get it right per location — branches that genuinely differ in what they offer should not share a category by default.

Keep them alive. Hours (including holiday hours, which are a genuine trust signal and a frequent source of bad reviews when wrong), photos, services, attributes, products, posts. A profile that has not changed in two years is a weaker profile.

Watch for unauthorised edits. At scale, profiles get changed by Google, by users, occasionally by a former employee. Someone needs to be alerted when a branch’s hours or phone number change without a ticket. Edits that go further than that — a suspension across several branches at once — are a different emergency, and the suspension recovery guide covers it.

Verifying profiles one at a time stops being necessary above ten locations

Google’s Business Profile Manager has a bulk path for exactly this problem, and the eligibility rule is worth knowing before assuming you need it, or don’t.

Bulk verification requires ten or more profiles from the same business, submitted as a single spreadsheet inside Business Profile Manager’s Verifications tab rather than the individual location dashboard.

Google’s instructions for verifying profiles in bulk are specific that uploading the spreadsheet does not by itself submit anything. The request still has to be filed through Verifications, then Chain, then Start. The spreadsheet has to list every location the business manages, not a shortlist of the easy or urgent ones. Service-area businesses aren’t eligible for the bulk path at all.

Below ten locations, or with a service-area business at any size, verification happens the way it happens for one location. Individually, sometimes still by video call with an authorised representative standing where the profile says the business is.

Google states only that it will contact you if it needs more information, not a guaranteed turnaround. Build slack into any launch plan that assumes verification will be quick at either scale.

That threshold has a practical planning consequence. Launching or rebranding fewer than ten locations at once means budgeting for individual review timelines, location by location. Ten or more, and the batch goes through Google’s bulk process together — reviewed as one submission, not necessarily resolved any faster branch for branch, but at least not filed fifty separate times by fifty separate people.

The other structural tool sits above individual profiles entirely. Google’s developer documentation on managing locations at scale describes location groups: collections of profiles that let an account run bulk tasks, such as verification or permission changes, across many locations at once, grouped however makes operational sense: by chain, by region or by category. A single location can belong to more than one group.

Google recommends granting access through user groups rather than adding personal accounts to a location group one at a time, on the stated grounds that it is “an easier way to manage at scale.” For a business already juggling which manager should be able to edit which branch, that is the actual answer to a permissions question a spreadsheet usually cannot solve cleanly.

None of this replaces the field-level work the Google Business Profile optimisation guide covers — categories, hours, services and photos still have to be right, one location at a time. It just determines how many separate actions it takes to get there.

Google also documents a separate process for transferring locations between accounts or location groups entirely, requiring the destination account to hold at least manager-level access first. Google doesn’t spell out why a business would use it. The obvious candidates are a chain being acquired, sold in part, or reorganised across franchise groups: worth knowing the mechanism exists before one of those situations arrives, not during it.

The evidence says finish twenty profiles before deepening one page

Whitespark’s 2026 Local Search Ranking Factors survey, which for 2026 shows the same panel scoring the same factors it scored in 2023, found a specific pattern in what moved.

The factors that rose fastest were Business Profile completeness signals. Presence of GBP predefined services climbed from 81st to 22nd, keywords in the GBP services field rose 75 places, proper hours set on GBP rose 64 places, and “business open at time of search” is new to the top five entirely.

The factors that fell were the ones that take the most time to produce. Internal links from the GBP landing page dropped 65 places, links out to authority sites fell 64, and the volume of content on service pages fell 40.

Whitespark’s commentary alongside the data notes that review and behavioural signals grew in weight over the same period, while citation-signal weighting continued a slow decline. One more sign of where the panel thinks the leverage has moved — and a reason a disciplined review system earns its place in a limited hour as much as a complete profile does.

For a single-location business, that argues for finishing the profile before writing a tenth service page. It’s a recommendation rather than a measurement: the survey scores practitioner judgement, not a controlled test of cause and effect. For a business with twenty locations and a small team, the same finding compounds rather than simply repeating.

An hour spent correcting a category, filling in the services field or fixing stale hours is an hour spent once and finished. An hour spent writing content genuinely specific to one location — real staff, real parking detail, real local proof rather than a template with a town name changed — is an hour spent on one twentieth of the estate.

None of this argues against location content: a business that never says anything specific about one of its branches keeps losing to the one that does. It is an argument about sequencing.

Bring twenty profiles to genuine completeness first. That is achievable as a modest, repeatable weekly task, and it moves the whole estate at once. Deep, differentiated content for twenty pages is a far larger undertaking, realistically done a few branches at a time — whichever ones the grid already flagged as furthest behind, not whichever ones happen to be easiest to write about.

The full movement between the two surveys, including which factors rose and fell by how much, is broken out on this site’s local SEO statistics page.

Location pages need a reason to exist

None of this makes location content optional. It only orders it behind profile completeness, which is cheaper and faster to finish. The most common multi-location content failure is a template with variables in it. Town name, address, phone number, a paragraph of boilerplate, a map embed. Fifty of them.

Google sees fifty near-duplicate pages. It picks one, or none, and the rest sit unranked. Worse, they compete with each other, so a query the business should own returns three of its own weak pages rotating in and out.

The test for a location page is straightforward: could this content appear on any other branch’s page unchanged? If yes, it is not location content.

Element	Templated version	Version that earns the page
Heading	“[Service] in [Town]”	The same, which is fine — the heading was never the problem
Team	“Our expert team”	Named staff, their specialisms, how long they have been there
Getting there	An embedded map	Parking, which floor, nearest station, where the entrance actually is
Services	The full company list, repeated	What this branch does that others do not, and what it does not do
Area	A stuffed list of nearby postcodes	The neighbourhoods and landmarks people actually use to describe the area
Proof	Company-wide testimonials	Reviews from this branch, work done in this catchment
Schema	`Organization`, repeated	`LocalBusiness` with this location’s real NAP, hours and coordinates

What actually differentiates:

The people. Named staff, their specialisms, how long they have been there. This is the single most differentiating and most under-used thing available to you, and it is free.
The specifics of this place. Parking, public transport, accessibility, which floor, what the building looks like, where to find the entrance. Genuinely useful and impossible to templatise.
What is different here. Services this branch offers that others do not. Equipment, stock, opening hours, languages spoken.
The catchment in its own terms. The neighbourhoods, landmarks and adjacent towns people actually use to describe the area — not a stuffed list of place names, which reads as spam to a person and increasingly to a machine.
Local proof. Reviews from this branch’s customers, work done in this area, local partnerships or sponsorships.
LocalBusiness schema with this location’s real name, address, phone, opening hours and geo-coordinates. Google’s guidance is to use the most specific sub-type available — Dentist, Restaurant, HealthClub — rather than the generic parent, and the structured data implementation is covered step by step here.

If you genuinely cannot write something specific about a location, that is worth noticing. It usually means nobody at head office knows much about that branch, which is a bigger problem than the page.

Structure them properly. A flat list of fifty pages hanging off the root is weak. A hierarchy — region, then city, then branch — gives search engines a map of your geography, spreads authority sensibly, and gives you pages that can rank for the broader “in [city]” queries that no single branch page will ever win.

Consistency is an operations problem

Name, address and phone number need to match across your site, your profiles and the major directories. Everyone knows this. At scale it stops being a marketing task and becomes a data-governance one.

The realistic version:

Hold one internal record that is the truth. A single source — a spreadsheet is fine to start — with the exact, agreed formatting for every location. Not “whatever is on each page right now”.

Fix the sources that matter. Chasing every obscure directory is a poor use of time. Your own site, your profiles, the major aggregators and the significant industry directories in your sector are where the effort belongs.

Have a process for change. A branch moves, a number changes, a suite number gets added. Without an owner and a checklist, that change reaches the website and nowhere else, and six months later there are three versions of the address in circulation.

The mechanics of which directories, aggregators and platforms are actually worth that ongoing effort, and which ones are legacy busywork the current evidence no longer supports, are covered in full in the citation-building guide. The point specific to having several locations is narrower. A single-location business fixes its listings once. A multi-location business generates new inconsistencies continuously, as branches open, close, move and change numbers — which is why the process needs an owner rather than an occasional audit.

Inconsistency is rarely a single dramatic error. It is drift, and drift is a process failure.

Reviews are a system, not a campaign

Reviews carry real weight in local rankings and enormous weight in whether someone actually chooses you. At one location, review generation is a habit. At twenty, it has to be a system, and it has to be per-location — because the review profile that matters to a customer is the one attached to the branch they are considering.

What that system needs:

A consistent ask, built into the point in the customer journey where satisfaction is highest, and the same at every branch.
Per-location visibility. Volume, average rating and recency, per branch, reviewed monthly. Aggregate review scores hide the branch quietly collecting one-star reviews.
Responses to all of them, and quickly to the bad ones. A well-handled complaint is more persuasive to a future customer than a five-star review, because it shows what happens when something goes wrong.
A feedback loop into operations. Recurring complaints at one branch are an operations signal, not a marketing one. The mechanics of asking, responding and routing at volume are in the local review strategy guide. The most valuable thing a review programme produces is often not the reviews.

Never incentivise, never gate, never buy. Google’s prohibited and restricted content policy treats paid or incentivised reviews as fake engagement, and the stated consequences run to a profile being blocked from receiving new reviews for a period, or having existing ones unpublished. The downside is permanent, and it is easily detected.

Structure content so it can be quoted

One addition that has become worth the effort. Local questions are increasingly answered by AI systems reading your pages rather than by a user clicking through to them, and those systems quote sources. What is actually measurable about that shift, as opposed to asserted, is set out in the guide to local SEO for AI search.

The practical implication is unglamorous: answer questions directly and in full sentences. A page that says “Our Leeds branch is open until 8pm on Thursdays and has free parking for ninety minutes” can be quoted. A page that conveys the same information through an hours table and an icon cannot.

This is not a new discipline. It is the same clarity that helps a human skimming on a phone, which is why it is worth doing regardless of what the answer engines end up doing.

What to do first

In order, because each one makes the next more effective:

Fix the reporting. Get per-location, grid-based visibility. Until you can see which branches are failing, everything else is guesswork.
Audit the profiles. One per location, verified, correct categories, current hours, real photos. This produces results faster than website changes.
Fix the worst three locations. Not all fifty. The three with the largest gap between commercial importance and visibility. Learn what works, then templatise the approach — not the content.
Rebuild the location pages with a hierarchy and genuinely differentiated content, starting with the branches that matter most.
Put the review system in place and review it monthly, per branch.

A branch that ranks and still does not convert is a different problem again, and one that gets misdiagnosed as a visibility failure more often than anything else on this list. Speed of response and what the location page does once someone lands on it are where that money actually goes.

The temptation with multiple locations is to do a little to all of them at once. Doing it properly for three, learning what actually moves, and then rolling out a process beats a shallow pass across fifty every time.

What that looked like across a real estate group’s branch network is written up in visibility across every location, and the sector view is on the multi-location businesses page.

Questions

Should each location have its own Google Business Profile?: Yes. Every location with a physical address customers can visit, or a defined service area, needs its own verified profile. Never consolidate several branches into one listing — you lose the map pack in every catchment except the one the listing is registered in. Manage them under a single organisation account so permissions and reporting stay sane.
Do I need a separate page for every location?: Yes, but only if each page can justify its existence. A location page that differs from the others by a town name and a phone number is a duplicate with a substitution, and Google treats it as one. If you cannot say something genuinely specific about a location — its team, its stock, its parking, its catchment — the honest answer is that you have a content problem to solve before you have a page to publish.
How do I stop location pages competing with each other?: Give each one a distinct geographic target and genuinely distinct content, and link them through a proper hierarchy rather than a flat list. Cannibalisation between location pages usually shows up as several branch pages rotating for the same city query, none ranking well. The fix is clearer targeting and better differentiation, not more pages.
How important is NAP consistency for multi-location SEO?: It matters, and at scale it is an operations problem rather than a marketing one. Name, address and phone number must match across your site, your profiles and the major directories. The realistic goal is not perfection everywhere but consistency in the sources that matter, plus a single internal record that is the agreed truth and a process for propagating changes when a branch moves or a number changes.
How do I track local rankings across many locations?: By location, not as an average. Local results are computed from where the searcher is standing, so a national average position is a number that describes nobody. Track rank per branch from within its own catchment, ideally on a grid of points around each location, so you can see how far the visibility extends rather than just whether it exists at one spot.
Is there a minimum number of locations before Google's bulk verification tool applies?: Yes. Google's own requirement is a spreadsheet with ten or more profiles from the same business, submitted through Business Profile Manager's Verifications tab rather than left as an upload. The spreadsheet must list every location the business manages, not a shortlist, and service-area businesses aren't eligible for the bulk path at all. Below ten locations, verification happens individually, the same way it does for a single-location business.
What is a location group in Google Business Profile, and is it worth setting one up?: A location group is Google's mechanism for running bulk tasks, such as verification or permission changes, across many profiles at once, organised however suits the business: by chain, by region or by category. A single location can sit inside more than one group. Below roughly ten locations the overhead of setting one up rarely pays for itself. Above that, an organisation account built around location groups and user groups, rather than adding individual people to each profile one at a time, is how Google itself recommends managing access at scale.
With twenty locations and limited time, should effort go into profile completeness or into content?: Completeness first, on the current evidence. Whitespark's 2026 practitioner survey shows the factors that rose most between 2023 and 2026 are Business Profile completeness signals, such as predefined services, keywords in the services field and accurate hours, while generic content volume and outbound linking fell. At one location that already argues for finishing the profile before writing another page. At twenty locations the same hour is spent once and repeated across the whole estate for free, which makes the case stronger, not weaker.
Is there research on how many location pages is too many before a flat structure stops working?: No substantial study measuring a specific numeric threshold was identified in the sources reviewed on 8 September 2026. What is well established is the mechanism rather than the number: search engines need a way to understand how pages relate to each other, and a flat list of fifty near-identical URLs gives them none. In practice the trigger is a symptom, not a count. Once several location pages start rotating for the same query, or a whole region has no page able to rank for the city-wide search, that is the signal to introduce a hierarchy, whatever the location count happens to be at that point.
How is NAP consistency at scale different from a one-off listings clean-up?: It is a different kind of problem, not a bigger version of the same one. A single-location business fixes its listings once. A multi-location business generates new inconsistencies continuously, as branches open, close, move and change numbers, which turns the work into an ongoing operational process rather than a project with an end date. Which directories and aggregators are actually worth that ongoing effort is a separate question, covered in the site's citation-building guide.