Original framework
Page-responsibility matrix
Assign every page one primary job before choosing keywords, headings or internal links.
When a service page should lead
Use a service page when the principal decision concerns the work itself: suitability, inclusions, process, credentials, pricing factors or how to enquire. It can mention genuine coverage without being duplicated for every place.
When a location page should lead
Use a location page when geography materially changes the customer decision. The page should connect real operations to available services and link to the detailed service destinations rather than restating them.
When a coverage hub is enough
A coverage hub can explain a shared service radius, region or group of areas when separate pages would add little value. It creates a clear route from services to geography without forcing thin city templates.
How the pages should link
Link service pages to justified locations where the service is genuinely available. Link location pages back to the relevant services. Use descriptive anchors and maintain a crawlable route from navigation or an industry hub to commercially important pages.
- Service → relevant location
- Location → available service
- Coverage hub → justified child page
- Industry guide → relevant service and local framework
- Business Profile → the most useful accurate destination
Common architecture mistakes
Avoid making every service-and-city combination indexable, pointing all internal links to the homepage, creating branch pages for unstaffed addresses, or allowing two pages to compete for the same primary intent.
A keyword spreadsheet cannot resolve these issues without operational information and a page-ownership decision.
Measure each page by its role
Service pages should support qualified service enquiries; location pages should support relevant local discovery and contact; coverage hubs should help customers choose a useful destination. Compare assisted journeys as well as last-click conversions.