Service-area and city pages that help instead of hurt

A page for every town you serve looks like a shortcut to ranking everywhere. More often it backfires: Google sees a stack of near-identical pages, shows one or two, and ignores the rest, and the pages rarely beat businesses actually located in those towns. These practices come from consolidating city pages on real sites. They cover why thin pages fail, how to decide how many pages to have, how to build hub pages that earn their place, and how to retire the rest without losing what they had.

Understand why swap-the-city-name pages fail

The pattern is familiar: one template copied a dozen times, with the town name changed in the title, the heading, and a sentence or two. Three things work against it.

Decide how many pages from data, not from a list of towns

The right number of service-area pages is the number of towns where people search, where you have real work to show, and where a page has a realistic chance to rank. Check three things for each town before you build a page or keep one.

1. Demand searched from inside the town

   Phrases with a town name often show no measurable volume, because people type the bare service and let Google localize the results. The useful number is the volume of the main service keyword searched from that town. Most keyword tools let you set the location.

2. Impressions in Search Console

   For a page that already exists, check whether it earns impressions at all, and for which searches. A page that has been indexed for a long time with no impressions is telling you something.

3. The live results from that town

   Run the searches located in the town. If your homepage or a nearby hub already ranks there, a separate page adds little.

Retire or skip a town's page only when all three are flat. Then apply one more test: do you have enough real, local material to make the page genuinely different from its siblings? If not, the town belongs in a hub's coverage list, not on a page of its own.

Build fewer hub pages with real local proof

A hub page covers a town and the smaller places around it, and it earns its place with material no other page on the site could carry. When I rewrote a set of city pages, I aimed for roughly 40 percent of each page to be specific to that town, not one swapped sentence. That share comes from:

• Jobs done there: the problem, what you did, and the neighborhood or a nearby landmark, with the customer's permission.
• Photos from those jobs, not the same gallery repeated on every page.
• Service details that differ by area, such as the housing stock, the permit office, access and parking, or the local events and seasons that drive demand.
• Coverage details: the smaller towns the hub covers and honest response times.
• Questions people in that town actually ask, answered for that town.
• Reviews from customers there, quoted word for word with the source, only if they exist.
• A phone number and a short form, so a visitor can act without hunting.

Consolidate thin pages into hubs with 301 redirects

Deleting a thin page turns its address into an error and throws away whatever it had earned: links, bookmarks, and any standing in search. A permanent redirect, a 301, sends visitors and Google to the page that now covers that town, and Google treats a permanent redirect as a sign that the target should be the page it shows. Google's redirect documentation covers the details.

1. Map every retired URL to a hub

   Send each one to the hub that covers that town, not to the homepage. Write the map down with the old URL, the new URL, and the date.

2. Move the town into the hub first

   Add the retired town's name, its real jobs, and its coverage details to the hub before the redirect goes live, so people land on a page that mentions the place they searched for.

3. Add the redirects

   Set a permanent 301 at the server or in the content management system. The syntax depends on the platform; the idea is the same everywhere.

   Redirect 301 /service-areas/old-town/ /service-areas/hub-city/

   location = /service-areas/old-town/ {
       return 301 /service-areas/hub-city/;
   }

   Use a redirect plugin, or the redirect feature in your SEO plugin if it has one. Choose the 301 type, then enter the old path and the hub URL.

4. Remove internal links to the old URLs

   Update the navigation, the footer, any nearby-areas lists, and links inside other pages so they point straight at the hub. Redirects are there to catch outside links and old bookmarks, not your own menus.

5. Update the sitemap

   Remove the retired URLs so the sitemap lists only live pages, and update the last-modified date on the hubs you changed.

6. Test every old URL

   Each retired address should answer with a 301 that lands on the right hub in a single hop, with no chain of redirects and no error at the end.

   curl -s -o /dev/null -w "%{http_code} %{redirect_url}\n" https://www.example.com/service-areas/old-town/

7. Request indexing for the hubs

   Once the rewritten hubs are live, inspect each one in Search Console and request indexing. Google limits how many individual URLs you can submit, so start with the hubs that matter most and let the updated sitemap cover the rest. Requesting indexing before a page is rewritten wastes a request. I also hold off on Validate fix in the indexing report until the requested pages have actually been recrawled.

Watch for the big-city mismatch

I have found this pattern more than once: the site is written for the big city nearby, and the business only ranks where it is actually located.

A detailing shop based in a smaller city had every page's title, description, and main heading written for the large city about 20 miles away. It ranked for none of those big-city searches, organic or map pack. Meanwhile it held the first map spot for a search in its own city, and that city's name did not appear in a single title tag on the site.

The map pack follows where the business is located, so the big city's map results go to businesses based there. Organic results do not depend on location in the same way, which makes them the realistic target for a big-city page. The fix:

• Own the home city first. Its name belongs in the homepage title and heading, in the structured data, and on a strong page of its own if the homepage is not enough.
• Keep a page for the big city only if you really work there and can prove it with jobs, photos, and reviews from there, and aim it at the organic results.
• Check where the demand actually is. When most searches are near-me searches, the work is on the Business Profile, not on more pages.

Match the number of pages to the situation

For scale: the equipment rental company above ended with seven hub pages after retiring the pages for three small towns, each redirected to the hub that covers it. Its homepage already ranked on the first page for searches made from those towns, and the retired pages had earned no impressions. The number came out of the data, not a target. To find which searches are worth a page in the first place, use the method in why competitors outrank you.