Service-area pages versus city pages: what Google says

A Business Profile answers where the business is based, whether people can visit it and which areas it serves. A service-area business visits or delivers to customers but does not receive them at its address. A hybrid business receives customers at a staffed location and also travels or delivers. Google allows the hybrid model to display both the address and a service area, while a home-based service business that does not receive customers should remove the public address.

A city page answers what someone in that place can buy, why the provider is credible there and what happens after the enquiry. The page sits on the website, not inside the profile. It can explain travel constraints, local product availability, response hours, examples, common questions and the next action. None of those details should be added merely to make a location keyword appear more often; their value comes from reducing uncertainty for a real visitor.

Google says service-area businesses should keep one profile for the central office or location. A separate profile is allowed for another real location only when it has a separate service area and separate staff. Virtual offices do not qualify unless they are staffed during business hours. These rules matter because creating profiles for every target city is not a shortcut for local visibility; each profile must represent a genuine operating location.

Service areas are entered as cities, postal codes or other supported areas rather than a radius. Google permits up to twenty entries and advises specificity. The two-hour guidance describes operating accuracy; it supplies no ranking entitlement. If a customer in a listed area receives a different service, price or arrival commitment, that difference belongs in the website content and in the operational brief.

A useful city page has a local proposition that a broad service page cannot carry cleanly. The firm may have an office, named team, stock point, service timetable, regulatory condition, installation boundary or portfolio in that market. It may also need to answer a location-specific decision, such as whether technicians reach a district on weekends or whether a property team handles site visits from a particular sales office.

The page should be complete enough to stand alone. A visitor should not need to click into a generic national page to learn the service, evidence or next step. It should also fit a browseable site structure: locations under a clear hub, services under a service hub, and links between the two only when they help. This structure is different from publishing dozens of isolated URLs that all repeat the same promise and lead to the same form.

City pages become risky when only the city name changes. Other warning signs include identical testimonials copied across markets, claims of local staff that cannot be verified, stock photography presented as local evidence, several domains for near-identical areas and pages that contain no useful action except a link to the main service page. Search Central lists substantially similar regional pages that funnel users towards one page among its doorway-abuse examples.

A template can still provide design consistency, but the substance needs to change. The opening answer, operating facts, proof selection, questions, internal links and next action should match the place. If the company cannot supply those differences, one strong service page plus an accurate service-area profile is usually more honest than a catalogue of thin city pages.

Start with evidence. Confirm a current customer base, an address or team where claimed, the actual travel boundary, the service owner, the accepted enquiry types and proof that can be named. Then inspect the search task. A person seeking an emergency visit needs availability and response boundaries; a person comparing a long-consideration supplier needs project evidence, specifications and commercial contact details.

Next, read the proposed page without the city name. If it could be published unchanged for ten other places, it is not ready. Ask which paragraph, proof item and frequently asked question would be false or unhelpful elsewhere. Those differences form the page. The test does not require invented local trivia. It requires documented business relevance.

Measure the profile and the pages separately. Business Profile interactions can show calls, direction requests and website visits, while website analytics and Search Console can show landing-page discovery, engagement and enquiries. A page receiving impressions but no useful action may have weak intent alignment. A profile generating calls outside the service boundary may need clearer areas or better qualification.

Use qualified outcomes as the final check. Count enquiries the business could serve, not every form submission. Record the location requested, service required, timing and whether the team accepted the opportunity. That makes the next page decision evidence-led: expand where an actual operating difference and qualified demand coexist; consolidate where several URLs merely split the same weak proposition.

Assign each location page an owner and a review trigger. A move, staff change, service-boundary change, discontinued offer or office closure can make a previously accurate page misleading. The review should confirm the address presentation, phone route, hours, named proof, service limitations, internal links and Business Profile connection. A date alone is not enough; the reviewer needs to record what was checked.

When two pages drift towards the same offer, compare their qualified demand and business differences. One may deserve a stronger local evidence section, while the other may be consolidated into a regional page with an appropriate redirect. Keep the route simple for customers and search crawlers. A page should not remain merely because it once attracted impressions.

Treat location expansion as a controlled release. Publish one complete page, connect it from the location hub, inspect mobile use and confirm that enquiries reach the correct team. Only then use the evidence to decide whether another market has enough distinction. This pace supports quality without confusing a city-keyword inventory for a service network.

Review the search snippet and on-page promise together. If the title names a city, the visible page should confirm how the business serves it without requiring a visitor to infer coverage from a footer list. Put material restrictions near the action, including appointment requirements or limited service days. Clear boundaries may reduce unsuitable clicks while improving the usefulness of the enquiries that remain.

Finally, keep a single source of truth for locations. The profile, location hub, individual pages, contact forms and sales routing should draw from the same operating list. When a service area changes, update every surface in one release. Consistency here is a customer-service requirement before it becomes a local-search consideration.