Why One Website Can Serve Three Shops — But Only If You Build It Right
Opening a second or third location is a big deal. Most owners celebrate, update their Instagram bio, and then do the laziest possible thing to their website: duplicate the existing location page, swap the postcode, and call it done.
Google notices. It sees near-identical pages, can't work out which one to rank for which search, and usually picks none of them. Meanwhile, Just Eat and Deliveroo — who do have location-specific pages — keep outranking you in every town you've just expanded into.
The good news: the right structure is straightforward. One brand domain. A proper page per location. Each page doing its own local SEO work. This playbook covers exactly that.
The Domain Decision: One Brand Site vs. Separate Sites Per Location
You'll hear people argue both ways. Here's the honest answer.
Separate domains for each location — say burgerpalace-manchester.co.uk and burgerpalace-birmingham.co.uk — split every bit of authority your brand builds. Links, reviews, traffic: all fragmented. You'd have to do twice the SEO work forever.
One domain, with each location as a page or subfolder, pools that authority while letting you target different local searches. The structure that works:
- yourrestaurant.co.uk/manchester/ — for your Manchester shop
- yourrestaurant.co.uk/birmingham/ — for Birmingham
- yourrestaurant.co.uk/sheffield/ — for Sheffield
- yourrestaurant.co.uk/menu/ — one central menu that feeds into every location page
This gives you local landing pages that can rank in their own map packs, plus a central brand that grows with every review, link, and visit across all three sites.
What Every Location Page Needs — And What It Must Not Share
Here's where most multi-site builds go wrong. They use the same paragraph of text on every location page, just with the town name swapped. Google classifies this as thin or duplicate content and downgrades the lot.
Each location page must have unique content. That doesn't mean writing a novel — it means covering the things that are genuinely different about that shop.
- Address and map embed — unique to this location, full street address, postcode
- Opening hours — don't assume all shops keep the same hours
- Phone number — a direct line where possible, not a shared central number
- Parking and access notes — useful for customers, differentiating for Google
- Local landmarks — 'two minutes from Piccadilly Gardens' is both helpful and unique
- Location-specific offers or specials — if your Birmingham shop runs a Tuesday deal, say so
- Reviews sourced from that location's Google profile — pull these through if your platform allows
- A link to that location's individual Google Business Profile — never to your account overview
The menu can be shared — that's fine and expected. But wrap it in page-level content that is genuinely written for that postcode.
One Google Business Profile Per Location — No Shortcuts
Google Business Profile (GBP) is not optional for local food businesses. It's the difference between appearing in the map pack and being invisible to anyone searching 'Chinese takeaway near me' in your town. For multi-location restaurants, the rule is simple: one verified GBP per physical address.
Each profile should have:
- The exact name, address, and phone number (NAP) that matches your website location page
- Its own set of photos — not a copy-paste from the original shop
- The correct primary category (e.g. 'Takeaway Restaurant' or 'Indian Restaurant')
- A link pointing to that location's specific page on your site, not the homepage
- Its own stream of recent reviews — see the section on reviews below
If your NAP details don't match exactly between GBP and your website, local rankings suffer. This consistency matters more than most owners realise. You can read more on getting the details right in our guide to Google Business Profile for UK takeaways.
Manage all your profiles through Google Business Profile Manager — one login, multiple locations, far less chaos than separate accounts.
Winning the Map Pack in Each Town
The map pack — the three listings that appear with a map when someone searches for food near them — is the most valuable real estate in local search. Getting into it for 'pizza delivery Manchester' and 'pizza delivery Birmingham' are two completely separate battles.
Each location needs to build its own map pack presence. The main signals Google looks at:
| Signal | What it means for each location |
|---|---|
| GBP completeness | Profile fully filled in, correct category, recent posts |
| Review recency and volume | Consistent new reviews on that location's specific profile |
| Location page on your site | Unique content, full NAP, embedded map, schema markup |
| NAP consistency across the web | Address matches on Yelp, TripAdvisor, local directories |
| Proximity to searcher | Can't change this, but good signals compensate |
| Engagement signals | Calls, directions requests, website clicks from the profile |
The full breakdown of how to compete for map pack positions is in our guide to winning the map pack for cuisine near me searches.
Reviews: One Profile's Reviews Won't Do the Work for Another
This surprises owners who've built a strong review base at their original site. Those 200 five-star reviews are attached to that location's GBP — they don't transfer to Manchester or Sheffield.
Each new location starts from zero. That's why a review generation process needs to be in place from day one at every shop, not added as an afterthought six months later.
The compliant way to ask for reviews: make it easy and timely. A QR code on the receipt, a card handed over with collection orders, a follow-up via order confirmation email. The ask should always be open — 'leave us a review' — never 'leave us a good review if you're happy'. Gating or filtering (only sending review links to customers who rated you highly first) is not compliant with DMCC guidelines and should be avoided entirely.
Never buy reviews. Never post fake ones. Beyond the ethics, Google removes them, and the DMCC has enforcement powers that are actively being used.
Central Menu Management Without Losing Local Flexibility
Managing three menus across three platforms — your website, GBP, Flipdish, Just Eat — is where multi-site operators start to feel the pain. A price change at one shop can mean four separate updates if you haven't built it properly.
On your website, the sensible structure is a single menu page that each location page links to. If one location has a slightly different menu — a Sunday special, a smaller range — that's a section within the menu page or a note on the location page, not a whole separate menu document.
The broader principle: your menu on your site should be real text with structured schema markup, not a PDF or image. Google can't read a JPEG. Real text means your dishes show up in search — 'lamb rogan josh Birmingham delivery' — in a way a scanned menu never will. If you're still relying on PDF menus, the implications are covered in detail in our post on why PDF menus are invisible to Google.
For ordering, if you're already on Flipdish, Slerp, or Storekit, the Growth plan wires those into your website — so the order buttons route correctly per location. Keep the third-party apps for delivery; consider joining the waitlist for Takely Ordering for your own-site collection orders when it launches.
Tracking Which Location Is Actually Pulling Its Weight
Once you have multiple locations, website analytics becomes genuinely useful — not just a vanity dashboard. You want to know: which location page gets the most traffic? Which converts visitors into orders? Which one is losing people at the menu?
The setup to get this working:
- Each location page tracked as a separate section in Google Analytics 4 (using the /manchester/, /birmingham/ subfolder structure)
- Order button clicks tracked as conversion events, tagged by location
- GBP profile clicks (calls, directions, website visits) reviewed monthly per location in the GBP dashboard
- UTM parameters on any location-specific links — in email, in GBP posts, in printed materials — so you can see where traffic is actually coming from
With this in place, you can see within a month if one location's page is underperforming and act on it — rather than assuming all three are fine because the total order volume looks OK.
For operations at this scale — up to ten pages, multi-location setup, franchise potential, full analytics — that's where the Bespoke plan at £1,999 + £129/mo comes in. Four to six weeks to build it properly, rather than bolting on a second location to a site that wasn't designed for it.
A Quick-Reference Checklist for Each New Location
When you're ready to add a new location to your site, work through this list before you go live:
- Create the location subfolder (yourrestaurant.co.uk/newtown/)
- Write unique page content — address, hours, local context, nearby landmarks
- Embed the Google Map for this address specifically
- Add LocalBusiness schema markup with this location's NAP details
- Verify a new Google Business Profile for this address
- Set the GBP website link to this location's specific page
- Upload location-specific photos to GBP (exterior, interior, team if possible)
- Set up a review collection process from opening day
- Check NAP consistency on TripAdvisor, Yelp, local directories
- Connect order buttons to the correct platform endpoint for this location
- Set up location-level conversion tracking in GA4
- Submit the new URL to Google Search Console
Frequently asked questions
Can I use the same website text for two locations if the menu is identical?
No. Even if the menu is the same, the location pages need unique text to rank independently. Google sees duplicate pages as thin content and typically won't rank either of them well. Write unique content about the area, parking, local landmarks, and any location-specific offers. The menu itself can be shared — it's the surrounding page content that must differ.
Do I need a separate Google Business Profile for each restaurant location?
Yes, one verified GBP per physical address. A single profile for multiple addresses isn't how GBP works, and you'd lose map pack visibility for every location except whichever one you list first. Manage them all through Google Business Profile Manager to keep things organised under one login.
Should I use subfolders or subdomains for my restaurant locations?
Subfolders (yourrestaurant.co.uk/manchester/) are the better choice for most food businesses. They keep all your domain authority in one place, are easier to manage, and perform just as well for local SEO as subdomains. Subdomains (manchester.yourrestaurant.co.uk) are treated more like separate sites by Google, which splits your authority unnecessarily.
How do I get reviews for a brand new location when we're starting from scratch?
Start immediately. Put a QR code linking to the new location's GBP review page on every receipt and on the counter. Train staff to mention it to regulars. Keep the ask open-ended — 'we'd love a review' not 'please leave five stars'. Aim for a steady trickle of genuine reviews over weeks rather than a sudden burst, which can look suspicious to Google.
How do I track which location on my website is driving the most orders?
Use Google Analytics 4 with each location page tracked as its own section via the subfolder URL structure. Tag order button clicks as conversion events and filter by location path. Also check your Google Business Profile dashboard monthly for each profile — it shows calls, direction requests, and website clicks per location, which tells you how well each GBP is performing independently.
When does it make sense to build a franchise page alongside my location pages?
Once you're running two or three locations profitably and fielding genuine enquiries from people who want to open their own. A franchise or business opportunity page on your main domain can capture that interest and qualify leads without you having to handle every enquiry manually. Our guide to [building a franchise page](/blog/franchise-page-franchisee-leads) covers what to include and how to structure the enquiry flow.
Keep reading