Location Pages vs. Service Pages: Avoiding Cannibalization
How to separate location and service pages so they don't compete.
Location pages and service pages serve different purposes, but when they overlap they cannibalize each other — two pages competing for the same query, neither ranking well. This guide explains how to separate them. See Local Content Strategy for the architectural context.
The cannibalization problem
Cannibalization occurs when multiple pages target the same query. Google cannot decide which page to rank, so it may rank neither well. The most common cause is creating a page for every service-city combination (e.g., 'plumbing [city]', 'drain cleaning [city]', 'water heater [city]') — dozens of thin pages that overlap.
The separation pattern
| Page type | What it covers | Target query |
|---|---|---|
| Service page | What the service is, how it works, pricing approach | [service] (no location) |
| Location page | Where the business operates, service area, local trust signals | [business type] [city] |
| Service + location | Link the two; do not create a separate page per combination | Covered by the location page |
Link service pages to location pages and vice versa. A service page about 'drain cleaning' links to the location page for '[city]'. The location page lists all services offered there. This avoids the combinatorial explosion of service-city pages.
Detecting cannibalization
Use Search Console to find multiple pages ranking for the same query. If two pages both appear for '[service] [city]', they are cannibalizing. Merge them or differentiate their intent. See Potential Cannibalization: How to Detect and Resolve It.
Primary sources
- Google Search Central documentation — Google (accessed 2025-01-15)