Guide  /  City pages

Fieldline

One city page, or a page for the service in that city?

Build pages for the jobs you run. Add a city page only where you already work and can say something a swapped city name would make false.

Three pages

The job, the city, and the pair

A service page is the job. Drain cleaning. Furnace repair. Panel replacement. It explains the work wherever you do it.

A city page is the place. It says you travel to Everett, names the jobs you will do there, and shows that you have done them. It links to the service pages. It does not pretend you have a shop there if the shop is somewhere else.

A service-in-that-city page is the pair. Furnace repair in Everett. The person who searched that wants the job, in that city. All three can exist. They should not be published on the same day, and the pair should be rare.

A city page

Only where the trucks already go

Publish it when four things are true. You dispatch there and can take more work. You have jobs, photos you can use, or reviews that name the city. The page can say something a copied city name would ruin: a scheduling limit, a neighborhood you cover, a job you did in enough detail that pasting another city over it would be a lie. And you will not invent a local office.

Two jobs in three years is a mention, not a page. Neighborhoods usually live as a sentence on the city page. Ballard, Queen Anne, and Fremont do not each need a URL because a build listed them.

A heating company based in Lynnwood makes it concrete. Everett, where the trucks already spend the winter and the photos exist, can earn a page. A neighborhood you would accept if someone called, with no record, stays on a short coverage note.

The pair

One service in one city, not the full grid

Add the pair when people search that job in that city, you want it on the schedule, and the city page cannot carry the detail. Then stop. The week you clone furnace repair, drain cleaning, and panel work across Everett, Bellevue, and Renton, you are back to a grid. Each clone has to stand on its own proof.

Google’s spam policies go after city pages that all funnel people to the same place, and after large sets of pages that are substantially the same. A city name swapped through one paragraph is that pattern.

The map stays tied to distance from your base. A page can help the ordinary results farther out. It does not create a new map pin. You can list up to 20 service areas on the Business Profile. That setting is not an order to publish 20 pages, or 20 pages per service. Why your business does not show up on Google is the distance check.

Order

Jobs first, then the few cities you can prove

Write the service pages for the jobs that pay. The homepage gets a short, true coverage note. Add a city page only where the proof is already true. One to a few is a normal start. Zero is a normal answer. Add a service-in-city page only for a pair you can defend.

If you cannot point to work in a city, you do not have a page problem yet. You have a coverage list. Sort it by where the trucks go.

Field Search is the plan for the profile and those pages, without a city farm. Schedule a call when you want the list sorted against the jobs you run.

Next step

Start turning local search into booked jobs

Short call. Clear next step.

Schedule a call
Scroll to Top