A franchise network on Google Maps is not one brand with a lot of pins. It is a set of individually ranked listings that happen to share a logo, and each one competes on its own merits in its own town. The strongest unit in the network gets no credit for the weakest, and the weakest drags the brand average down in the exact postcode where a new franchisee is trying to build a book of customers.
So most of the work in multi-location GBP is not optimisation. It is governance: who may change what, what happens when a unit changes hands, and how you publish to sixty listings without producing sixty identical posts.
Who owns the listing: brand or franchisee
Settle this before you touch a single field. There are three arrangements in practice, and only one survives a franchisee leaving on bad terms.
- Franchisee owns everything - the listing sits on a personal Gmail account. Fine until they exit, at which point the brand has no access, no reviews and no history in that town.
- Brand owns everything - clean, but the profile goes stale because nobody local can update hours when the car park is being resurfaced.
- Brand owns, franchisee manages - the franchisor holds the primary owner seat on the location group, and each franchisee is a manager on their own location only. This is the one to write into the franchise agreement.
Keeping listings inside a location group means ownership sits with an organisation rather than a person, and access can be revoked per location. State in the agreement that the profile, its reviews and its photos are brand assets licensed for the term.
Consistency rules worth enforcing centrally
Not every field deserves a policy. These do, because getting them wrong either breaks the brand or gets a listing suspended.
| Field | Controlled by | Why |
|---|---|---|
| Business name | Brand, locked | Must match the signage exactly. No city, no keywords, no "Best". |
| Primary category | Brand, locked | Sets what the listing is eligible for. One accidental change moves a unit out of its main query set. |
| Logo and cover image | Brand | Recognition in the map pack. |
| Business description | Brand, with a local slot | Consistent proposition, local flavour at the end. |
| Services and products | Brand, franchisee can disable | Not every unit offers everything. Listing what you do not provide creates bad calls. |
| Website URL | Brand | Each location points to its own store page, never a shared locator page. |
The name field is where networks get into trouble most often. Adding the town looks harmless and is a common suggestion from well-meaning consultants, but it is a violation unless the town genuinely appears on the shopfront. Suspensions hurt more in a network, because a competitor who reports one unit tends to look at the rest next.
The URL rule matters more than it looks. Every location needs a real page with its own address, hours, staff and phone number. Forty listings pointing at one homepage wastes the strongest relevance signal you control.
What to leave to local discretion
Franchisees run the unit. They know the school run traffic, the market day, the fact that the retail park entrance changed. Lock them out of everything and the profile decays.
- Opening hours and special hours - only the local operator knows about the bank holiday rota, the stock-take closure or the day the road is shut for the carnival.
- Photos of the actual unit - the team, the counter, the van. Brand-shot imagery on every listing makes the whole network look like a stock library.
- Review replies and Q and A - a reply from someone who was there on the day reads completely differently from a centrally written one, and parking and accessibility questions are purely local.
- Local posts - a school fundraiser, a new staff member, a local sponsorship.
The phone number is the genuinely contested field. Central handling gives you tracking and consistent scripts; a local line usually converts better and copes with the awkward questions. If you do route centrally, make sure the number reaches someone who can answer for that specific unit.
Bulk publishing without sounding like head office
Bulk publishing is the reason a management platform exists, and also the fastest way to make a network look automated. Treat central content as a frame rather than a finished asset: build the post with the offer, the dates, the legal wording and the image, then leave a slot the franchisee fills with the local detail. Give them a deadline and a default, so an unfilled slot still publishes something sensible.
Keep a shared media library so franchisees are not sourcing their own versions of the seasonal creative from a WhatsApp group.
Reporting up and reporting down
Two audiences, two completely different reports, and most networks only build one.
Reporting up is for the franchisor: comparative and exception-driven. Which locations sit below the network median on calls or direction requests, which have reviews unanswered past the agreed window, which have not posted this month, which have hours untouched since opening. Nobody at head office wants forty dashboards. They want the ten that need a phone call.
Reporting down is for the franchisee, and it answers one question: what should I do this month. Their own numbers with last month beside them, their unanswered reviews, and two or three specific actions. Send a franchisee a league table where they sit twenty-eighth and you get defensiveness. Send them three tasks and you get compliance.
On metrics: calls, direction requests, website clicks and profile views are tied to actual demand, and Search Console shows the queries reaching that location's page. Map position varies by the searcher's own location, so a single "we rank third" figure is not something to build a franchise report around.
Where a management platform fits
Ampli5 Pulse is built for this shape of problem: a multi-location dashboard, post scheduling across locations, a shared media library, and role-based team access so a franchisee sees only their own location while a regional manager sees the group. Review replies are AI-assisted and you approve each one before it publishes, which holds the brand voice steady without central marketing writing every reply. Performance insights cover calls, directions, clicks and views alongside Search Console, and reports can be white-labelled. It is not a rank tracker.