6 April 2026 , Blackgate
Multi-location SEO fails when every store page is the same blurb with a different suburb swapped in. Search systems reward pages that have clear local relevance; users reward pages that answer this opening hours, this team, and this service area. The goal is not word count - it is non-interchangeable value per place.
One entity, many places - get the basics right
Use one Google Business Profile strategy you can defend: one listing per real-world location with matching name, address, and phone (NAP) on the site. Inconsistent NAP between site, maps, and citations confuses people and data layers alike.
Location URLs should be stable and predictable: /locations/{city}/ or a clear path your CMS can support long term. If you rebrand or move, plan 301s and update citations - not only the website.
Duplicate content: what actually hurts
Franchise groups often start with one strong template and then “roll it out” with find-and-replace on the suburb. Search systems and people both notice when the only difference is the H1: you have not added local proof, you have added keyword variants of the same page.
- Copy-paste intros with only the city name changed - often reads as thin and offers no new entities (staff, services, offers).
- Single-page “we serve 50 suburbs” lists with no depth - better as hub + child pages with real local detail, or a honest service-area model if you do not have physical presence per suburb.
- www vs params for the “same” location - pick one canonical URL per location.
A sensible template (hours, CTA, map, reviews, FAQs) is fine; the body should still carry something you could not publish on any other site without lying.
Thin pages: raise the bar
Each location page should cover at least: address and map, contact, unique photo or proof where possible, local schema (where appropriate), and FAQs that reflect real questions (parking, booking, which services are offered here).
If a location is truly identical, merge into a regional page and list branches - but only when that matches how customers search and decide.
Internal linking and topical support
Point local hub and parent service pages at each other: the Sydney page should not be an island. A light topic model (see how to build a topical map with pillars and clusters) helps authority flow without keyword stuffing. For sitewide patterns, site structure and internal linking for new sites is a good companion.
Frequently asked questions
How much unique text per location page?
Enough that the page is genuinely useful for a local search - not a word-count quota. If two pages differ only in city name, merge or differentiate.
Subdomains vs subfolders for locations?
Often subfolders under one domain are simpler for authority; subdomains can work with strong linking - pick one model and be consistent.
Do I need a page for every suburb?
Only when you have a defensible reason to rank there - service area, or a real location. Doorway pages for places you do not serve backfire.
What about schema?
Use LocalBusiness (or the appropriate subtype) accurately - see schema markup basics for articles and FAQs for a broader read.
Where do I start?
Audit GSC and GBP for the top ten locations, fix NAP/URL consistency, then improve the thinnest high-traffic pages first.