Do I need a page for every city I serve?

No. Build a page for a city only when you can say something true and specific about working in that city, and let the rest of the service area live on one index page. A page whose only local content is the town name swapped into the same paragraph won't rank, and enough of them together will hold down the pages that would have.

How do I decide which cities get their own page?

One test, applied honestly. Would this page be wrong if you pasted the next town's name over it?

If every sentence survives the swap, the page is a template and search engines read it as one. If the swap breaks it, because the page talks about a specific corridor, a specific kind of building, a specific drive or a specific local rule, then the page has a reason to exist.

For a plumbing company the specifics are usually sitting in the job history already. Which parts of which towns are still on cast iron and which went in after the switch to PVC. Where the slab houses are. Which additions went up inside the same short window and are now all hitting the same failure at once. Which towns are on rural water and which are on city. None of that's marketing language, and all of it's the kind of thing a customer reads and thinks, right, these people work here.

If nobody at the business can produce a fact like that about a town, the page isn't ready. It's not permanently disqualified either. It's waiting on a job.

What happens if I just build them all anyway?

The pages don't sit there being neutral. Search engines assess quality across the whole domain, so a batch of near-identical city pages drags on everything else, including the pages that were already working.

The failure looks the same every time. A batch of city pages goes live. None of them rank. Traffic to the service pages slides over the following months, and nobody connects the two events, because they happened months apart. Pulling the thin pages down usually recovers it, which tells you what caused it.

The count was never the lever. A smaller set of pages that each say something will outrank a larger set that doesn't, every time.

What actually has to be on the page?

Enough that somebody who lives there recognizes it.

• A local paragraph only somebody who works there could have written. Named districts, corridors, roads. Real names only, because an invented subdivision on a published page can't be walked back.
• The services you genuinely run in that town, which is sometimes a shorter list than your full range.
• Proof from that town. A review, a job, a photo. One real item beats three sentences of assurance.
• Questions specific to the place, rather than the same five questions carried across every page.
• Links out to your service pages and to the neighboring towns, so the page belongs to the site instead of hanging off it.
• One clear next step. A single action, not four competing ones.

A page for Catoosa saying only that the company proudly serves Catoosa is competing against pages written by people who can name the street.

What order should I build them in?

Start where the work already comes from. The towns your existing customers live in are the towns you have facts about, photos from and reviews mentioning, so those pages are both the easiest to write and the quickest to rank.

Then move outward one ring at a time, and only as far as you actually want to drive. A page that ranks for a town well outside the distance you want to drive produces calls you'll turn down, and turning down a call costs the same time as taking one.

Metcalf Media builds city pages in that order for every client and adds new ones monthly as real jobs produce real material, which is why the roster is reviewed rather than fixed at launch. Local SEO compounds, and the second year of it looks nothing like the first fortnight.

What do I do with the towns that didn't make the cut?

Put them on the service area index page as a plain list, with the towns that do have pages linked from the same place. Nothing is hidden, a crawler sees the full coverage area, and no thin page has to be published to say it.

Those towns still get found. Somebody searching from a town with no page of its own lands on the nearest city page or on the service page, both of which say what you do and how to reach you. The map pack covers a good deal of the rest, and paid traffic can reach a town that organic never will.

Do I need a page for every service in every city as well?

Almost never at the start, and occasionally later. Multiplying every service by every town produces hundreds of pages, and no local business has hundreds of distinct true things to say.

Where the combination earns a page is a single high-value job in a single town with real search volume behind it. One page, written properly, because that one pairing is worth it on its own. The decision comes from search data and from what a booked job is worth, and the rest of the matrix stays unbuilt until something justifies it.

Metcalf Media would rather publish a short roster of city pages that each say something than a long one that says the same thing with the nouns changed.