Who owns what in a multi-location SEO strategy

Pick an ownership model, then write down who does each task

Pick one of three ownership models before anyone touches a profile or a page. In a centralised model, head office makes every change and branches send requests. In a decentralised model, each branch runs its own profile, page and reporting. In a hybrid model, head office owns anything that must match across branches, such as the business name, page templates, tracking and access, while each branch owns the details that change locally, with head office signing off a short list of risky edits.

The model matters because many multi-location search problems start as admin problems. A branch changes its hours and nobody updates the profile. A manager who left last year can still log in. Two pages chase the same suburb. Head office counts leads one way, the branches another. Say a hypothetical pest control business runs branches in Caloundra, Nambour and Gympie. The branch managers know their local customers, and head office runs the website and the budget. With no written split, each side assumes the other is looking after the Google Business Profiles, and the Nambour profile shows an old phone number for months.

A workable decision rule: go centralised when branches have nobody with time or skills to keep profiles current; go decentralised only when branches operate as genuinely separate businesses; otherwise default to hybrid. Hybrid suits most service businesses: branch staff see changes first, and head office protects what breaks when one branch goes its own way.

Then turn the model into a task matrix. Each recurring task gets one person who does it, one person who signs it off (or none, if the risk is low) and a list of people who are told. Review it whenever a branch changes manager. One version for a hybrid model:

Build a location register with a named owner per branch

A location register is one shared sheet with a row for each branch. The website, the Business Profiles and any directory listings all copy from it. When a detail changes, it changes in the register first, then everywhere else, and it settles any disagreement between sources.

Give every row two owners. The branch owner owns the details that change locally: hours, the local phone number, services, photos and review replies. The head office owner looks after anything that must match across branches, such as the business name, categories, page templates, tracking and access.

Build Google's rules into the register. Google's Business Profile guidelines say all locations in the same country must use the same business name, with two exceptions. Sub-brands, departments and different types of operation, such as retail and wholesale, may use a distinct name if it's applied consistently to all their locations. And a location that consistently uses a different name on its storefront, website or stationery can use that name. If a branch uses a different name, note which exception covers it. The guidelines also say a virtual office, meaning a rented address the business doesn't operate from, isn't eligible for a profile.

Categories need a head office rule. The same guidelines say to use as few categories as possible to describe the core business, and to choose categories that are as specific as possible but representative of the main business. Branches that do the same work should share a primary category, recorded once in the register, and a branch that wants a different one should show head office the work it actually does there. The services each profile lists should match the services on that branch's page.

Service areas get their own column. Google's guidelines say a profile's overall service area shouldn't extend farther than about 2 hours of driving time from where the business is based, so check each branch's list against that limit before entering it.

Add a store code column too. Google's Business Profile Help describes a store code as any unique identifier that stays the same for a location, and says each location must have its own. Pick a simple pattern, such as PEST01 and PEST02, and never reuse a code. The same page warns that adding or changing a store code on an existing location through a bulk spreadsheet upload creates a duplicate location, so change codes for existing branches in Business Profile Manager. The spreadsheet doesn't verify anything on its own: Business Profile Help says uploading it doesn't send a verification request. Bulk verification is a separate request made through a form under Verifications, then Chain, in Business Profile Manager, and it needs 10 or more profiles from the same business in the spreadsheet and isn't open to service-area businesses. Typical register fields:

Give each person the lowest role that does the job

Access is where multi-location setups quietly break. Every Google tool has its own roles, and one pattern fits them all: the business keeps the top role on an account it controls, and everyone else gets the lowest role that does their job. Get this right first and the rest of the local SEO work has a stable base.

In Google Business Profile, a profile can have several owners but only one primary owner. Managers can edit details, post updates and reply to reviews, but Google's help says they can't add or remove users or remove the profile. That makes Manager the natural role for branch staff and outside help. Google Groups can't be added as owners or managers, so each person needs their own login. A primary owner also can't remove themselves until they've handed primary ownership to someone else.

With two or more profiles, Business Profile Help describes business groups as a more secure way to share access with co-workers. Group branches by region or manager, so a new starter gets the right profiles at once. Agencies work through an organisation account, and Google's overview for agencies notes that an organisation account can't directly own an individual profile.

Search Console needs extra care when someone leaves. Its help says a property must keep at least one verified owner, and that deleting an owner doesn't delete or revoke their verification token. While that token (such as an HTML file or DNS record) stays in place, the removed owner can verify again. So remove the person, then remove their token once you've checked nothing else relies on it. The same page says to use caution here, because one token can also verify other services, such as Merchant Center or Google Workspace, and removing it could affect them.

Start handovers early. Business Profile Help says new owners and managers wait 7 days before they can manage some features, including removing users and transferring primary ownership. One way to split roles across the main tools:

Map one page, one profile and one set of facts to each branch

Page ownership means every branch has one page on the website that belongs to it, and every page that targets a place has one branch behind it.

Google's Business Profile guidelines apply the same logic to profiles. They say not to create more than one profile for each location, and ask for either a phone number that connects to the individual location or a website that represents it. Either one meets that request, so a local phone number can do it on its own. Doing both is still worth it: point each profile's website link at that branch's own page rather than the homepage, so the profile and the page describe the same branch. For branches that travel to customers, the guidelines say a service-area business should have one profile for its central office or location with a designated service area, and should hide its address if customers aren't served there.

Where page territories overlap, assign each suburb to one branch and write it down. Two branch pages aimed at one suburb split the effort and leave customers unsure who'll turn up. Google's spam policies describe doorway abuse as pages created to rank for specific, similar searches, including pages aimed at particular regions or cities that funnel users to one page. The service area page guide explains when a suburb earns its own page, and when to merge overlapping pages covers the fix if duplicates already exist.

Decide who supplies what on each branch page. Head office owns the fixed parts: the template, the service descriptions that are true everywhere, the contact form and the tracking. The branch supplies the parts only it knows: photos of its own team and vehicles, the jobs it handles most, local access notes and answers to the questions its customers ask.

Make the markup copy the register too. Google Search Central's LocalBusiness documentation lists name and address as required properties and telephone, url and openingHoursSpecification among the recommended ones, and Google's general structured data guidelines say not to mark up content that isn't visible to readers of the page. So each branch page should show its own name, address, phone and hours, and its markup should carry the same values. When the profile and the page disagree, fix the register first, then both.

The site structure you choose sets how much of this head office can control. The governance trade-offs:

Run reviews, listings and changes from the register

Write a review policy that every branch follows, because reviews are where branch staff most often break rules without knowing it. Google's Maps content policy on fake engagement bans offering incentives such as payment, discounts or free goods in exchange for reviews, and bans discouraging negative reviews or selectively soliciting positive ones. It also prohibits content based on a conflict of interest, which includes current or former employment. Australian law adds its own limits: the ACCC says it's against the law for a business to create fake or misleading reviews or to arrange for others to do so. The Google review guide covers how to ask; the policy covers who does what.

The policy itself fits in four rules. Ask every customer the same way at the same point, such as after the job is signed off, never only the happy ones. Offer no discounts, gifts or prize draws for reviews, and never ask staff, family or contractors to review the business. Reply from the branch within a time the business sets itself, and route complaints about refunds, safety or legal matters to head office before replying. Never ask a customer to change or remove a review in exchange for anything, and never pressure anyone to review while on site.

Day-to-day changes run in a fixed order: update the register, then the profile, then the branch page and its markup, then the directories. Business Profile Help says special hours suit a business that adjusts its hours or closes for up to 6 days in a row, and that a business closed for 7 or more days in a row, or for an unknown period, should be marked temporarily closed. Address moves need head office sign-off: Business Profile Help says a business that moves to a new address after verification must verify again, and a name change might need verification again too. Edit the existing profile's address rather than creating a new profile, so the move doesn't leave two profiles for one branch.

Directory listings follow the same pattern. Head office claims the listings that feed maps and voice assistants beyond Google, such as Apple Business Connect and Bing Places for Business, plus the industry and Australian directories that matter for the trade. The business listing accuracy guide explains how to clean up old listings. One way to split the main listings:

Agree what every report number means, then build a branch scorecard

Reporting definitions are the written meaning of each number, agreed before anyone compares branches. Without them, one branch counts every tap on the call button as a lead, another counts only booked jobs, and the comparison tells you nothing.

Start with what Google counts. Business Profile Help defines calls as the number of times a customer clicked the call button on your profile. That's a tap, whether or not anyone answered. Views are counted per person, and a person is counted once a day. Google Analytics defines a key event as an event that measures an action that's particularly important to the success of your business, so pick key events that mean the same thing at every branch.

Then write your own terms down. A call might mean a connected call from a new customer, logged by the branch. A lead might mean a form submission or logged enquiry call, counted once per customer per week. A branch's traffic might mean visits to that branch's pages or its tagged profile link. The reporting period should be the same for every branch, such as a calendar month. For matching calls to a call log, read call tracking and conversion reconciliation, and for splitting paid and organic enquiries, see paid search versus organic lead attribution.

Check whether your tools can split by branch before promising a branch report. Google Analytics Help says one property can link to several Business Profiles, but once more than one is linked you can't segment or filter those metrics by an individual profile, and the linked data covers only the last 6 months. Set these up before the first branch report goes out:

• Pull each branch's performance straight from Business Profile, one profile at a time.
• Tag each profile's website link with campaign parameters, with the branch name in utm_campaign. Analytics Help says to always use utm_source, utm_medium and utm_campaign together.
• Set a content group for each branch's pages. Analytics Help describes content groups as custom buckets for related pages.
• If branch pages sit in their own folders, add a Search Console property for each. Search Console Help suggests one per subpath you want to track, plus one that contains them all.

Worked example: putting a three-branch business under one plan

Here's the method applied to the hypothetical pest control business in Caloundra, Nambour and Gympie. Every finding is illustrative.

Before changing anything, head office lists every branch's current footprint: which login owns each profile, who has access to each Google tool, which pages target which suburbs, and how each branch counts leads. Say the audit finds that the Nambour profile's primary owner is a former manager's personal account, two pages target Buderim, Gympie has no branch page, and Caloundra counts every call-button tap as a lead while the others count booked jobs. Gympie, with no page at all, goes first, because it has the biggest gap. Then the steps run in order:

1. Choose hybrid. Branch managers keep hours, photos and review replies; head office keeps the name, categories, templates, tracking and access.
2. Write the register: three rows, store codes PEST01 to PEST03, one primary category shared by all three, and each branch's suburbs listed once.
3. Fix access. Head office asks the former manager to transfer primary ownership of the Nambour profile to a business-controlled account, allowing for the 7-day wait before the new owner can remove users, then removes the old login.
4. Settle the Buderim overlap. The register gives Buderim to Nambour, the duplicate page is merged into the Nambour page, and the old URL redirects to it.
5. Build the Gympie page from the template, with the Gympie manager supplying photos, common jobs and local questions, and point the Gympie profile's website link at it.
6. Issue the review policy to all three branches and log the first month's replies in the register.
7. Agree the definitions: a lead is a form or logged enquiry call, once per customer per week, and every branch reports by calendar month.
8. Book a quarterly check with each branch owner: register rows against live profiles and pages, users on every tool, leavers and their Search Console tokens, profile links, and new suburb pages that overlap.