Opening a second location should be a growth milestone — not the beginning of an SEO headache. Yet for most NZ multi-location businesses, expansion triggers a cascade of ranking problems: pages competing against each other for the same keywords, Google unsure which location to show for a given search, and a site structure that worked perfectly for one branch suddenly collapsing under the weight of five.
Multi-location SEO is fundamentally different from single-location SEO. The rules change. The technical requirements multiply. And the consequences of getting it wrong — duplicate content penalties, cannibalised rankings, confused customers — can undo years of organic search progress in weeks. According to Moz's guide to multi-location SEO, the most common mistake businesses make is treating each location page as a clone of the next, which signals to Google that your content lacks originality — and suppresses rankings across the board.
Why Multi-Location SEO Breaks (And How to Prevent It)
When a business with one location adds a second, the instinct is to duplicate what worked. Create a new /auckland page. Copy the content from /wellington. Swap the city names. Ship it. Within weeks, both pages start losing rankings — not because the content is bad, but because Google can no longer determine which page is the authoritative result for queries that could match either location.
This is the cannibalisation trap, and it is the single most expensive SEO mistake multi-location businesses make. Two pages targeting identical keywords — differentiated only by location name — force Google to choose one or suppress both. Neither outcome serves the business. The fix is not to avoid creating location pages — it is to build them with enough differentiation that Google sees distinct entities rather than copies.
As reported by Search Engine Journal, successful multi-location SEO treats each location page as a standalone business website in miniature — with unique content, unique value propositions, unique imagery, and unique local signals. The pages share a brand, but they must not share a template.
The Location Page Architecture That Actually Works
A multi-location SEO strategy begins with three architectural decisions that determine whether your pages compete or cooperate:
1. Build a Location Hub-and-Spoke Structure
Rather than linking to location pages from the main navigation — which dilutes link equity and creates navigational clutter — use a central "Locations" hub page that links out to each individual location page. This hub-and-spoke pattern concentrates internal link equity on the hub, which Google treats as the canonical entry point for location-based queries about your brand, then distributes authority down to individual location pages through contextual links.
For a Kiwi business with branches in Auckland, Hamilton, Wellington, and Christchurch, this looks like: /locations/ (hub page with unique content about the business's national footprint, a map, and customer testimonials) → /locations/auckland/, /locations/hamilton/, /locations/wellington/, /locations/christchurch/ (individual location pages with unique local content).
This structure signals a deliberate geographic architecture to Google, making it easier for the algorithm to associate each location page with its specific service area.
2. Uniqueify Every Location Page — No Exceptions
The number one reason multi-location pages fail to rank is content duplication. Google's algorithm is sophisticated enough to detect when two pages differ only by city name and a few keywords. Here is what genuinely differentiates a location page:
- Unique staff introductions: Name the people who work at each location. Include their roles, their local community involvement, and — with permission — their photos. Google cannot index a photo of "Auckland branch manager" on two pages and treat them as distinct. It can when the names, faces, and stories are different.
- Localised case studies: A project completed for a client in Wellington belongs on the Wellington page — with the client's permission — not on every location page. These case studies anchor the page in real, verifiable local activity that no other page can claim.
- Location-specific services: If your Hamilton branch offers residential services that your Christchurch branch doesn't, say so. Differences in product availability, service scope, opening hours, and parking accessibility all count as unique content signals.
- Local landmarks and directions: Describe how to find each location relative to landmarks a local would recognise. "Two doors down from the Hamilton Gardens entrance" is content no other page can legitimately carry.
The discipline is simple: if you could swap the city name on a location page and it would still read as accurate, the page is not unique enough to rank independently.
3. Claim and Optimise Every Google Business Profile
For multi-location businesses, Google Business Profiles are not optional — they are the primary signal Google uses to associate your website pages with physical locations. Each branch needs its own verified GBP listing with:
- A unique local phone number (not a call centre forwarding to head office)
- Business hours specific to that location
- Location-specific categories (a Wellington branch might serve government clients, while a Queenstown branch serves tourism businesses — reflect that in secondary categories)
- Location-specific photos — never reuse images across GBPs
- A GBP description that mirrors but does not duplicate the corresponding website location page
Google cross-references GBP data with website content to validate that a location exists where you claim it does. A well-maintained GBP listing for each branch — with regular posts, review responses, and photo updates — reinforces the location signals on your website, creating a feedback loop that improves rankings for both.
Schema Markup: The Technical Layer Most Multi-Location Businesses Miss
If your location pages lack LocalBusiness schema markup, Google is essentially guessing which pages represent physical locations and where those locations are. Schema removes the guesswork. For each location page, implement LocalBusiness schema with:
- @type: LocalBusiness (or a more specific subtype like ProfessionalService, AutomotiveBusiness, or HomeAndConstructionBusiness)
- name: Your business name — identical across all locations to maintain brand entity consistency
- address: The full street address for that specific location, with postal code and country
- geo: Latitude and longitude coordinates — this is how Google maps your page to a precise point on the map
- telephone: The unique local number for that branch
- openingHoursSpecification: Hours for each day of the week at this location
- sameAs: Links to the corresponding GBP listing for this location
Without schema, Google must infer location data from page content — a process that is slow, error-prone, and often results in the wrong location surfacing for the wrong query. With schema, you hand Google a structured data file that says: "This page represents a physical location at these exact coordinates, serving this specific city."
Review Strategy at Scale
Multi-location businesses face a unique review challenge: customers searching for "plumber Hamilton" see review stars from your Hamilton location, not your Auckland one — but your overall brand reputation influences click-through rates across all locations. The strategy balances two layers:
Local reviews drive local rankings. Encourage every customer interaction to generate a review on the GBP listing for that specific location. A Hamilton customer reviewing the Auckland listing because that's what comes up first in Google creates confusion for both the algorithm and future customers. Train staff at each location to guide customers to the correct listing — and make the process frictionless with a QR code at the counter, a link in the post-service email, or a card handed out with the invoice.
Aggregate reviews build brand trust. While local reviews drive local rankings, the total volume and average rating across all locations influences how your brand appears in organic search results. A business with 400 reviews across five locations — each averaging 4.5 stars — carries more credibility in the search results than a competitor with 20 reviews at a single location. Invest in review generation as a system, not a one-off campaign.
How to Know If Your Multi-Location SEO Is Working
Measuring multi-location SEO performance requires segmenting data by location — and most businesses don't. They look at aggregate organic traffic, see it growing, and assume all locations are benefiting equally. In reality, one high-performing location can mask the underperformance of four others.
Set up Google Search Console property sets that isolate each location subfolder (e.g., /locations/auckland/*). Track separately: impressions, clicks, average position, and the specific queries each location page ranks for. When the Christchurch page starts ranking for "Christchurch" queries and the Wellington page starts ranking for "Wellington" queries — rather than the home page ranking ambiguously for both — your architecture is working.
The ultimate test: search for your service + a city you serve. If the page that ranks is your location page for that city — not your home page, not a blog post, and not a competitor — your multi-location SEO is doing its job. If your home page ranks instead, you haven't built enough location-specific authority to convince Google that your location page is the better result.
Multi-location SEO is not about building more pages — it's about building pages that answer questions no other page can. That means unique content, clean architecture, precise schema, and a review strategy that feeds each location's authority independently. Get the foundations right and every new branch you open becomes a new ranking opportunity — not a new ranking risk. Disruptive's SEO team helps NZ multi-location businesses build search strategies that scale with every new branch — contact us to audit your current location architecture and identify the highest-ROI fixes.