Local SEO for one location is a checklist. Local SEO for twenty is an operations problem, and it fails for operational reasons: nobody owns the Business Profiles, the location pages were generated from one template with the town name swapped, and reviews accumulate at whichever branch has a manager who cares.
At seothumb.com, multi-location local SEO starts with an audit of every profile and location page. You get a forecast per branch before any retainer is discussed. One senior consultant then owns the whole estate, so no branch quietly falls behind.
Key takeaways
- The Google Business Profile drives most map pack rankings, and the primary category is the single biggest lever per location.
- Build one location page per address with content that is only true of that branch, not a template with the town swapped.
- Fix NAP data at the aggregators first, then major directories, using one canonical address format everywhere.
- Run reviews as a per-location workflow and track rankings on a geo-grid so weak branches become visible quickly.
Here is how to run it properly across a real estate of locations.
The Business Profile Is Most of the Ranking
For map pack results, the Google Business Profile does more work than the website. Prioritise accordingly. This is why seothumb.com corrects aggregator records before touching a single individual directory listing.
Primary category is the single biggest lever. Not a close call. A dental practice categorised as “Dentist” and one categorised as “Cosmetic dentist” compete in measurably different result sets. Choose the primary category to match the highest-value query you want to win, then add secondary categories for the rest. Check what the businesses currently ranking above you have chosen.
Complete every field. Services, attributes, opening hours including holiday hours, description, opening date, and the full products list where the category supports it. Incomplete profiles rank worse, and the effect compounds across a whole estate.
Photos, per location, genuinely. Exterior shots so people recognise the building, interior, team, product. Stock imagery repeated across twenty locations is worse than fewer real photos.
Service area versus storefront. If customers do not visit the address, set it as a service-area business and hide the address. Listing a storefront that is actually an office is a guideline violation and a suspension risk. Google sets out these rules in its guidelines for representing your business on Google.
Assign an owner. The most common failure across an estate is not a bad profile, it is an unclaimed or half-claimed one that nobody has logged into for a year.
Location Pages: One per Address, and Actually Different
The two failure modes are opposite and both common. In every seothumb.com estate report, weak branches are listed by name so the fix has a clear owner.
One page listing every location. It cannot rank for “[service] in [town]” for twenty towns, and it gives the map pack nothing to associate with each address.
Twenty pages from one template with the town name substituted. Technically distinct URLs, functionally duplicate content, and Google treats them accordingly.
A location page that earns its place contains things that are true only of that location:
- The actual address, phone number and hours for that branch, matching the Business Profile exactly
- An embedded map and genuine directions — landmarks, parking, transit
- The staff at that location, named where the business allows it
- Services offered there, since estates are rarely uniform
- Reviews from that location
- Photos of that building
- Anything locally specific: neighbourhoods served, local partnerships, parking arrangements
The test: if you swapped the town name out, would the page still make sense for a different branch? If yes, it is a template, not a location page.
Each of these carries LocalBusiness markup with fields matching the profile. Google’s LocalBusiness structured data documentation lists the required and recommended properties.
NAP Consistency Is About the Aggregators
Name, address and phone consistency matters less as a direct ranking factor than it used to, and still matters because inconsistent data propagates.
The important detail: most directory listings are populated from a handful of data aggregators. Correcting a hundred individual directories while the aggregators still hold an old phone number means the old number returns.
Fix the aggregators first, then the major directories, then the long tail. And decide the canonical format once — “Suite 4” or “Ste 4”, “Street” or “St” — and apply it identically everywhere including the website footer and the schema.
Suite numbers cause a specific problem for estates with multiple businesses at one address: they are frequently dropped by directory software, merging two distinct locations into one record.
Reviews as a Workflow, Not a Campaign
Review velocity and recency both matter, and both come from process rather than effort.
What works at scale:
- A single moment of ask, built into the existing customer interaction — at checkout, on completion, in the follow-up email.
- A direct review link per location, short enough to print on a card or put in an SMS.
- A response commitment. Every review answered within a few days, negative ones included and especially. Response rate is visible to customers and correlates with conversion from the profile.
- Per-location reporting, so the branches that never ask become visible.
What to avoid: review gating — asking customers privately how they feel and only routing the happy ones to Google. It is against Google’s policies and it is the kind of thing that gets an entire estate’s reviews removed at once.
Track on a Grid, Not from One Point
A single citywide rank for “dentist near me” is close to meaningless. Map pack results vary street by street, and the whole point of a multi-location estate is covering specific catchments.
Geo-grid tracking samples positions across a grid of coordinates around each location, which tells you the thing that actually matters: how far from each branch does your visibility extend, and where does a competitor take over. On an estate you want the grid per location, rolled up so you can compare branches.
The pattern that shows up almost immediately is that one or two branches are dragging the average, usually for a mundane reason — a miscategorised profile, an unclaimed listing, no reviews.
When a geo-grid shows one branch lagging, these are the usual causes and the first fix to try.
| What the grid shows | Likely cause | First fix |
|---|---|---|
| Weak visibility even close to the branch | Wrong primary category or incomplete profile | Match the primary category to the main query and complete every field |
| Branch missing from the map pack entirely | Unclaimed, unverified or suspended profile | Claim the profile, assign an owner and check for guideline issues |
| Visibility drops sharply a short distance away | Few or old reviews compared with nearby competitors | Install the review ask and a direct review link at that branch |
| Two branches appear as one listing | Suite number dropped by directory software | Correct the aggregator record with the full, canonical address |
| Map pack fine, organic local results weak | Templated location page with no unique content | Rewrite the page with branch-specific details and LocalBusiness markup |
What to Do in What Order
- Audit every profile. Claimed, categorised, complete, correct. This alone frequently moves rankings before anything is built.
- Fix NAP at the aggregators, then the major directories.
- Build location pages with genuinely distinct content, and mark them up.
- Install the review workflow at whichever branches are weakest.
- Set up geo-grid tracking per location so there is a baseline before anything else changes.
- Then work on the wider site — service pages, internal links, technical health — which is where organic (non-map) local rankings come from.
The order matters because steps 1 and 2 are cheap and fast, and they frequently produce the first movement.
This is the sequence behind local SEO engagements here, and it scales from three locations to sixty. If you want a read on your estate before committing to anything, send us your domain — the free audit covers profile completeness and location page architecture alongside the technical checks.
For more on ranking branches, browse our local SEO articles, and see the technical SEO guides for the site health work behind organic local rankings. Location pages are a template problem at heart, which our guide to template-level on-page SEO covers, and measuring SEO revenue shows how to tie branch visibility to real enquiries.
Frequently Asked Questions
Does Every Location Need Its Own Google Business Profile?
Each physical location that serves customers in person, with its own staff and hours, should have its own verified profile. Offices that customers never visit should not be listed as storefronts. Service-area businesses can use one profile with the address hidden, defining the areas they serve instead.
Can We Use One Template for All Our Location Pages?
You can use one layout, but not one block of copy. The structure can be shared while the content changes: address, hours, directions, staff, services offered there, local reviews and real photos. If a page still makes sense after swapping the town name, it needs more location-specific detail.
How Long Does Multi-Location Local SEO Take to Show Results?
Profile fixes and NAP corrections are cheap and often produce the first movement in map pack visibility. Location pages and review workflows take longer because they depend on indexing and steady review volume. Setting up geo-grid tracking first gives you a baseline, so you can see which change moved which branch.
