How should a multi-location company structure its Google Business Profiles?
One profile per physical location that meets the eligibility rules — not one per service, not one per city you travel to. Own them all under a single location group with central control, use the same brand name on every profile, and give each location its own tracked phone number so per-location demand is measurable. The most common failure is one shared call-center number across every profile.
The unit is a location, not a market
Profiles map to real, staffed, verifiable places. A company operating four branches gets four profiles. A company operating one branch and serving eleven cities gets one profile with declared service areas. Creating a profile for a market you serve but do not occupy is the fastest way to a hard suspension.
The same rule kills the other common idea — a profile per service line at the same address. Multiple profiles at one address are a recognized spam pattern and are treated accordingly unless the businesses are genuinely distinct and separately staffed.
Naming, and the temptation to add the city
Every location uses the same brand name. Appending the city is only correct when the location genuinely operates under that name on its signage — which is occasionally true for acquired companies and rarely true otherwise.
Acquisitions are the real complexity here. When you buy a company, you decide whether to keep its name and its review history or migrate to yours. Migrating usually means renaming the existing profile rather than creating a new one, because a new profile starts with zero reviews and the old one keeps ranking. Renaming a profile with a strong history is often the better trade even though it feels riskier.
The shared phone number problem
Most multi-location operators route every call to a central dispatch center, and most of them put that one number on every profile. This causes two distinct problems. It muddies entity identity, since a phone number shared across many listings weakens the association between a location and its data. More importantly, it destroys per-location measurement: every call arrives on the same line and nobody can tell which profile produced it.
The fix is a unique tracked number per profile with the location's real number listed as an additional number, all still routing to the same center. Suddenly location-level demand is countable, and you can see which branch's visibility is actually producing calls.
Manage centrally or it will drift
At two or three locations, manual management works. Past that it does not. Hours get updated at four of nine locations, a branch manager creates a duplicate, a service list goes stale for a year. Location groups plus the profile API make bulk updates and audits possible instead of aspirational.
This is where local SEO turns into an integration problem. Profile data, per-location call data and per-location revenue from the field service system need to sit in one place before anyone can compare branches honestly — which is exactly what a multi-location dashboard and rolled-up intelligence briefs are for.
Topics: multi-location · Google Business Profile · location groups · operations
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.