Which Pages Should a Multi-Location Business Fix When AI Cites the Head Office Instead of Local Branches?

Why does the head office win?

• Your homepage and organisation markup show the head office address, so it looks like the business's only location.
• Branch pages are thin templates: an address, a map widget and the same copy as every other branch.
• Branch Business Profiles link to the homepage, so every profile points back to a page about the head office.
• Reviews and coverage concentrate on the head office or flagship.
• The store locator is a script-driven map, so crawlers that do not run JavaScript may never find individual branch pages.
• Directories list only the head office, often copied from company registers.

What should you fix, in order?

1. Branch Business Profiles: complete for every location, with its own phone number, hours, categories, photos and services. Link each to its own location page.
2. Location pages: one per branch, with unique content: the team, services offered at that branch, opening hours, parking and directions, nearby landmarks, and branch-specific reviews or testimonials.
3. A crawlable locations list: an HTML page listing every branch with links, reachable from your footer, not only a map.
4. Structured data per location page: LocalBusiness markup with that branch's address, phone, hours and coordinates. Keep organisation markup on the homepage for the company as a whole.
5. Directory and aggregator listings per branch, with branch phone numbers and links to branch pages.
6. Branch-level reviews: give each branch its own review link, so customers review the location they used.

How specific location and service pages need to be is covered in how specific service, location and customer pages should be for AI to understand a business.

What should I fix first when AI assistants recommend only our flagship store?

Start with the gap between the flagship and the rest. The flagship usually has the most reviews, the most photos, press coverage and a richer page. To close the gap:

• Give each other branch a reason to be recommended in text: what it offers, who it suits and what is different about it, such as parking, longer opening hours or a specialist service.
• Ask every customer at every branch for an honest review in their own words, using that branch's own review link, so reviews land on the location they visited.
• Seek local coverage for each branch, such as a neighbourhood news item or a local business directory feature.
• Stop linking everything to the flagship. Menus, ads and social profiles that always point to the flagship reinforce the imbalance.

Then test "[category] near [each branch's area]" questions. If the flagship is still recommended for a neighbourhood 20 minutes away from it, the branch near that neighbourhood lacks evidence.

Wrong-location recommendation for multi-location dentists: how can I find and fix AI answers that send buyers to the wrong branch?

Dental groups are especially exposed, because patients choose by distance and by dentist, and each branch offers different services and accepts different insurance. To find wrong-branch answers:

1. List each branch with the areas it serves and its main services, such as implants, orthodontics or emergency care.
2. Ask assistants area-specific questions: "Emergency dentist in [neighbourhood]", "Invisalign near [landmark]", "Dentist in [suburb] that takes [insurance]".
3. Record which branch each answer recommends and whether it is the nearest one offering that service.
4. Open the cited sources for wrong answers. They are usually a branch profile with the wrong services, a thin location page, or a dentist's profile still attached to another branch.

To fix them:

• List services per branch on each location page and profile, and state which services a branch does not offer.
• Put each dentist on the right branch's page, with their own profile where Google's rules for individual practitioners allow.
• State insurance accepted per branch, if it differs.
• Keep emergency hours per branch accurate, since urgent questions are where wrong-branch answers do most harm.

Why does Google AI recommend our headquarters instead of nearby branch locations?

Google says local results are based mainly on relevance, distance and popularity. If the head office profile has the most reviews, the fullest description and the most links, it can outscore a nearby branch whose profile is thin, even though the branch is closer. Google's AI features draw on the same local data. So:

• Make branch profiles as complete as the head office's: categories, services, attributes, photos, hours and a description specific to that branch.
• Link each profile to its location page, not the homepage.
• Check for duplicate or unverified branch profiles, which split reviews and signals.
• Use the head office profile only if customers visit it. A head office that does not serve customers should not compete with branches for local searches.

Should a franchise use one domain or separate location pages for AI visibility?

Usually one domain, with a page for each location, is stronger. A single domain concentrates the brand's authority, keeps information consistent and gives assistants one clear source for brand facts. Location pages carry what is local. Separate franchisee domains can work, but they fragment signals, often contradict the brand site, and are harder to keep accurate.

If franchisees do keep their own domains, link brand location pages and franchisee sites to each other, and keep names, addresses, phone numbers and services identical across both. How AI gets service areas wrong is covered in why AI gets your service area wrong.

How do you check that the fixes work?

Build a question set with one or two questions per branch area and per key service, and run it across assistants monthly. Record the branch recommended, whether it is the right one, and the sources cited. Track the share of answers that name the correct branch. The measure that matters is right branch, right service, right area, not whether the brand appears at all.

What might an illustrative case look like?

Consider an illustrative optician chain with eight branches whose AI answers nearly always named its city-centre flagship, even for suburbs 30 minutes away. Its branch pages were identical templates, its store locator was a script-driven map, and seven branch profiles linked to the homepage. The chain wrote a distinct page for each branch, with its optometrists, services, parking and hours. It added an HTML list of locations to the footer and relinked every profile to its branch page. It also set up a review link per branch. Three months later, suburban questions named the nearest branch in most answers.

What do people ask about multi-location businesses and AI?

Should branch pages be different even if services are the same?

Yes. Staff, hours, directions, parking, local landmarks and branch reviews make each page useful and distinct.

Does the head office need a Business Profile?

Only if customers visit it. Otherwise it can draw local searches away from branches.

How many reviews does a branch need?

There is no fixed number. Aim for a steady flow of recent reviews, so the branch is not far behind nearby competitors.