Should contractors create a page for every city?

A contractor should not create a page for every city simply because a keyword tool shows search volume. Create a city or service-area page when the business genuinely serves that market and the page gives local customers information they cannot get from a generic service page. If the only change is the city name, the page is unlikely to help a customer—and may resemble the doorway abuse Google explicitly prohibits.

“We cover 40 towns. Do we need 40 pages?” is the wrong first question. The better one is: “Would a customer in each town need a meaningfully different answer before calling us?” Sometimes the answer is yes. Coverage, arrival time, building stock, weather exposure, permits, equipment and available services can vary. Often the answer is no.

This distinction matters because location pages sit between legitimate local information and an old SEO shortcut: generate hundreds of near-identical URLs, replace one place name with another and hope each ranks. Google’s spam policies describe doorway abuse as pages created to rank for similar queries that funnel users to an intermediate destination. The issue is not the existence of city pages. It is their purpose and value.

Service page, area page or service-and-city page?

Most contractor sites need fewer page types than agencies sell them.

• Service pages explain a distinct job: roof replacement, boiler repair, drain clearing or panel upgrades. They answer scope, process, suitability and buying questions.
• Service-area pages explain how the company serves a real territory: coverage, local availability, relevant services, project evidence and next steps.
• Branch pages represent genuine operating locations, with accurate contact details, staff or service responsibility.
• Service-and-city pages can make sense when local demand and the offer are materially distinct. They become wasteful when every service is crossed with every town.

A roofing company may need one strong “roof replacement” page and three substantial market pages. It probably does not need 60 URLs combining five services with 12 suburbs. Site architecture should mirror the business, not a spreadsheet multiplication exercise.

When a city page deserves to exist

Use four tests before creating the URL.

1. The business can actually serve the area

Confirm drive time, technician coverage, licensing, job value and capacity. A page that ranks outside an economical dispatch radius produces bad leads and frustrated searchers. In the US that may mean a specific metro and ZIP-code cluster; in Canada, a municipality or part of a province; in the UK, towns and postcodes that crews genuinely cover.

2. The market matters commercially

Prioritise areas with enough demand, suitable jobs and operational capacity. Search volume alone is not a business case. A smaller nearby town with strong close rates may be worth more than a famous city that consumes two hours of travel.

3. Customers need local information

Local differences should change the page. Roofing materials and storm exposure, heating systems, hard-water issues, older pipework, housing type and local response constraints may all matter. Use only details that affect the service; decorative facts about a town do not demonstrate expertise.

4. The company has evidence

Real project photos, neighbourhoods served, locally relevant reviews, team coverage and common job types make a page credible. Do not fabricate case studies or imply a local office. If evidence is still thin, strengthen the core service page and collect operational proof before expanding.

What turns location pages into doorway pages?

Google’s examples include multiple pages targeted at specific regions or cities that funnel users to one page, and substantially similar pages closer to search results than a clear browseable hierarchy. Warning signs on a contractor site include:

• the same paragraphs with only place names changed;
• dozens of pages created at once without corresponding operations;
• pages that all redirect or push visitors to the same generic lead form;
• invented office addresses, staff or project claims;
• long lists of suburbs written for keywords rather than customers;
• orphan URLs that cannot be reached through normal navigation;
• pages with no useful answer beyond “we serve this city.”

Not every similar sentence is a problem. Business names, warranties and processes naturally repeat. The page needs enough unique reason to exist as a whole. Google’s people-first guidance asks whether visitors leave feeling they learned enough to achieve their goal. That is a better editorial test than chasing an arbitrary percentage of “unique text.”

A useful page blueprint

A strong service-area page does not need tourist history or 2,000 words. It needs specific, decision-useful information in a sensible order.

1. Clear coverage statement. Say what the company does in the area and any meaningful boundaries or availability.
2. Relevant services. Link to the detailed service pages instead of duplicating them in full.
3. Local operating context. Explain property, climate, equipment or scheduling factors that genuinely affect the work.
4. Evidence. Show authentic projects, reviews or team information tied to the territory when available.
5. Customer questions. Answer response time, estimates, permits, emergency availability, financing or warranties where applicable.
6. Precise next step. Provide a click-to-call number and a short request path that preserves the selected service and area.

Write the title, main heading and introduction plainly. “Roof repair in Leeds” is more useful than a string of variations such as “best affordable local roofers Leeds near me.” Natural terminology helps both readers and search systems understand the offer.

Do you need an office in every target city?

No. A service-area contractor can honestly describe where crews travel without pretending to have a branch. A website location page and a Google Business Profile are not the same thing. Google Business Profile has separate rules for service-area businesses, addresses and multiple locations; our service-area profile guide explains those requirements.

Create a branch page when there is a real operating location with distinct responsibility and accurate details. Do not use virtual offices or borrowed addresses to manufacture proximity. On the website, language such as “serving Bristol from our regional team” is clearer than presenting an office that customers cannot visit.

How many pages should you launch?

There is no magic number. Start with a small group you can make genuinely useful and measure. For many contractors, three to six priority areas are a more sensible first release than every postcode in the CRM.

After publication, use Search Console to review queries, impressions, clicks and pages. Pair that with call and booking data. A page attracting searches from outside the dispatch area needs tighter coverage. One earning relevant impressions but few clicks may need a clearer title and proposition. A page generating traffic but no qualified enquiries may target the wrong intent.

Expansion should follow evidence: real jobs, new capacity, customer questions and demonstrable market opportunity. Our guide to realistic contractor SEO timelines explains why indexing and relevant impressions should be evaluated before declaring success or failure.

Canonical tags are not a cure for weak pages

Canonical tags help Google understand which URL represents duplicate or very similar content. They are useful when technical duplicates are necessary—for example URL parameters or alternate versions. They are not a way to publish 30 thin city pages while asking Google to treat each as unique.

If two area pages do not deserve separate search results, consolidate them into a stronger regional page and redirect the retired URL where appropriate. If both deserve to exist, give each distinct information and use a self-referencing canonical. Keep important pages linked from a crawlable service-area hub or relevant navigation.

Practical examples by trade

Roofing

A useful local page may address roof types common in the area, storm or coastal exposure, inspection availability and recent local work. Link to the detailed roofing marketing and service strategy rather than repeating every roofing service.

HVAC and heating

Equipment and language vary by market. Air conditioning, furnaces and heat pumps may dominate one US or Canadian area; boilers and heating engineers may be more relevant in the UK. Local pages should reflect services actually offered, not imported keyword lists. See our HVAC growth approach.

Plumbing

Dispatch radius, emergency coverage, older housing, water conditions and sewer responsibility can alter the buyer’s questions. Make those answers local and connect them to the right plumbing service pathway.

What to ask an agency before approving city pages

• Why does each proposed page deserve its own URL?
• What operational or customer evidence will make it distinct?
• How will customers and search engines reach it naturally?
• Which existing page targets the same intent?
• How will qualified calls and booked jobs be attributed?
• What happens to pages that show no useful demand?

An agency should be able to answer those questions before producing copy. If the plan begins with “one page per city” and ends with rankings, it skips the customer and the operation. Use our agency selection checklist to examine ownership, reporting and promises as well.

Frequently asked questions