Local SEO Consultant, Kenya

Writing Kenyan addresses so maps and customers agree

Few Kenyan businesses have a street number customers would recognize. People describe a location by building, floor, road and area, then add a landmark: second floor of a plaza on Thika Road, next to the bank, opposite the petrol station. That works in conversation but needs care on a map, where one wrong field moves the pin to the far side of a dual carriageway or to another wing of a mall.

For every location I record one agreed form of the address and use it everywhere:

• building or plaza name, with floor, wing and shop or suite number
• road and area, such as Upper Hill, Kileleshwa or Nyali, and the town
• a pin placed on the entrance customers use, checked against satellite imagery and street photos
• a plus code where the plot has no usable street address, which is common on new developments and in parts of many towns

Postal details need separating out. Letterheads often show a P.O. Box with a postal code, which is fine for invoices and the contact page but cannot serve as a listing address. Landmarks, on the other hand, are useful: they belong in the directions section of the branch page and in profile posts, where they help a first-time visitor without cluttering the address fields.

Malls and plazas deserve particular attention. A pin on the parking entrance, the wrong tower or a neighboring building sends customers in circles, and the profile may lose relevance for searches close to where the shop really is. The underlying approach is explained on my local SEO page.

Ownership, duplicates and the name on the register

Many Kenyan listings were never set up deliberately. A customer added the shop to the map, Google created a place from photos, an agency built the profile years ago, or a branch manager verified it on a personal account. The result is often two or three listings for one location, none fully controlled by the business.

I trace every listing for each branch, recover access through the proper request process where needed, merge or remove duplicates and record who owns each profile. Ownership should sit with a business account held by head office, with branch staff added as managers, so a resignation never locks you out.

Names come next. The registered company or business name held by the Business Registration Service may differ from the name over the door, and branches are often known by area. Whatever is painted above the entrance is what the listing should say, with no keywords or slogans tacked on. Put the registered name in the website's legal and contact sections, on invoices and in Organization schema, which tells Google and cautious buyers that brand and registration describe one business.

Verification can be awkward in shared office buildings, where signage may be no more than a line on the reception directory, or for businesses operating from a stall inside a market. Google picks the method, and I prepare a checklist of what the person on site should show, so the attempt is not wasted.

Swahili, English and branch networks across Kenyan towns

Kenyan customers move between English and Swahili, and listings can reflect that without becoming confusing. Category names and some fields appear in the searcher's interface language automatically, so the work is mostly in descriptions, posts, product or service names and the branch page itself. A clinic or agrovet serving customers who search in Swahili may benefit from a Swahili description and posts, while a corporate supplier in Upper Hill may not need them at all.

The engagement runs in English. Kenyan Swahili wording should come from fluent writers on your payroll or at a local agency who know how your customers talk, never straight out of a translation tool.

Branch networks raise structural questions. Pharmacies, supermarkets, hardware chains, clinics, banks and courier companies often have outlets in Nairobi and in towns such as Mombasa, Kisumu, Nakuru, Eldoret and Thika. Each real branch deserves its own page, linked from its profile, with:

• the agreed address, landmark directions and a map
• hours, including any differences from head office
• services and stock specific to that branch
• a direct phone line and WhatsApp link

Pages for estates or towns without a branch are another matter. Copies that change only the place name are doorway pages and rarely help. A few area pages earn their place when they describe real coverage, delivery arrangements or response times. My multi-location SEO page describes the central branch register that keeps those details in step.

Reviews: honest requests and Kenyan consumer rules

Ratings and comments shape which Kenyan businesses get the call. They also tempt shortcuts that I do not use: buying ratings, getting staff and family to post, rewarding reviewers with airtime or discounts, or sending the link only to smiling customers. Each of these breaks platform policies, and misleading reviews or testimonials may raise questions under Kenya's consumer protection rules. Ask your lawyer how they bear on your business.

Requests themselves involve personal data. Sending a review link by SMS or WhatsApp uses a customer's phone number, and Kenya's Data Protection Act sets expectations for how that number was collected and how it may be used. Whoever handles data protection for you should approve the wording and the list of recipients.

The routine I set up is simple enough for busy branches:

• an identical, neutral message to all customers once the order is delivered, the patient discharged or the goods collected
• a short link that opens the review form for the correct branch, not the head office listing
• a named person per branch who replies politely, in the customer's language where possible, without repeating personal details
• a way to report reviews that genuinely break policy, while honest criticism stays visible and receives a reply

Where a CRM or point-of-sale system records completed jobs or purchases, the request can be triggered from there, which keeps it consistent and removes the temptation to choose who gets asked.

Phone lines, WhatsApp chats and leads per branch

Kenyan local inquiries arrive mostly by call and WhatsApp. A frequent weakness is the number itself: a listing carries a manager's personal line, so when that person moves on, calls and chats go with them. I recommend a business line and a WhatsApp Business account per branch, owned by the company, and the same number on the profile, branch page, directories and signage.

Measurement then follows each inquiry back to its branch:

• tagged website links on every profile, so analytics separates map visits from other organic visits
• click-to-chat links with a prefilled message naming the branch, so the first WhatsApp message identifies its source
• call tracking only where a provider offers suitable local numbers, with the main number kept as the listed number to avoid inconsistency
• click events on phone and WhatsApp buttons, recorded within your consent settings
• a branch and channel field in the CRM, so sales can see which locations generate inquiries and which turn them into paid orders

Chat logs, call records and phone numbers are personal data under Kenya's Data Protection Act, so retention and access should be agreed with your data protection lead or advisor.

Each month, every branch sees its own calls, chats, route requests, fresh reviews and the orders that followed. My CRM consulting for Kenyan businesses covers the system side. Questions buyers put to chat assistants are handled on my Kenya AI search optimization page, while overall search strategy lives on the SEO consultant Kenya page and the Kenyan services hub. I work remotely; a visit to Kenya happens only by prior arrangement.