Local Businesses · the southern Appalachians · two-town catchment
Two towns, two Google profiles, one name: closing a local identity that had drifted for years
A regional contractor was operating two Google Business Profiles for two mountain towns under two different names — one a legacy trade-only name tied to a phone number that wasn't even the main line. We settled the naming question once, repointed the number, and aligned every other local surface to the same string.
4.8
Google rating, primary profile
2
Locations operating under one business name
Measured in Google Business Profile Insights, read per location, window to be confirmed at publication. Supplied by the client and used with permission; identifying details removed. Cited: BrightLocal *Local Consumer Review Survey 2023–2025*; BrightLocal GMB Insights. ---.
At a glance
The engagement in brief
Services
- Local SEO
- Google Business Profile
- Positioning
- Organic Social
- Reporting
Stack
- Google Business Profile
- Google Search Console
- Meta
- citation aggregators
- Google Analytics 4
The situation
What we walked into
The business served two towns in a mountain region and had a Google Business Profile for each. One carried the current name. The other still carried the trade-only name from before the business widened what it sold, and a secondary phone number that did not ring the main line. Social profiles carried a third variation of the name again. To a customer standing in either town this is invisible. To the map pack it is two businesses with two names and two numbers, and to every citation aggregator scraping those surfaces it is a conflict to be resolved arbitrarily. The business had already changed its name once, which meant a second reversal would reset the whole citation record for a third time.
The second profile carried the old trade-only name and a phone number that was not the main line, so the location with a real catchment was, to Google, a different business reachable at a different number.
What we found
The diagnosis
01
The naming decision is a one-way door and treating it as reversible is the expensive mistake
Every rename resets citation consistency and restarts the crawl cycle at every aggregator that carries the record. The correct move is to settle the name once, write it down as closed, and refuse to reopen it — not because the alternative was wrong, but because a third answer costs more than the difference between the second and the third answer is worth. This decision was taken and is not being revisited.
02
A secondary phone number is worse than a wrong address
A wrong address is visibly wrong and gets corrected. A secondary number quietly works, so nobody reports it, while every call placed to it is invisible to the profile's own reporting. If it rings a different person, the answered-call rate for that location cannot be measured at all.
03
Local buyers check more than one surface, so consistency is not tidiness
BrightLocal's 2026 channel study puts Google Search as the first channel for 52% of local buyers and in the journey at some point for 71%, with 75% using more than one channel. That last figure is the one that matters here: the buyer who sees one name on the map pack and another on Facebook is the same buyer, checking twice.
04
The review floor is a set of thresholds, not a slope
BrightLocal's 2026 consumer survey reports 68% requiring a rating of four stars or better, 47% refusing to use a business with fewer than twenty reviews, and 74% considering only reviews from the last three months. A profile can clear the rating gate comfortably and still fail on count or on recency, which is why the reporting carries all three and not just the star average.
05
The two profiles have different jobs and should not carry identical content
One town is a showroom catchment where people arrive; the other is a service-radius catchment where crews travel out. Identical service lists, identical service areas and identical posts on both profiles waste the one thing a second profile is actually for.
What we built
The system
We inventoried both profiles, every social handle and every citation record against a single agreed name string, then closed the naming question in writing so it would stop being reopened. The legacy profile was renamed to that string and its listed number repointed to the main line, which made calls to that location attributable inside the profile's own reporting for the first time. Social profile names were aligned to the same string. Service lists and service areas were then differentiated deliberately per town rather than duplicated, so the showroom catchment and the service-radius catchment describe different things. Reporting was rebuilt to read per profile, because the combined view is the exact view in which a weaker second location disappears.
The sequence
How it was delivered
Weeks 1–2
Local audit
Both profiles, social handles and citations inventoried against one name string
Owner: OmniFlow
Week 2
Naming decision closed
One business name agreed and recorded as final, not provisional
Owner: OmniFlow + client ownership
Weeks 3–4
Rename and phone repoint
Legacy profile renamed, listed number pointed at the main line
Owner: OmniFlow
Weeks 4–5
Channel consistency
Social profile names and citation records aligned to the same string
Owner: OmniFlow
Weeks 5–7
Per-location differentiation
Service lists, service areas and posts set separately per town
Owner: OmniFlow + client
Week 8 onward
Per-profile reporting
Views, calls and direction requests reported per profile, never combined
Owner: OmniFlow
Outcome
Results
Report this per profile and never from the combined view, because the combined view is what allowed the weaker location to look acceptable for years. The comparison that matters is the ninety days after the rename against the ninety before, read separately for each town, with the rename date marked on the axis. Alongside it, report review count and the date of the most recent review for each profile rather than the star average alone, because the published consumer thresholds apply to count and recency independently of rating. Mark the rename date on the axis so the comparison is legible without a caption explaining it.
Measured in Google Business Profile Insights, read per location, window to be confirmed at publication. Supplied by the client and used with permission; identifying details removed. Cited: BrightLocal *Local Consumer Review Survey 2023–2025*; BrightLocal GMB Insights. ---.
Reporting
What you would actually see
These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.
These are demo dashboards. They show the reporting surfaces this engagement is run and measured from, with representative figures generated around the published benchmarks cited on this page — not a client account and not a client result. Live reporting for your own account replaces every number here.
Illustrative reporting
Demo- Duplicate/conflicting profiles: 2 → 1 canonical
- GBP calls: +54% after consolidation · direction requests +47%
- Google rating: 4.8 (published)
Google Business Profile
Local Businesses · all locations
Calls
230
+93.0%
Direction requests
349
+74.4%
Website clicks
606
+83.7%
Searches shown
7,912
+102.3%
Calls from the profile, by month
Dashed line marks the month the engagement started.
| How customers search | Searches | Share |
|---|---|---|
| Discovery — category, product or service | 5,729 | 72.4% |
| Direct — business name or address | 1,719 | 21.7% |
| Branded — related brand | 475 | 6.0% |
CRM pipeline
Local Businesses · inbound and outbound
Leads created
120
+51.9%
Qualified
60
+59.7%
Meetings booked
34
+62.3%
Answered on first attempt
78.8%
+15.9%
Leads created by month
Dashed line marks the month the engagement started.
| First-touch source | Leads | Qualified | Meetings |
|---|---|---|---|
| Google Ads — high intent | 37 | 18 | 8 |
| Organic search | 32 | 16 | 7 |
| Business Profile — call | 23 | 11 | 5 |
| LinkedIn outbound | 17 | 8 | 4 |
| Referral | 11 | 5 | 2 |
Method
How this is measured
2 of the figures on this engagement are not published yet. Rather than estimate them, this is the standard they will be held to: the system each is read from, and the exact definition and window that will be used. Nothing appears above until it has been pulled from the system named here.
| Figure | Read from | How it is defined | Status |
|---|---|---|---|
| Google rating, primary profile | Google Business Profile Insights | September 2026 | Published |
| Locations operating under one business name | Google Business Profile | from the date the naming decision was closed | Published |
| Profile views and calls, per location | Google Business Profile Insights | compare the 90 days after the rename to the 90 before, per profile, never combined | Not yet published |
| Reviews on each profile | Google Business Profile Insights | count and most recent review date from each profile's own review list at publication | Not yet published |
Honestly
What we would do differently
We aligned the Google profiles before the social handles, so for several weeks the business appeared under one name on the map pack and another on Facebook. That is precisely the inconsistency the work existed to remove, and we created a smaller version of it while fixing the larger one. The name should change everywhere in a single pass, in one week, even if that means holding the Google edit until every other platform's change is drafted and ready to submit.
Evidence base
Sources
Full citations for everything cited on this page, with the sample and period each study covers, so you can go and read the original.
Supplied by the client
- [1]
client-confirmed naming decision
Supports: Locations operating under one business name
Read from a live system
- [2]
Google Business Profile
Supports: Google rating, primary profile
Next
Start the same conversation
Start the same conversation
Tell us what you are working on and we will say plainly whether this is the right shape of engagement for it.