SEO Regional

I start by defining the region from keyword data. For a roofing company covering four counties in the South West, I ran a spreadsheet: 'roofer [county]' and 'roofer [town]'. Somerset had 650 monthly searches, Devon 580, Cornwall 420, Dorset 300. The top 15 towns summed to 2,100. The regional term 'roofer South West' only had 120 but 'roofer near me' with location context added another 400. I decided to build a South West regional hub and city pages for towns with over 100 monthly searches. That gave me a hub plus nine city pages.

The hub page includes a map of the service area, a video of a recent roof replacement in Exeter, testimonials from clients in all four counties, and a paragraph about local building regulations. Each city page then features a case study from that town – for example, a thatched roof repair in Tiverton – and a local landmark reference. I link from the hub to each spoke with the town name, and each spoke links back to the hub with an anchor like 'roofing across the South West'.

The decision rule I use now: if the combined search volume of city terms is less than twice the regional term, I skip city pages and incorporate town sections into the hub. In the example above, the regional term 'South West' plus 'near me' gave 520, while city terms summed to 2,100 – ratio about 4:1, so city pages were justified.

I also ensure the site architecture is flat: hub at /roofing-south-west/, city pages at /roofing-south-west/exeter/, etc. No more than two clicks from the home page. I link from the hub to spokes, and spokes link to each other for nearby towns. I add breadcrumb structured data and use [local SEO](/local-seo/) principles throughout. I also set up the Google Business Profile as a service-area business, listing all the counties as service areas, rather than listing a single address on each city page.

The biggest mistake I see is creating thin doorway pages. I once audited a locksmith who had 40 pages swapping 'locksmith [city]' – zero unique value. Google can spot this with entity analysis. If you only change the city name and a phone number, you risk a manual action. Each city page must have independent content: a different service story, a local partnership, or a unique problem solved (e.g., 'broken key in a Vauxhall Corsa' for one town).

Do not ignore broader queries. Terms like 'locksmith near me' or 'emergency locksmith [county]' often have higher combined volume than exact city terms. My client's 'locksmith near me' in the region drove 3x more calls than any single city page. So the regional hub should target those phrases, and the city pages should target 'locksmith [city]' and '[city] emergency locksmith'.

NAP drift is another pitfall. If you list a different address on each city page but use the same phone number, Google may get confused. For a service-area business, set up [Google My Business](/google-my-business/) as service-area and use the same office address across all pages, or use no address on city pages. I recommend using the head office address on the regional hub and marking the business as service-area in GBP. Then on city pages, omit the address or use a generic 'serving [city] area'. Ensure [citation SEO](/citation-seo/) consistency on directories like Yell and Thomson Local with the head office NAP and include service areas in the description.

Cannibalisation can happen when the regional page and city page both try to rank for 'plumber [town]'. To avoid this, I assign the regional page to target 'plumber [region]' and 'plumber near me', and city pages target 'plumber [town]' and 'plumber [town] area'. Use unique title tags and H1s. If I see overlap, I adjust internal linking signals. I also run a [local SEO audit](/local-seo-audit/) every quarter to catch these conflicts.

Edge case: if your region spans two different area codes for phone numbers, use one central number and a local presence page with a local number only if you have a physical office. Otherwise, just use one number. Also, review the [local SEO checklist](/local-seo-checklist/) to ensure nothing slips through.

Early in my career, I worked with a carpet cleaning company that served 12 suburbs of Birmingham. I created a separate page for each suburb, copying the main body and only changing the suburb name in the title and first sentence. The result: Google indexed all 12 but ranked none in the top 50. The regional hub page I later built for 'Birmingham carpet cleaning' ranked within a month. I learned to group suburbs into one hub with a few high-volume city pages.

I also completely ignored Google Business Profile service-area setup. I listed the company's single address on every city page, thinking it would help local ranking. Instead, Google showed the same address for all searches, which confused users and hurt trust. Now I set GBP as a service-area business, select all relevant cities as service areas, and only mention the physical address on the regional page.

I used to think I needed a unique phone number for each city to track calls. That caused citation inconsistencies and split local signals. Now I use one central number and track calls with a call tracking platform that shows which page the call came from.

I changed my mind about the value of 'near me' queries. I used to ignore them because they didn't include a city name, assuming they were too vague. But data from Google Search Console showed that 'carpet cleaner near me' in Birmingham drove more traffic than any individual city term. I now optimise the regional hub page for that phrase.

Another admission: I didn't monitor regional keyword rankings. I only tracked city terms. So I missed that the regional page was ranking for several county-level terms. Now I track both sets and compare the conversion rates. I also learned that [local SEO pricing](/local-seo-pricing/) models often undervalue regional pages – clients are happier to pay for a strategy that covers a whole metro area. And if you're struggling to scale, hiring a [SEO Agency London](/seo-agency-london/) that understands regional structuring can save months of trial and error.