Location pages that aren't doorway pages: how we build city pages for local businesses

For a business that serves many towns, location pages can explain service coverage and help customers decide whether to enquire. They also create a risk when the pages repeat the same promise without useful local information.

Google’s spam policies describe doorway pages: many similar pages created to rank for specific searches, each funnelling users to the same place. A set of city pages that only swaps the city name fits that description closely.

The test we apply

Before building a location page we ask: would this page still be useful if you removed the city name from it? If the remaining content is identical to every other city page, it is not worth publishing.

A real location page usually has:

• Local specifics: the utilities, regulations, climate, housing stock or common problems in that area.
• Local proof: projects, photos or reviews from that area, where they genuinely exist.
• Local pricing context: honest price ranges or factors that differ by area, with sources.
• A reason to exist: the business actually serves the area and wants work there.

What that looked like in practice

As reported in the Regional Solar Installer case study, we built 50 city pages for the solar installer in September 2026. Each page was researched individually:

• Pages average about 4,400 words, built from local data rather than a single template.
• The highest pairwise text similarity between any two city pages is 24.7%. We measured this before launch to make sure no two pages were near-copies.
• Six older /best-solar-* URLs were consolidated into the matching city pages with single-hop 301 redirects, removing pages that competed with each other.
• 33 blog posts were linked to the relevant city pages, so the pages sit inside the site’s structure rather than floating on their own.

The pages went live on 23 September 2026, too recently to report results. We will publish the outcome when there is enough data.

When not to build city pages

• You don’t actually serve the area.
• You have nothing specific to say about it.
• An existing page already answers the same local need. Review its intent and coverage before adding another URL.
• You would be publishing dozens of pages at once without the capacity to research them.

What evidence should you gather before writing?

Confirm that the business serves the area. A keyword opportunity is not evidence of service coverage.

Ask the operations team about delivery limits, appointment availability, travel charges, and work they can accept. Record who confirmed the coverage and when. If coverage changes seasonally or depends on project size, explain that condition in customer-facing language.

Separate the information you can verify from details you would like to include. A completed project, an approved customer quotation, and an official utility policy have different sources. Retain the source for each claim rather than collecting facts in an untraceable draft.

For a solar page, an official utility document may explain interconnection requirements. For a roofing page, the relevant authority may explain permit rules. Use those details only when they help a customer understand the service. A list of landmarks adds little if it has no bearing on the work.

Check current official sources when requirements can change. Identify the jurisdiction and date. Avoid presenting a rule from a nearby municipality as if it applied throughout the region.

You can publish a useful page without a local testimonial. Explain verified coverage, the service process, and relevant conditions. Do not invent a local project or borrow a testimonial from another location without making its origin clear.

How do you make the page useful without repeating the whole service page?

Give the city page a clear job. It should explain what a customer in that area needs to know before taking the next step.

Keep the main service page responsible for the general offer. Link to it when the customer needs the full process, scope, or exclusions. The city page can then focus on local constraints, genuine examples, and coverage details.

Shared navigation, contact information, and short process summaries are normal. The question is whether the central explanation adds value for that location. A different heading and a new city name do not establish that value.

Use keyword mapping to decide which URL should answer each need. A city page and a service page can support each other when their purposes are clear. If both target the same need with the same explanation, review possible keyword cannibalization.

A customer should be able to find the page through the site’s ordinary navigation or relevant content. A page accessible only through search traffic is harder to discover and maintain. Place it within the service-area structure and add useful internal links from related service and project pages.

Do not link every city from every article. Choose links that answer a real next question. A local installation guide might link to the relevant service area. An unrelated technical article may have no reason to do so.

Does a city page justify a separate Google Business Profile?

No. A website page does not establish eligibility for a new business location or profile.

Follow the Google Business Profile rules for the real business. A service-area business should represent its actual operating arrangement. It should not create a supposed office for each city it serves.

If customers do not visit the business address, follow Google’s address-display requirements. Website coverage pages can explain where the business travels without implying a staffed public office in each place.

A genuine additional location has its own eligibility considerations. Verify those facts with the business before adding an address, map, opening hours, or location-specific structured data. A rented mailbox is not proof of a customer-facing office.

Keep the page wording precise. “We serve customers in this area” and “Visit our office in this area” make different promises. Use the statement that operations can support.

How should you evaluate similar pages?

Compare the main content and the customer’s reason for using it. A similarity score can help find repetitive pairs, but it does not establish a safe ranking threshold.

Our reported 24.7% figure describes the pre-launch comparison for that project. It is not a Google standard, a guarantee, or a target other sites must copy. Different comparison methods can produce different values.

Read the closest pairs together. Check whether the local advice, evidence, and next steps differ in useful ways. Repeated boilerplate may be harmless; a repeated core explanation can indicate that one broader coverage page would serve customers better.

When considering consolidation, check existing traffic, enquiries, links, and the intent of both URLs first. Preserve useful information and choose a genuinely relevant destination. A redirect is a site change with consequences, not a shortcut for failing a similarity test.

If those records are unavailable, record that limitation before making the decision. Do not treat missing performance data as proof that a page has no value.

What should you measure after publication?

Measure discovery and business usefulness separately. Search visibility can show whether Google finds the pages. It does not show whether the enquiries are suitable for the business.

Start with indexing eligibility, sitemap inclusion, canonical consistency, and crawlable links. Then review Search Console by page and query over comparable periods. New pages may have little data; that is a reason to wait for evidence, not to declare success.

For enquiry quality, use the records the business actually maintains. Look for the service requested, genuine coverage, qualification, and outcome. Avoid counting repeated form events as separate customers.

Review the content when coverage, policy, pricing conditions, or local evidence changes. Give each page an owner and a reason for review. A large location library becomes less useful if its underlying promises are no longer accurate.

Word count alone cannot answer whether a page deserves to exist. The page needs truthful coverage, relevant information, a clear place in the site, and a practical next step for the customer.

Sources

• Spam Policies for Google Web Search · accessed October 8, 2026
• Guidelines for representing your business on Google - Google Business Profile Help · accessed October 8, 2026
• Tips to improve your local ranking on Google - Google Business Profile Help · accessed October 8, 2026