Multi-location social media fails in one of two directions. Either head office controls everything and the local pages read like a press release from another country, or every location does as it pleases and the brand shows up in twelve different fonts and one lawsuit. The workable model sits between them, and it is mostly a question of deciding in advance who owns which post.
Should each location have its own page?
Yes, if it has its own address and its own opening hours.
The reason is search rather than social. A Google Business Profile per location is what makes each branch findable, and local pages let a customer see the actual staff at the actual branch. A single national account cannot do either.
The exception is a location so small it will never post. A dormant local page with three followers and a last post from 2024 is worse for the brand than no page. If a branch cannot commit to something monthly, keep the Google Business Profile, which needs less, and skip the social page.
Who owns what?
This is the whole decision. Write it down, because every argument later is a version of this question.
| Layer | Owns | Typically publishes |
|---|---|---|
| Head office | Brand campaigns, national offers, product launches, crisis messaging | To brand accounts, and as ready-made assets for locations |
| Location | Staff, events, local partnerships, community posts, opening hours | To its own local pages and Google Business Profile |
| Shared | Seasonal campaigns, promotions with local dates | Head office writes it, location adapts and publishes |
The middle row is the one that gets stolen by head office, and it is the row that makes the whole thing work. Nobody at head office knows that the branch manager ran the school fundraiser. That post outperforms the national campaign at that location, every time.
The bottom row is where the process lives. Head office prepares a campaign as a kit: the image, the caption, the dates, and the parts a location is allowed to change. Locations fill in the local detail and publish. Nobody writes from scratch and nothing goes out off-brand.
How much freedom should locations get?
Enough to sound like a place, not enough to redraw the logo.
A practical rule: locations control the words and the photographs, head office controls the brand assets, the claims and the offers. Anything with a price, a legal claim, a national promotion or a comparison to a competitor is head office’s, without exception. Anything about the people in that building is the location’s.
Give each location:
- A folder of approved images and video they can use anytime.
- A short list of what they must never post, phrased as examples rather than policy language.
- A named person to ask, with a response time. An unanswered question becomes an unapproved post.
That last item is the one that actually determines whether the system works. A location that waits four days for an answer stops asking.
Where do approvals fit?
On the shared row, and on new locations, and nowhere else.
Approvals applied to everything get rubber-stamped within a month, and then they are a delay rather than a control. Applied narrowly they are useful:
- New locations or new managers, for the first sixty days, so somebody sees the tone before customers do.
- Anything with a price, an offer or a claim, permanently.
- Anything during a live brand issue, temporarily and explicitly.
Everything else goes out without a queue. A photo of the team at a local event does not need a regional marketing manager to read it first, and pretending it does is how a system built for safety turns into a system nobody uses.
How do you keep it consistent without making it identical?
Two things, and neither is a brand guideline document.
A shared calendar. Everyone can see what the national campaign is doing this month and when. Most brand inconsistency is not defiance, it is a location not knowing a campaign was running.
A rhythm rather than a script. A structure like “one product post, one people post, one local post, one useful post” per fortnight produces posts that clearly belong to one brand while being visibly different in each town. A per-post script produces twelve identical feeds, which is what customers ignore.
Measure per location and compare like with like. A branch in a town of 4,000 will never match a city centre site, and ranking them on followers just teaches managers to buy them. Growth rate and click-throughs are the fairer comparison, and there is a reporting template worth copying.
The short version
- One Google Business Profile per location, always. A social page only if the branch will actually post.
- Head office owns brand, claims and offers. Locations own people, events and their own community.
- Ship campaigns as kits with local blanks, not as finished posts to copy.
- Approve new managers, priced offers and live issues. Approve nothing else.
- Compare locations on growth rate, not on follower count.
Running the whole estate from one calendar
The practical version of the model above needs three things from a tool: accounts grouped per location, a shared calendar everybody can see, and an approval step you can point at some posts and not others.
BulkPublish does that. Each location’s channels can be their own group, so the calendar filters to one branch at a time, posts and media carry labels so a national campaign can be pulled up across every location at once, and a post can be held for approval without every post being held. Google Business Profile is published to alongside the social networks, which matters more here than anywhere else. The agency guide covers the same grouping problem from the other side, and the pricing page lists the channel count each plan connects, which is the number that decides how many locations fit.