Running local SEO across several branches without duplicate pages

Fibvo editorial · 26 August 2026 · 5 min read

Your company has a head office in Chennai, branches in Coimbatore and Madurai, and a warehouse that opened in Hosur last year. Search your company name with any of those cities and the head office appears for all of them. Two branches have no Google Business Profile. The website has a single contact page listing four addresses, and customers keep calling the wrong office. When the signals are this muddled, Google struggles to decide which branch to show, so it shows the one it knows best, or none.

Start with a branch register, not with pages

Before changing the website, build one sheet with a row for each location. It becomes the source for the website, every profile and every directory listing, so each decision is made once. For each branch, record:

• The trading name exactly as it appears on the signage
• The full postal address, written the same way every time, with PIN code
• A phone number answered at or for that branch, rather than a central helpline
• Regular hours, plus how the branch handles Sundays and public holidays
• The person responsible for the branch's profile and its review replies
• The URL of the branch's location page and of its Google Business Profile

Only include places that qualify. A branch belongs on the register if customers visit it during stated hours, or if staff work from it and travel out to customers. A registered office used only for paperwork, a salesperson's home or a desk rented to get a postal address in another city does not.

Give each real location its own Google Business Profile

Google expects one profile for each location where the business genuinely operates, and none for places it does not. Keep the business name identical on every profile. Tell branches apart through their addresses, their categories where services really differ, and photos taken at each site. Do not add area names to the brand name; Google's guidelines only allow that when it is how the branch is actually signed.

Manage the profiles together in Business Profile Manager by placing them in a business group, so owners and managers can be added at group level rather than profile by profile. Businesses with many locations under one brand can request bulk verification instead of verifying each branch separately.

Point each profile's website link at that branch's location page, not the homepage. Adding UTM parameters to the link, such as utm_source=google, utm_medium=organic and utm_campaign=gbp-madurai, lets you separate profile visits by branch in GA4.

Build location pages that could only belong to one branch

A location page answers the questions someone has before visiting or calling that branch. Many multi-location sites fail here by publishing one template with the city name swapped. Write each page from what is true about that site:

• Name, address, phone and hours matching the branch register, written as text rather than inside an image
• An embedded map and directions from landmarks locals use, such as the nearest bus stand, metro station or highway exit
• The services this branch handles, and any it refers to another branch
• Practical details such as parking, loading bay access, cut-off times for drop-offs or documents to bring
• Photos of the building, the team and the work area, taken on site
• Comments from customers of that branch, used with their permission

Logistics firms, where Fibvo does much of its work, often run branches at ports and inland container depots that each handle only some services. Saying so plainly on each page saves wasted calls and tells Google which branch is relevant to which search.

Add LocalBusiness structured data, or a more specific subtype, to each page with that branch's own address, phone and hours.

Keep pages from copying or competing with each other

Near-identical pages cause two problems. Google may pick one version and ignore the rest, and a large set of pages built mainly to rank in different places looks like the doorway pages its spam policies target.

If you could swap the city name for another and the page would still read true, it is not a location page yet.

• Create a page only for a real branch. Cities you merely deliver to belong on a service page or a single page about the areas you cover.
• If two branches share a city, name each page by its locality and link between them so visitors can choose.
• Make sure tracking or filtered versions of a location page carry a canonical tag pointing to the clean URL.
• Avoid publishing the same branch page in two places, such as on a subdomain and in a subfolder.

Handle openings, moves and closures in the same order

Multi-location local SEO decays when branches change and only some records are updated. Agree a sequence and follow it every time.

• New branch: add it to the register, publish the location page, create and verify the profile, then add the page link to the profile.
• Moved branch: update the profile address first and expect to re-verify, then update the page and the register on the same day.
• Closed branch: mark the profile as permanently closed rather than deleting it, and redirect the location page with a 301 to the nearest open branch or to the branch list.

Finally, keep a plain HTML list of all branches, grouped by state or city and linked from the footer or main navigation. Store locators built only from a map widget and JavaScript can leave branch pages hard for crawlers to reach, and a simple list helps visitors too.

---

Written by Fibvo — Bengaluru and Erode, India — working with clients in other time zones. Questions, or think we have it wrong? Tell us.