Skip to content
Skayle Marketing

Local search · 12 min read

Same brand, same website: why one branch ranks and the next does not

Two branches with the same name, the same services and the same website end up with very different local visibility, and the causes are rarely the ones head office suspects. Most of what determines a branch result is decided at the branch, not at the centre.

Written by , FounderUpdated

The question

Why identical branches produce different results

A network opens five locations, runs one website, one brand and one marketing budget, and ends up with three branches that appear consistently and two that barely register. It reaches the marketing team as two complaints that sound like one: location pages not ranking, and a branch that has been invisible since it opened. The branch managers conclude they are being neglected. The centre concludes those branches are not following the process. Usually neither is right.

Google Business Profile Help names three things behind a local result: relevance, meaning how well the profile matches the search; distance, meaning how far the business is from the person searching; and prominence, meaning how well known it is, including links and reviews. Read that list against a network and the awkward fact becomes obvious. All three are measured at the location, not at the brand.

That is why central effort produces uneven results by design. The website is shared, and it matters, but it is the smaller half of the answer. The larger half accumulates at each address separately: its own categories, its own reviews, its own photographs, its own history, and a physical position that nobody can change.

The practical consequence is that a network needs a per-branch diagnosis rather than a programme. The five causes below are checkable in an afternoon per location, and they run from the most fixable to the least.

The causes

Five reasons a branch lags, in the order worth checking

Work down this list. It is ordered by how quickly each cause can be corrected, which is not the same as how often it occurs.

The branch profile is classified differently from the others.
This is the most common finding and the easiest to miss, because nobody compares profiles side by side. A branch set up by a different person years later has a different primary category, a shorter services list, missing attributes or an address formatted inconsistently. It is competing for a different set of searches than its siblings and nobody noticed.
There are two profiles for the location and they are splitting everything.
A relocation, a rebrand or a change of manager typically leaves a second listing behind. Reviews, photographs and references divide between them, so neither reaches the weight the branch should have. Search the address, the former name and the old phone number in Maps before concluding anything else, because every other diagnosis is unreliable while a duplicate exists.
The location page says nothing that is only true of that branch.
Where every location page is the group page with the place name substituted, the pages compete with each other and none is a clear answer to a local search. It also fails the more basic test: a person deciding between two branches learns nothing from it. The fix is not more pages, and it is not more words. It is four paragraphs per branch that would be false on any other branch page.
Reviews arrive at some branches and not others.
Reviews attach to the profile that earned them, so a group average conceals a wide internal spread. Almost always the difference is procedural rather than cultural: at the strong branches somebody asks as part of the job, and at the weak ones asking is an initiative that stopped when the person who started it moved on. That is a rota problem with a search consequence.
The branch is simply further from where people search.
Distance is measured from the person searching to the business, and a branch on the wrong side of a catchment will lose searches it can never win. This is the one cause on the list that does not respond to work. Recognising it early is valuable, because the alternative is a network spending years and a budget on the only variable that is fixed.

Where each signal lives

What the brand decides, and what each branch decides for itself

The left column is why central work produces uneven results. The right column is the part a network can genuinely standardise.

Local search signals sorted by whether they accumulate at the individual location or apply across the whole brand
DimensionAccumulates at the branchApplies across the brand
Categories and servicesSet per profile, and frequently inconsistent across an estate nobody has audited.Only in the sense that a standard can be written and then applied one profile at a time.
Distance from the searcherEntirely. Fixed by the lease, and unaffected by anything marketing does.Not at all.
Reviews and ratingsEntirely. They attach to the profile that earned them and do not transfer.The asking process can be standardised. The results cannot be pooled.
Photographs and profile completenessPer profile, and usually the clearest visible difference between a strong and a weak branch.Standards and templates only. Somebody local still has to take the pictures.
Website authorityIndirectly, through how well that branch page is linked from the rest of the site.Yes. This is the main thing the centre genuinely contributes to every location at once.
Location page contentYes, and it is the field where central control most often produces identical pages.The template and the standard. The substance has to come from the branch.
Structured dataThe values are per location and must match what the page shows.The implementation. Build it once from the location data rather than by hand.
Local references and coverageSponsorships, partnerships, community involvement and local press are earned locally.National coverage helps the domain, and does little for one branch’s local prominence.

Which searches are which

Searches decided at the branch, and searches decided by the brand

Networks report on both together, which hides the problem. Splitting them tells you immediately which kind of visibility is missing.

Decided almost entirely at the branch

Proximity and profile strength dominate. Central content and brand authority barely register here.

  • service near me
  • service in town name
  • open now nearby
  • best service close to me

Decided by the brand, then routed to a branch

The person has already chosen you. The failure mode is routing them to the wrong location or to a central queue.

  • brand name town name
  • brand name opening hours
  • brand name near me
  • brand name phone number

Decided by the website across all locations

One good page serves every branch. Duplicating it per location weakens all the copies at once.

  • how much does the service cost
  • what to expect at your first appointment
  • service explained
  • do i need this service

These are examples of how customers in this market search, drawn from keyword research and from the questions that come up on sales calls. They are illustrative, not a volume claim — the actual demand in your area is something we size before recommending anything.

Diagnosis

How to work out which problem a lagging branch has

One afternoon per branch. Run it in this order, because a duplicate profile invalidates every check that comes after it.

  1. Look for duplicates before anything else

    Search the branch address, the current name, any former name, the previous phone number and any acquired brand in Maps. Note every listing that appears. Until you know there is one profile per location, no other measurement means anything, and any improvement work you commission may be strengthening the wrong listing.

    You get: A listing inventory per branch, with duplicates identified for merging

  2. Put the profiles side by side

    Export or screenshot the primary category, additional categories, services, attributes, hours, photograph count and review count for every branch into one table. The lagging branches usually declare themselves in that table within a minute, because differences that are invisible one profile at a time are obvious in a column.

    You get: A one-page comparison table across the whole estate

  3. Test proximity honestly

    Have someone standing in the branch’s catchment run the main service search on their own phone, then repeat from two points at increasing distance. This establishes the edge of the branch’s visibility as a fact rather than a theory, and it separates a branch that is under-performing from a branch that is simply further away than its competitors.

    You get: Screenshots from three points, showing where visibility stops

  4. Read two location pages side by side

    Take the strongest branch page and the weakest and read them in adjacent windows. Count the sentences on each that would be false on the other. If the count is near zero, the pages are the same page and that is a finding. If the count is high and the branch still lags, the page is not the problem and you can stop looking there.

    You get: A difference count per page pair, with the sentences that carry it

  5. Check who is asking for reviews, and when

    Not whether there is a policy — whether there is a person and a moment. At the branches that accumulate reviews there is almost always a specific point in the job where a specific role asks. At the ones that do not, asking was an initiative that stopped. Fix that before commissioning anything else, because it is the signal that keeps compounding after the project ends.

    You get: A named role and a named moment per branch, written into the operating routine

Remedies

What a lagging branch usually needs, in this order

Ordered by cost and speed. The first three are administrative and cheap; the last two are slow and compound.

  • One profile, verified, owned by the business rather than by a former agency or a departed manager.
  • The same classification standard as the strongest branch: primary category, additional categories, services and attributes matched deliberately rather than by accident.
  • A complete profile with photographs of that building, that team and work done there, rather than group stock imagery repeated across the estate.
  • A location page carrying four paragraphs that would be false on any other branch page, with structured data matching what the page actually shows.
  • Internal links from the services that branch genuinely sells, and from neighbouring location pages, so the page is not reachable only through a locator.
  • A review routine owned by a named role at that site, triggered at a specific point in the job, running every week rather than in bursts.
  • Local references earned nearby — a supplier listing, a membership, a sponsorship, a partnership — which are the only part of prominence a branch can build deliberately.
  • An honest decision about the searches distance rules out, and a plan for the surfaces that are not distance-weighted instead.

Questions

What network marketers ask about branch divergence

Why does one branch outrank another with the same setup?

Because almost nothing that decides a local result is shared between them. Google names relevance, distance and prominence, and all three are measured per location: the categories on that profile, the physical position of that address relative to the searcher, and the reviews and references attached to that branch.

The shared website contributes, but it is the smaller half. Two branches with identical central support routinely diverge, and that is the expected outcome rather than evidence of neglect.

How long should a new branch take to become visible?

Longer than anybody wants, and there is no honest number to give. A new profile starts with no reviews, no photographs, no accumulated references and no history, and every one of those accrues over months.

What can be committed to is the order of work: verification and classification first, then the location page, then a review habit from the first week of trading. Set the expectation as a slope rather than a launch date, because promising parity by a given quarter creates a credibility problem inside the business.

Our location pages are not ranking. Are they competing with each other?

They are if they are the same page with the place name changed. Where several pages address one search equally well, none of them is a clear answer, and which one appears becomes arbitrary.

The test is straightforward: read two of them side by side and count the sentences that would be false on the other page. If the answer is close to zero, the pages are duplicates with different headings, and merging or genuinely rewriting them is the work.

Can a branch on the edge of a town be fixed?

Not for searches where distance decides it. Distance is measured from the person searching, and no amount of content or review activity shortens it. This is the one cause in the list that is genuinely immovable.

What can be done is to compete where the branch is closest, which usually means the immediate area rather than the city name, and to build the kinds of visibility that are not distance-weighted — ordinary organic results, comparison and directory surfaces, and referral relationships nearby.

Should each branch have its own website?

Generally not. Separate sites split the authority the group has built, multiply the maintenance, and produce inconsistent information that undermines every location at once.

The exception worth considering is a franchise network where franchisees genuinely own their marketing and will act independently regardless. Even then, a shared platform with local editing rights is a better answer than a set of unrelated sites nobody can audit.

Do reviews transfer between branches?

No. Reviews attach to the profile of the location that received them, and Google names review count and rating as part of prominence for that profile.

This is why a group average is a misleading internal metric. A network can hold a strong overall rating while two branches have four reviews each, and those two branches are competing on their own numbers rather than the group’s.

Two branches behaving differently and no obvious reason

Send us the two locations and the searches that matter at each. We will tell you which of the five causes is behind it, including when the honest answer is that one of them cannot be fixed.

Last updated

We use analytics to understand which pages are useful. Nothing runs until you choose, and we do not sell or share what we collect. What we would set.