Why One Business, Several Branches, Still Needs Separate Pages

Google ranks pages for specific places, not businesses in general. A search for “dentist Botany” or “gym Albany” returns results tied to that suburb, and a single generic “our locations” page rarely competes against a dedicated page built around that suburb’s search intent.

Auckland makes this more pronounced than most New Zealand cities. The region stretches from Warkworth to Papakura, and a customer in Henderson is not going to drive to your Half Moon Bay branch when a competitor’s West Auckland page shows up first. Distance and traffic matter here in a way they do not in smaller towns, so each branch needs to win its own patch of the map.

The Difference Between a Service-Area Business and an Actual Branch

Before you build location pages, work out which type of business you actually are, because the right structure differs.

• Service-area business: you travel to the customer (plumbers, electricians, cleaners, landscapers) and have no public-facing premises in each suburb. For this model, read our guide on how many suburb pages a service-area business actually needs, since the advice below is written for businesses with real, visitable branches.
• Multi-branch business: you have a physical premises at each location that customers walk into or book an appointment at (clinics, salons, gyms, retail stores, showrooms). This is the model this article covers.

Mixing the two approaches is one of the fastest ways to create thin or duplicate pages, because a service-area template padded with a real branch’s details (or the reverse) rarely reads as genuine to either Google or the customer.

What Each Location Page Needs to Avoid Thin Content

A location page that only swaps the suburb name into an identical template is what search engines treat as duplicate or near-duplicate content. Each page needs enough unique substance to justify its own existence.

1. A real street address and parking or transport notes specific to that branch, not a generic “easy parking available” line reused everywhere.
2. Branch-specific hours, including any differences for public holidays, half-days or seasonal changes.
3. The team at that branch, with names and photos where staff are comfortable with that, since this is one of the strongest differentiators between near-identical pages.
4. Services or stock that differ by branch. If one site offers a service the others do not (a larger studio, a specific treatment, extra parking for trailers), say so.
5. Local reviews pulled through to that specific page, not a mixed feed from every branch.
6. A map embed centred on that branch, not a zoomed-out map of all branches together.
7. Directions relevant to that suburb, such as which motorway exit to use or which side street has free parking.

Structuring URLs and Navigation So Customers Find the Right Branch

Keep the structure simple and consistent so both customers and Google can predict where a branch page lives.

• Use a clean URL pattern such as yoursite.co.nz/locations/albany rather than burying branches under unrelated paths or query strings.
• Add a locations index page that links out to every branch, with a short line of unique copy for each, not just a bare list of suburb names.
• Put a location switcher in the main navigation if you have more than two or three branches, so a visitor on the wrong branch page can move to the right one in one click.
• Avoid auto-redirecting visitors based on guessed location. Let them choose. Auto-redirects based on IP address frequently send people to the wrong branch and frustrate anyone checking hours before they leave home.
• Link each branch’s blog mentions and case studies back to its own page, rather than always pointing to the homepage, to build genuine relevance signals for that specific location.

One Google Business Profile Per Location, Linked Correctly

Every physical branch needs its own Google Business Profile, not a single listing covering all sites. This is where most multi-branch Auckland businesses lose visibility without realising it.

• Verify each branch separately through Google’s standard address verification process. A shared or duplicate listing risks suspension.
• Link each profile to its matching location page, not to the homepage. A GBP that points to the homepage gives Google no page-level signal to connect the listing to that specific branch’s content.
• Keep NAP (name, address, phone) details identical across the website, the GBP listing and any directories your business appears in. Inconsistent details, even something as small as “St” versus “Street,” can weaken how confidently Google associates the two.
• Upload branch-specific photos to each profile rather than reusing the same photo set across all of them.

For a wider look at how your website and your Google Business Profile should work together, see our breakdown of Google Business Profile vs website for Auckland businesses.

LocalBusiness Schema: Marking Up Each Branch Properly

Structured data will not fix thin content on its own, but it does make it explicit to search engines which page belongs to which address, which helps your listings display correctly in local search results.

• Add LocalBusiness schema to each location page, with that branch’s own address, phone number, opening hours and geo-coordinates. Do not use one schema block with a list of all addresses crammed into it.
• Use the correct sameAs property to link each branch’s schema to its own Google Business Profile URL, not to a shared company page.
• Check your markup with Google’s Rich Results Test after publishing, since a single misplaced field can stop the whole block from validating.

If schema markup is new territory for your team, our guide to schema markup for small business covers the basics before you tackle a multi-location setup.

Common Mistakes That Trigger Duplicate Content Problems

Most of the duplicate content issues we see in multi-branch Auckland sites come down to the same handful of shortcuts.

Mistake	Why it hurts rankings
Same paragraph with only the suburb name swapped	Reads as duplicate content across every branch page
One shared Google Business Profile for all branches	Google cannot confidently rank the right branch for the right suburb
Location pages with no unique photos or staff details	Pages look interchangeable, so none stands out in search results
Publishing the same blog post on every branch’s page or subdomain	Link value gets split across competing versions instead of one strong page
Inconsistent NAP details between site, GBP and directories	Weakens the link between your listing and your website in Google’s eyes

A small amount of overlap between branch pages (shared brand copy, a shared “about us” section, a shared booking system) is normal and will not cause harm on its own. The problem is when the overlap is the entire page.

FAQ

How many Auckland branches before I need separate location pages?

Two is enough to justify it. Even with just two branches, each one should have its own page, its own Google Business Profile and its own schema markup so customers near either site can find the right one.

Can I use one page with a suburb dropdown instead of separate pages?

A dropdown can work for navigation, but the underlying content still needs to be separate, indexable pages. A dropdown that reveals the same text with a different heading will not satisfy either Google or a customer comparing branches.

Will separate location pages cause duplicate content penalties?

Not if each page has genuinely unique details: address, hours, staff, photos, local reviews and any branch-specific services. The penalty risk comes from copying the same paragraph across every branch, not from having multiple location pages.

Should each branch have its own phone number?

Where practical, yes. A dedicated phone number per branch makes call tracking easier and strengthens the NAP consistency between that branch’s website page and its Google Business Profile.

What if one branch is much smaller than the others?

Give it a page anyway, scaled to what is genuinely true of that site. A shorter, honest page beats an inflated one that repeats claims that do not apply to that branch.