What a city page represents

A city page describes a business’s offering or service coverage in a named city. It should help someone understand whether the business can serve them there and how to take the next step. The city in the title need not be the place where customers can visit a branch.

A city name does not tell a visitor whether a business has premises there. Someone looking for a home visit needs different information from someone planning to bring an item to a counter. Make it clear which arrangement the page describes.

A page can explain both arrangements when that helps the customer. Keep the facts separate: where the team travels, where customers can visit, and how they arrange either service. Do not borrow an address or suggest a local office simply to make the page look more local.

A fictional Northbank service page

Imagine a fictional curtain-repair team with a workshop in Eastmere and home visits in Northbank. It is preparing a Northbank page. The team can explain the home-visit service, but still needs to settle the collection boundary and whether customers can bring curtains to the workshop.

Fictional Northbank service details
Customer questionWhat the team knowsWhat still needs an answer
Do you visit Northbank?The team offers home visits in the city.Does collection cover this street?
Can I bring curtains in?The workshop is in Eastmere.Are customer drop-offs available?
How do I ask about a repair?The team wants a photo of the curtains.Where should the customer send it?

The Northbank page can describe home visits without pretending there is a Northbank counter. Put the collection question beside the contact route so a customer can ask about their address. If drop-offs are later offered, link to the confirmed workshop visiting information rather than mixing that address into the service-area claim.

Give the page a job

Before creating another URL, check the existing service page. It may already answer the city-specific question clearly. A new city page should have a customer task of its own, such as explaining a local collection arrangement, rather than repeat a general service description with a different place name.

Google’s doorway-abuse policy describes pages created for specific, similar queries that lead people through intermediate pages less useful than the final destination. Its examples include region- or city-targeted pages that funnel users to one page. Read that context before treating a word-swap test as a policy verdict.

Google Search Central: doorway abuse

Keep the local answer current

When the service changes, update the local answer and its next step together. For the curtain team, a changed collection boundary matters to the customer deciding whether to enquire. Adding a landmark or rewriting a paragraph would not answer that practical question.

Use Local Landing Pages when deciding which local destination a visitor needs. Local SEO covers the broader task of keeping business information consistent with the actual operation.