
The Scenario: A Multi-Branch Business Competing for One City at Best
Consider a Johannesburg industrial equipment supplier with depots in Germiston, Pinetown, and Bellville. Its site has one 'Contact Us' page listing all three addresses in a paragraph, plus branches as footer text. When someone searches 'compressor supplier near Bellville', Google has no reason to surface the Bellville depot-there isn't a page. The site competes for one generic city term at best, and at worst confuses crawlers about which location serves which query. This is the common trap: treating local SEO as a marketing afterthought rather than a design deliverable.
For South African multi-branch and service-area businesses, local visibility depends on how well the website encodes physical locations into its structure. That means modelling each branch or service area as a distinct page entity, not a paragraph buried on a contact page. Below is a build-level playbook: designing location pages that carry machine-readable signals, align with Google Business Profile (GBP), and avoid doorway-page pitfalls.
What 'Local' Actually Means to a Crawler (and Why Design Decides It)
A search engine does not 'see' your branch. It sees URLs, headings, structured data, internal links, and text. Local relevance is inferred from those elements. Design choices-template structure, URL patterns, navigation hierarchy-determine whether each location is a crawlable, indexable entity or an invisible footnote. Tabs or accordions collapse multiple entities into one URL, weakening location-specific ranking potential. A dedicated page per location, linked from a locations index and marked up with LocalBusiness schema, gives each branch its own addressable node.
Tip: Think of each location as a product variant-it needs its own URL, title, description, and structured data. The design system should support that pattern.
Modelling a Location as a Page, Not a Paragraph
Define a location content type in your CMS with fields for branch name, street address, suburb, city, province, postal code, phone, opening hours, geo-coordinates, service area, and a unique intro paragraph. This structured data feeds both the rendered page and the JSON-LD. The template renders fields consistently while allowing unique content per location-local team bios, area-specific case notes, or directions from landmarks.
For service-area businesses without a storefront (e.g., mobile IT support across Cape Town's Southern Suburbs), use service-area pages: state areas served, optionally embed a map polygon, and use LocalBusiness markup with areaServed rather than a physical address. Never imply an office where none exists.
The Location Template: Which Elements Every Branch Page Must Carry
- Unique H1 with the location name (e.g., 'Compressor Sales and Service in Bellville').
- NAP block in consistent format, marked up with schema.
- Opening hours in human- and machine-readable form.
- Embedded or static map with directions link.
- Local content block (200-300 words) on area-specific services and landmarks.
- Internal links to service pages and nearby locations.
- Breadcrumb navigation with BreadcrumbList schema.
- Call-to-action (phone, directions, form) above the fold.
The NAP Handshake Between Your Site and Google Business Profile
NAP consistency starts with your website. The name, address, and phone number on your location page must match the corresponding GBP listing exactly-including abbreviations and suite numbers. A mismatch ('St' vs 'Street', different phone formats) can weaken local ranking signals. Design your template to pull NAP from a single source of truth (the CMS fields) and render it identically across footer, contact page, location page, and schema, then update GBP listings to match.
Warning: Inconsistent NAP between site and GBP is one of the most common local SEO issues we see. It can undermine even the best-designed location pages.
Where Thin City Pages Tip Into Doorway Territory
Scaling location pages without unique content is risky. Google's spam policies explicitly target doorway pages that exist only to rank for specific queries without adding value. Creating 50 city pages by swapping the city name in a template manufactures duplicates-a real danger for franchises. Enforce a minimum uniqueness threshold: at least 30% of page content (excluding NAP block and standard template elements) must be unique per location-local staff, community involvement, area-specific services, or local testimonials. If a location cannot meet that threshold, consolidate it into a regional page or a single page with clear sections.
Scaling a Franchise Template Without Manufacturing Duplicates
Design a template with optional fields franchisees can fill: local manager name, photo, short bio, local case study, community sponsorships, and localized service descriptions. Use conditional rendering to hide empty fields rather than display placeholder text. For locations sharing a service area, use one page listing multiple suburbs with a clear primary service hub. Add canonical tags for paginated or filtered location lists, audit for duplicate content with tools like Siteliner or Copyscape, and be ready to merge or de-index thin pages.
Local Internal Linking: Location Pages, Service Pages and the Locations Index
Create a 'Locations' index page listing all branches with links. Each location page should link to relevant service pages (e.g., 'Compressor Sales' and 'Compressor Service') and nearby locations. Service pages should include an 'Available at these locations' block linking back. This reciprocal linking distributes authority and helps crawlers understand local structure. Use descriptive anchor text: 'Compressor service in Bellville' rather than 'click here'.
POPIA-Aware Form and Consent Design in Local Page Templates
Sources
- Google Business Profile Help - Improve your local ranking on Google
- Google Search Central - Local business (LocalBusiness structured data)
- Google Search Central - Spam policies (doorway pages and scaled content abuse)
- Google Search Central - Creating helpful, reliable, people-first content
- South African Information Regulator - POPIA overview




