Walkthrough
One service page for every city you serve
Owners ask whether each town needs its own page or whether one page will do. The answer depends on how different the work is from place to place.

Build it in this order
- 1
List the places that pay
Pull your last 50 jobs and count them by town. The top five towns get pages first.
- 2
Make each page useful on its own
Name streets, show real jobs, and add a map. Hundreds of copied pages that differ only by a city name get you nowhere.
- 3
Embed a map and your details
Put the address, hours and phone on the page, identical to your Google Business Profile.
- 4
Link the pages together
Add a short list of nearby towns at the bottom of each one.
- 5
Then point links at the pages
Aim a bought link or a local mention at the city page it fits, not at the homepage.
Split pages or one big page?
Split when the service really differs. A roofer in Tampa and one in Tallahassee face different storms, codes and insurance rules, so two pages make sense.
Keep one page when the work is the same everywhere and the towns sit close together. Padding it with ten thin copies invites trouble.
Doorway pages are a known issue. Google's spam policies describe them as pages made to rank for place variations that all send people to the same spot, so avoid that pattern. Read the state guide before you pick donors for each page.
Which way to go
| Your situation | Better choice |
|---|---|
| One shop, three towns within 10 miles | One page, with a section for each town |
| Two offices in different counties | One page per office |
| Mobile service across a metro | A page per top five towns, plus one hub |
| Statewide, same service everywhere | A state page and a few city pages for the big markets |

Where the links go
Local linkbuilding is mostly about sending signals to the right page. A city page that gets a link from a paper in that city is a clean, tidy story.
If you buy a link, pick a donor in a matching niche and send it to the city page. The anchor can be your service and town in plain words, and it should vary from link to link.
Maps embedded on a page help visitors, though they are not a ranking trick. Check your pages in Search Console to see which ones get impressions.
Reading your own job data before you pick pages
The best city list comes from your own records, not from a keyword tool. Your past jobs show where customers live. Start there. Then compare the result with what people search for.
Count the jobs by town
Open your invoices or your booking software and export the last year. Sort the rows by town, then count them. A town with ten jobs is a real market. One job is a guess.
Say a roofer finished forty jobs in a year, and thirty were in three towns. Those three get pages first. The others can wait for their turn.
Spot the towns that repeat
Some towns look close on a map but behave differently. Think of two suburbs that share a school district, a zip code and a bus line. They may belong on one page, and one usually does the job.
Two towns next door can share one page when the work is the same. Say two neighbouring towns share a school district and one main road. One page can serve both if your work is identical in each. Ask a few real customers before you choose.
Use Search Console to see demand
Search Console shows which queries already bring impressions to your site. Filter for a town name. Look for pages where a town shows up next to your service.
If a query is getting impressions but no clicks, the page may need a clearer title or a better first screen. Fix that before you add a new town page. More pages will not fix it.
Writing a town section that is not a copy
A town section should read as if someone who works there wrote it. If you can swap the town name and change nothing else, the page is not doing its job. Detail wins. A neighbour would recognise it.
Name the streets and the local rules
List the streets you serve most, the neighbourhoods with older housing and any permit office that matters for your trade. They are hard to fake. Visitors decide faster for that reason.
A plumber north of a county line and one south of it face different permit steps. That difference belongs on the page. Write it plainly. Padding with keywords helps no one.
Show the work, not stock photos
Real job photos from that town do more than any stock image. Add a caption with the street or the area, and leave out the customer's address. Crew photos help too.
Use no more photos than you can keep current. An old photo of a finished job from three years ago can make a page look abandoned. Refresh them as the work changes.
Keep the service the same, change the detail
The core service description can stay consistent across pages. The town section changes the local details, the jobs and the contact route. That split keeps pages useful. Repeated paragraphs help nobody on the page.
Hybrid pages are common for good reason. A general service page holds the full explanation, and each town page carries only what is different there. Those two jobs should stay separate.
A city page outline (an example, not a template to copy)
- H1 with the service and the town, in plain words
- Two real job photos from that town, with a caption naming the street or area
- One quote from a customer who agreed to be named
- Opening hours, phone and address matching your Google Business Profile as of 2026
- A short note on local rules, such as permits issued by the city office
- Three links to your other pages and two to nearby town pages

What to watch afterwards
Wait six weeks. Then open Google Search Console and filter by the page URL. Look at impressions first, since clicks lag.
If one town page gains and another stalls, compare them. Details matter. The winner usually has more real detail, a better photo or a link from a source in that town. Tools such as Semrush and Ahrefs can show referring domains for a page, and the budget page explains how much to put behind each one.
Keep a note of each change with its date, so you can tell what worked.
Three strong pages beat thirty empty ones. Add a fourth only when you have a real job photo for it.
Keeping the details identical
Customers and search engines both check the basics. Your name, address and phone should match across the site and your listings. Mismatches confuse. Nobody means to cause them.
One name, one address, one phone
Write your business name, address and phone number once, then paste the same version everywhere. Check the footer. Check the contact page, the town pages and your Google Business Profile. Small differences, such as Suite and Ste, are enough to confuse a listing.
If you serve a town but have no office there, say so plainly. A line such as serving this area from our office in City A is honest. A street address you do not use is a different matter. Stay on the honest side of that line.
Structured data that describes a real place
Local business markup should describe a place you really operate or a business you really run. If you only visit a town, do not mark it as an office. Keep it honest. Search engines compare structured data with what people can see.
Ask a developer to check the markup after each change. Run the rich results test. It catches most mistakes. Then compare what the test shows with the visible page.
Reviews and mentions from the town
Reviews name the town more often than any page you write. Ask recent customers to mention the place they live in, if they are willing. Never write reviews yourself. Never trade a discount for one.
A mention from a local club or a town calendar is worth more than a generic directory row. If one exists, link to it from the town page. Visitors notice. Other people in town know you.
Questions about city pages and local links
Most city page questions come down to three worries: duplication, detail and upkeep. Here is how to think about each.
Will city pages hurt my rankings through cannibalisation?
They can, when several pages target the same query with nearly the same text. Make each page answer a different question, such as the local rules, the typical jobs or the travel area. Then the pages do not compete for the same search.
How many city pages should a small shop have?
Start with the three or four towns that bring the most work. Add another only when you have real jobs and photos for it. Three strong pages beat thirty thin ones, as the callout above says.
Do I need a page for every neighbourhood?
Usually not. Neighbourhood names are useful inside a town section, in a sentence about streets you serve. Make a separate page only when the work and the customers really differ from the rest of the town.
Should city pages carry local links?
They can, when a link comes from a source in that town. Good local linkbuilding points a donor or a local mention at the matching page, not at every page. The state guide explains how to pick the donor.
What if I serve a metro with no clear town lines?
Group the towns by how the work differs, not by the map. A hub page for the metro plus a few pages for the largest markets is a clear structure. Keep each page honest about where you actually go.