Discussion
  • Local SEO

Multi-location brands: one strong page per branch, or city hubs with nested location pages? Which drove more map pack and local organic visibility?

Published 1 reply

Discussion starter: a local SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    The short answer: for map pack visibility, the page that matters most is the branch page each Business Profile links to, not the hub above it. City hubs earn their place when a city has several branches, or when people search at city level and no single branch is the right answer. Where a city has one branch, a separate hub usually adds a thin page that competes with the branch page for the same queries.

    The main qualification is that the map pack and local organic results rank different things. The map pack ranks Business Profiles, and your website feeds it mainly through the linked landing page and your domain’s overall prominence. Local organic ranks pages, and that is where hub design can win or lose city-level queries. No public controlled study compares “flat branch pages” with “hubs plus nested branches” head to head. Most before and after stories change the content, internal links and profile links at the same time, so treat any claim that one structure “drove” more visibility as a case study, not a rule.

    Why the two result types respond to different parts of the site

    Google’s Business Profile help documentation names three local ranking inputs: relevance, distance and prominence. It also says a business’s position in web results contributes to prominence, which is the documented link between your website and the map pack. Distance is the one you can’t change with site architecture. A Sydney hub page cannot make your Parramatta branch closer to a searcher in Bondi.

    That makes the profile landing page the highest-leverage URL. Sterling Sky’s guide to Business Profile landing pages describes a law firm whose Staten Island profile linked to a homepage optimised for Queens; after pointing it to a page targeting the Staten Island service and location, they reported “dramatic ranking increases” for that profile within a month. That is one agency case study, the weakest useful level of evidence. The same guide adds the caveat that matters: if the linked page does not rank organically in that area for the main keyword, keep working on the page until it does. The link choice alone is not the lever.

    Local organic behaves more like normal SEO with a location layer. Suburb and “near me” queries tend to surface branch pages. City-wide queries such as “physio Sydney” are where a hub can compete, because it can answer “which of your nine Sydney clinics suits me?” better than any single branch page can.

    Important distinction:

    Nested URLs and nested linking are different decisions. A URL like /locations/nsw/sydney/parramatta/ is mainly for people and maintenance. What affects crawling and internal authority is whether the hub actually links to branches, whether branches link back and to nearby branches, and how many clicks they sit from the homepage. A flat URL structure with a strong store locator can link just as well as a nested one.

    What each structure changes in practice

    Element One strong page per branch City hub plus nested branch pages
    Profile landing page Branch page (the same in both models) Branch page; linking profiles to the hub removes branch-specific relevance
    City-level organic queries One branch page has to stretch to cover the whole city, or none ranks well Hub can target the city query and route people to the right branch
    Suburb and “near me” queries Branch page targets these directly Same, provided the hub does not compete for them
    Internal linking Depends on the locator and navigation Hub gives a natural crawl path and a place to cross-link branches
    Main risk Weak coverage of city-level demand in multi-branch cities Thin hubs, cannibalisation, and doorway-style templating at scale
    Evidence to inspect Queries each branch page gets impressions for in Search Console Whether hub and branch pages trade places on the same queries

    When a city hub is worth building

    The deciding factor is whether the hub has a job no branch page can do. That depends on branch density and on how people in that city search.

    Condition Lean towards branch pages only Lean towards a hub with nested branches
    Branches in the city One or two Three or more
    Query pattern Mostly suburb, landmark and “near me” searches Meaningful demand for “[service] [city]” with no suburb
    What the hub could say A list of links and a paragraph of city boilerplate Genuine comparison: services, hours, specialists, parking and transport by branch
    Scale Tens of branches, simple locator Hundreds of branches where hubs also organise crawl paths
    Services Same services everywhere Services differ by branch, so routing people matters

    Hypothetical example:

    A physiotherapy brand has 45 clinics: nine in Sydney, six in Melbourne, three in Brisbane and one each in 27 regional towns. I would build hubs for Sydney, Melbourne and probably Brisbane, each comparing clinics by service (hydrotherapy, sports, women’s health), hours and parking. In the 27 single-clinic towns, the branch page is the town page, so no hub. Every Business Profile links to its own branch page. If the Brisbane hub only restates what the three branch pages say, I would drop it and link the three branches from the locator instead.

    Where multi-location builds go wrong

    Watch for this:

    Google’s spam policies list pages targeting specific cities or regions that funnel users to one destination as an example of doorway abuse. The risk is not having many location pages. It is having many pages that differ only by the city name. Hubs are the usual offender, because a template like “Looking for a physio in [city]? We have [n] clinics” is easy to generate and has nothing a user needs.

    Three other failure patterns show up often on these sites:

    • Hub and branch cannibalisation. In a city with one or two branches, the hub and a branch page both target “[service] [city]”, and Search Console shows them swapping for the same query. Neither builds consistent visibility.
    • Profiles linked to the hub or the homepage. Often done “to consolidate authority”. It removes the branch-level relevance the profile needs and sends users to a page that doesn’t show their branch’s hours or phone number.
    • Branch pages as address cards. A name, address, phone number and embedded map is not enough content to rank organically in a competitive suburb. Under Sterling Sky’s caveat above, a page that can’t rank organically is a weak landing page for the profile too.

    What makes a branch page carry weight

    • Name, address and phone number that match the Business Profile exactly
    • Regular and holiday hours, kept in sync with the profile
    • Services offered at this branch, and those that are not, with links to the service pages
    • Branch-specific details: practitioners or staff, parking, public transport, accessibility, photos of the actual site
    • Directions from nearby suburbs and landmarks people actually use
    • LocalBusiness structured data with the branch address, geo coordinates and opening hours, linked to the parent Organization
    • Links from the hub or locator, and to the two or three nearest branches
    • A UTM-tagged URL in the profile’s website field, so profile clicks can be separated from organic clicks in analytics

    Practical detail on branch pages may matter more now that Google has removed Business Profile Q&A and expanded Ask Maps (Gemini in Maps) to English globally, with some features still US-only. Public evidence on which sources Ask Maps draws from is thin, so treat this as a sensible hedge rather than a proven ranking input.

    How to measure which structure is working

    Map pack visibility is noisy and depends on where the searcher is, so one rank check from the office tells you little. I would use three data sources together:

    1. Geo-grid rank tracking per profile for three to five core keywords, run on the same grid and schedule before and after any change.
    2. Search Console page and query data, grouped by city, to see which URL ranks for city-level versus suburb-level queries and whether hub and branch pages overlap.
    3. Business Profile performance (calls, direction requests, website clicks) plus UTM-tagged sessions and bookings per branch.

    If you want evidence rather than opinion, stagger the rollout. Build hubs in half the qualifying cities and hold the rest as a control for 8 to 12 weeks.

    • Hypothesis: hubs increase non-brand organic clicks for city-level queries without reducing branch page performance.
    • Primary metric: non-brand organic clicks to all location pages in the city (hub plus branches), not the hub alone.
    • Secondary metrics: average grid visibility per profile, calls and bookings by branch.
    • Confounders to log: review volume changes, category or hours edits on profiles, new competitors, seasonality and core updates.

    What would change the decision: if hub cities gain city-level clicks and branch pages hold steady, roll hubs out to the remaining multi-branch cities. If branch pages lose impressions on queries the hub starts ranking for, you have created cannibalisation, and the better move is a stronger locator with branch pages doing the ranking. If map pack grids don’t move either way, that is expected. The map pack mostly responds to the landing page, reviews, categories and proximity, not the layer above.

    If this were my brand, I would get every profile linked to a strong branch page first, because that work helps both result types in any structure. Then I would add hubs only in cities with three or more branches and real city-level demand, and judge them on combined city-level clicks rather than on whether the hub page itself ranks.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.