Multiple metros, one company.
How to structure a site covering several service areas without the pages cannibalising each other.
Hub and suburb structure
One page per metro acting as a hub, with suburb pages beneath it, each linking up to its metro and across to its nearest siblings. Every location needs a verified Business Profile with a genuine address and staff, and each metro hub needs content specific to it: crews, response times, local projects, and the permitting reality there.
What makes a metro hub distinct
Six things, and if you cannot supply them the metro is not ready for a page.
The cannibalisation problem
Companies that grew by adding pages usually end up with dozens of near-duplicate suburb pages competing with each other, and often two metro pages competing for the same city. The fix is a redirect map: retire the thin pages into fewer strong ones so nothing that had earned authority loses it. Expansion after that is cheap. Expansion before it multiplies the problem.
Where the borders sit
Decide which metro owns each suburb, once, and link accordingly. Suburbs on a boundary should sit under one hub and be linked from the other, not duplicated under both. This is a fifteen-minute decision that prevents a year of two pages splitting the same signal.
Profiles, not just pages
Each genuine location needs its own verified profile with a distinct address, phone number, and hours, and each should link to its metro hub rather than the homepage. Shared call centre numbers across locations weaken the local signal, and profiles pointing at a single generic homepage waste the strongest link the profile can give you.
When not to expand
If you cannot staff a metro, do not publish a page claiming you serve it. Enquiries you cannot service become cancellations and bad reviews, and the reviews follow the profile for years. The order that works is capacity, then a real presence, then the pages, then the profile. Reversing it produces traffic you have to apologise for.
Reporting per metro
Segment enquiries, close rates, and acquisition cost by metro rather than blending them. It is common for one market to carry the business while another consumes margin, and a blended report hides both facts. That segmentation is also how you decide where the next build effort should go.
Boundary suburbs need an owner
Every metro has suburbs that could sit under either hub. Decide once, write it down, and link accordingly. The rules that work: assign by which office actually dispatches there, keep the suburb under one hub only, link to it from the neighbouring hub rather than duplicating it, and never publish the same suburb under two metros because it feels closer to both. This is a fifteen-minute decision that prevents a year of two pages splitting the same signal.
One domain or several
One domain, almost always. Separate domains per metro split authority, multiply maintenance, and require each to earn trust from nothing. The exceptions are genuine separate brands or separately owned entities, where a shared domain would misrepresent who the customer is contracting with. If the company is one business trading in four metros, it is one site with four hubs.
When a metro should be retired
If a market has produced no work for a year and no crew covers it, retire the pages rather than leaving them claiming service you cannot deliver. Redirect them to the nearest metro hub, update the profile or remove it, and keep the reviews attached to the location that actually earned them. Stale metro pages generate the enquiries you have to apologise for, which is worse than not appearing at all.
Related guides.
The setup that drives enquiries without ad spend, and the clerical errors that quietly cap a listing.
Dedicated local pages outperform one generic service page. Thin copies of each other do not.
City pages, Google Business Profile, storm content, and what actually moves map-pack visibility for a roofer.
See what your market rewards.
$2,500, and you get the city-by-city order to build in.