Anyone serving several cities wants to show clearly where the service is available. That is legitimate. City pages only become problematic when they look almost identical and are only meant to send visitors on to another, more useful page. Google describes such constructions as doorway abuse.
A city page needs a concrete job
Do not start with the place name but with the reason for the search. Perhaps travel, service area, appointment process, official requirements, scope of service or contact person really do differ. Then a page can explain this particularity. If it only replaces “service in town A” with “service in town B”, it lacks a job of its own.
Test question: Would a reader have fewer follow-up questions after the location page than after the general service page? If not, a regional main page is usually the better choice.
An example: a repair business serves two towns with different appointment windows. In one town there are fixed route days and a tighter radius, in the other only appointments by arrangement. These differences matter to customers and can support separate pages. If, on the other hand, the same rules apply everywhere, listing the area on a strong service page is enough.
Before creating each location page, write down in one sentence what additional decision-making benefit it provides. If you cannot, the place name alone is not a sufficient concept.
Three models: helpful, borderline, superfluous
Helpful
A page for one place of service describes real appointment windows, a different service, clear boundaries of the area and the right next step. It does not lead away from the answer; it is the answer.
Borderline
A page names a few local places but otherwise contains almost the same text as ten other pages. Here the team should check whether a shared area page with a clear list of the places served would be better.
Superfluous
Many almost identical pages catch similar search queries and then send all visitors to the same contact or service page. Google names exactly these intermediate pages as an example of doorway abuse.
The limit is not a certain number of words. A short page with precise service conditions can be more useful than a long text with interchangeable paragraphs. The problem is the pattern of many pages that serve the same search intent, are worded similarly and only lead visitors to another destination.
So compare new drafts side by side. Mark every sentence that would fit all pages unchanged after swapping the place name. If almost only such sentences remain, bundle the information. This also saves maintenance effort when prices, times or areas change.
Which local information can carry a page
Local value comes from verifiable information: an area that is actually served, comprehensible travel or service times, a special on-site process, relevant services and a way to get in touch. Do not invent references, offices or local results just to make the page look denser. Fewer statements with real meaning are better than a long block of place names.
- What exactly is possible in this area?
- Which limits or requirements apply?
- How do the enquiry and the appointment work?
- Where can you find the overall service if the location page does not fit?
Good local information can be confirmed by the business: is the service really offered there? Which travel costs or lead times apply? Is there work that is not possible in a particular area? Such information helps customers before they get in touch. An invented local “branch” or a made-up customer example, on the other hand, would be misleading.
Internal navigation should also show the difference. Link a location page where readers check the service area, and provide a way back to the overall service. Pages that can only be reached through a sitemap serve the orientation purpose poorly for people.
When a regional main page is enough
If the process is the same everywhere, a good main page is often easier to understand than twenty variants. It can name the entire service area, explain the service and, if needed, refer to the few places that are genuinely different. This keeps navigation clear and prevents similar pages from competing for the same search intent.
SEO for several cities therefore starts with information architecture: first collect real differences, then decide whether they become separate pages. The number of URLs is not a mark of quality.
A regional page can describe the area on an understandable map or list and lead to a few detail pages for frequent special cases. Avoid an endless list of small places without further explanation. Readers want to know whether their specific job can be accepted.
Review existing location pages regularly against real enquiries. If nobody can name a difference in content between two pages, merging them can make sense. When merging, redirect old URLs appropriately and update internal links; do not remove them from the navigation haphazardly.
