← All posts

Getting found

Do You Need a Page for Every City You Serve?

August 19, 2026 6 min read Matt McAlexander

Do You Need a Page for Every City You Serve?

You serve six towns. Somebody told you to build six pages, one per town, and swap the city name on each. It sounds like free traffic. Six pages, six cities, six chances to show up.

I want to talk you out of that, and I am going to use my own site as the example, because I got it wrong and had to go clean it up.

Do you need a separate page for every city you serve?

No. You need one for every city where you can say something true that you cannot say about the others.

That is the whole rule. If the page carries real information that only applies to that town, it earns its place. If it is your standard pitch with a city name find-and-replaced through it, it does not, and publishing it costs you more than skipping it.

What is the test for whether a city page is real?

Swap the city name and read it again. If every sentence is still true, you wrote a template.

Try it on a draft. Take your Murrieta page, change every “Murrieta” to “Menifee,” and read it top to bottom. If nothing breaks, if no claim becomes wrong, then you have not written about Murrieta. You have written a form letter that happens to mention Murrieta.

A real page for a spread-out city knows which neighborhoods sit on which end of it. A real Lake Elsinore page knows the difference between the downtown blocks and the hillside tracts. Those sentences break when you swap the city, which is exactly the point.

I am not above this test. I ran it on my own pages and failed it six times, which I will get to.

What does Google do with six near-identical pages?

It picks one and mostly ignores the rest, and sometimes it picks none of them.

Google publishes its spam policies openly, and two of them are relevant here. Doorway abuse covers “sites or pages created to rank for specific, similar search queries,” and it names “having multiple domain names or pages targeted at specific regions or cities that funnel users to one page.” Scaled content abuse covers “many pages generated for the primary purpose of manipulating search rankings and not helping users.”

Neither of those is aimed at you personally. Both describe what a stack of find-and-replace city pages looks like from the outside, which is the problem, because Google is on the outside.

The quieter damage matters more than the policy, though. When you publish six pages targeting six versions of the same query, they compete with each other. Google has to decide which one deserves the ranking, your link equity splits across six URLs instead of concentrating on one, and whichever page finally wins is weaker than the single strong page you would have built if you had only built one.

That is called cannibalization. It is self-inflicted, it is common, and almost nobody notices it is happening.

How many city pages should a local business actually have?

Start with the cities you would drive to today, and only the ones where you have something specific to say.

For most local service businesses around here that is a handful, not a dozen. A Temecula plumber who genuinely works Temecula, Murrieta, and Menifee should have three good pages. He should not have eleven pages covering every place within forty minutes, including the three he has never taken a job in.

Your Google Business Profile carries a lot of the geographic weight anyway. Its service area setting is what tells Google where you work. City pages exist to give a human a reason to believe you know their town, and to give Google something specific to match against. Neither of those jobs gets done by volume.

What goes on a city page that earns its place?

Detail a person who lives there would recognize.

  • The actual neighborhoods. Not “the greater area.” Old Town. The Colony. Sun City. Canyon Hills. Names people say out loud.
  • Conditions specific to that place. Around here that means hard water and what it does to fixtures and water heaters, slab-on-grade construction and the slab leaks that come with it, tile roofs where the underlayment gives out long before the tile does. If you are a plumber or a roofer in this valley, that kind of detail is the entire reason your page exists.
  • What you have actually done there. A job, a photo, a review from someone in that zip code. One real thing beats six paragraphs of positioning.
  • Links to the neighboring city pages. People searching from the edge of a town do not care about municipal boundaries.
  • A FAQ that changes by city. If the questions are identical across all of them, those are not city FAQs. That is your general FAQ, copied.

What about a page for every service in every city?

Only when the combination has its own answer.

There is a version of this that works. Roofing in Temecula can be legitimately different from roofing in Murrieta, because the rural western edge out toward De Luz sits in fire hazard territory and that changes the materials conversation in a way it does not for a tract house in the middle of town. That is a real distinction and it deserves its own page.

But you need the distinction before you build the page, not after. The mistake is generating the whole grid first and hoping the content shows up later. Build the combinations where you can actually answer the combined question and leave the rest of the grid empty. An empty cell costs you nothing. A thin page costs you the strength of the good pages sitting next to it.

What I found on my own site

Six duplicates, and I deleted all six.

I had a blog post called “Web Design in Menifee” and a separate landing page also called “Web Design in Menifee.” Same title, near identical meta description, the same FAQ questions, both trying to rank for the same thing. Six cities, doubled. The landing pages were better built and linked from every page on the site, so the blog copies were never going to win. All they could do was make the real pages fight for it.

So the blog copies got redirected into the landing pages, and the blog went back to doing what a blog is for. There is now one page per city, like the Temecula one, and no duplicate anywhere.

I am telling you this because I would rather you learn it from my cleanup than from your own traffic six months from now.

The short version

One page per city you actually work in, with real detail on it, beats a dozen thin pages every time. If you cannot say anything specific about a town, that is useful information. It means you should not have a page for that town yet. Go do a job there first.


Want a straight read on your own site?

Tell me your business and the towns you cover and I will tell you honestly whether you need city pages at all, and how many. No charge, and no pitch if the answer is that you are fine as you are.

If you do want a site: $399, one time, and you own it and every file forever. Live in seven days, or you don’t pay a cent.

See what yours could look like, or read what a website actually costs around here.

Matt McAlexander, owner of Temecula Web Co.

Matt McAlexander

Owner & designer, Temecula Web Co.

I design, write, and build every site myself, for local businesses in Temecula, Murrieta, and across Southwest Riverside County.

Call Matt Text Matt