Local SEO, South Africa

Suburbs, office parks and PO boxes in South African addresses

South African addresses look simple until you compare them across systems. The same suburb name appears in more than one metro: there is a Rosebank and an Observatory in both Johannesburg and Cape Town, so a listing that drops the city can send a customer across the country. Office parks, industrial townships and shopping centers add building names, unit numbers and shop numbers that are often recorded differently on the profile, the website and the invoice.

For each location I compare the street address, suburb, city, province and postal code everywhere they appear, and look for problems such as:

• a PO Box or Private Bag from the company letterhead used where the physical address belongs
• a business park name used as the street on one listing and left out on another
• a pin placed on the park's main road rather than the building, or behind a security boom customers cannot pass
• a suburb that changed name or boundary, still shown in its old form on directories

In townships and peri-urban areas, a stand number or a nearby landmark may be what customers recognize, and the branch page can add plain directions where the map alone is not enough. Keep postal addresses for invoices and the contact page; a map listing must show a site customers can enter or, for crews who travel, the areas they cover. Clean location data also feeds the structured data on each branch page, described on my schema markup page.

Verification, categories and the name CIPC holds

Verification is Google's call, and South African branches are increasingly asked to film a short clip of signage, interior and proof of management. That is tricky for an unbranded depot, a practice tucked inside a medical center or a unit behind a guarded boom, so the branch gets a shot list in advance and a plan B if Google rejects the first clip.

Names cause more trouble than verification. Your company may be registered with CIPC as a (Pty) Ltd with one name and trade under another, with branches known by suburb. The listing should carry the name customers see on the door, without added keywords. The registered name and registration number belong on your website's legal and contact pages and in Organization markup, where they confirm which entity stands behind the brand. When the CIPC record, invoices, supplier databases and listings disagree, buyers and search engines both hesitate.

Categories follow what each branch actually does. A head office, a trade counter and a service workshop under one brand may each need a different primary category, and secondary categories should never list services a branch does not provide. Hours need the same care: public holidays and temporary closures for maintenance or power interruptions belong in special hours, so customers do not arrive at a locked gate. Changes like these are small, but they are what map results depend on.

Franchise networks, dealer groups and suburb pages

Franchising is a familiar model in South African food, motor, pharmacy, property and retail services, and dealer networks run on similar lines. The tension is always the same: head office wants consistent branding and data, while franchisees need to answer reviews and post updates quickly. I set up a split of roles in which the brand keeps ownership and core fields such as name, categories and website link, and local managers handle photos, posts and replies. A handover step covers outlets that change owner, so profiles are never lost with a departing franchisee. My multi-location SEO page explains the location master behind that split.

Website pages follow the real network. Every branch with premises deserves its own page with address, hours, team, services and directions. Suburb pages without a branch are a different matter. A page for each suburb you deliver to, repeating one paragraph with a new name, is the doorway pattern search engines discourage. A smaller set of area pages earns its place when it says something specific: response times, installation work done nearby that you may describe, access arrangements for estates or complexes, or the team that covers the area.

Where a brand uses Afrikaans, isiZulu, isiXhosa or another local language in its names or local copy, fluent writers at the business or a South African agency should own that wording. The engagement runs in English, and I check that one agreed form appears everywhere.

Reviews under consumer protection rules and POPIA

Ratings carry weight in South African map results and in the decision to call. They also invite shortcuts I do not use: buying reviews, asking staff or family to post, offering a voucher for a rating, or sending invitations only to customers who seemed pleased. These break platform policies, and misleading reviews or testimonials can raise questions under the Consumer Protection Act and the advertising code applied by the Advertising Regulatory Board. Your legal advisor should confirm how those rules apply to your business.

Review requests also touch privacy. POPIA sets conditions for electronic direct marketing, and whether a request sent by SMS, email or WhatsApp falls within them depends on its content and your relationship with the customer. That is a question for your information officer or advisor, and I design the routine around their answer.

A routine that holds up usually includes:

• one neutral request to every customer at a natural point, such as job sign-off or collection
• a named person per branch who replies within a set period, without repeating personal details
• a process for flagging reviews that genuinely break policy, while leaving honest criticism visible
• attention to local complaint and review platforms where customers already discuss your sector

Where your CRM marks a job complete, the request can be sent automatically, which keeps it consistent across branches and removes the temptation to pick and choose.

Calls, WhatsApp chats and directions counted per branch

South African customers who find a branch on the map rarely fill in a form. They phone, ask for a route or start a WhatsApp conversation, and none of that is visible unless someone sets out to capture it. I set up measurement so each branch sees what local search produces:

• profile website links tagged per location, separating map visits from other organic traffic
• call tracking numbers placed where Google's guidelines allow, keeping your main number consistent across the site and directories
• a WhatsApp Business number or link per branch, with a prefilled message naming the location so the first chat can be tagged
• click events for call and WhatsApp buttons, recorded within your cookie consent settings
• a lead source and branch field in the CRM, filled automatically by forms and call systems

Call recordings and chat histories contain personal information, so POPIA applies to how they are stored, who sees them and how long they are kept. Your information officer should confirm the setup. Consent choices also mean analytics will miss some visits, and reports mark those gaps rather than hide them.

Reports then show, per branch, calls answered and missed, chats, direction requests, new reviews and the quotes or sales that followed in the CRM. My CRM consulting for South African firms covers the system side. For AI assistants, see the companion AI search optimization page for South Africa; the broader plan sits on the South Africa SEO consultant page and the South Africa hub. All work is delivered remotely, with site visits only by arrangement.