You can serve a town without giving it a page
A locksmith based in Fareham may take jobs in several nearby towns. That does not mean the website needs a new page every time the van crosses a boundary.
A location page earns its place when it helps someone in that area make a decision. If the only change is swapping “Fareham” for “Warsash”, the visitor has gained very little.
Start with one accurate account of where you work. Add separate location pages when you have a useful reason for them. This guide gives you a way to choose, plus a plan for dealing with pages that already repeat each other.
Separate a branch from an area you serve
A branch page helps people use a real business location. It might need an address, opening hours, access details and information about the team or services available there. Those facts belong together because the customer may be planning a visit.
A service-area page has a different job. It explains where a team travels and how service works in that area. It should not imply there is a shop or office where none exists.
A page heading such as “Our Warsash office” would be wrong for a firm that only travels there from Fareham. “Locksmith services covering Warsash” describes coverage without inventing premises, provided the firm really offers that service there.
The website and Google Business Profile also have different settings. Google's service-area guidance explains how eligible businesses describe the areas they serve, including hiding an address when customers are not served there. Creating a website page does not create a branch or justify another profile.
Ask what the local reader needs to know
Before commissioning a town page, write its useful facts on a blank sheet. Leave the town name out of the first pass. Can you still see why this page needs to exist?
- Is there a different service or team available here?
- Do booking arrangements or coverage limits differ?
- Can you show relevant work from this area?
- Are there access details customers need before visiting a real branch?
- Is there a recurring local question with an answer you can support?
You do not need a different answer to every question. You do need enough substance to help a visitor beyond telling them the town exists. A paragraph about local history rarely helps someone choose a locksmith.
Local photos and customer stories can help when they explain the work. They are not decorations to scatter across otherwise identical pages. Use them with permission, and never invent an address, customer or local project to fill a gap.
Three choices for a service business website
Choice one: a clear coverage section
This suits a small business with one service offer across a compact area. Put the places you cover on the main service page, along with any boundary or travel rule a customer needs to know.
Do not make people scroll through dozens of town names to find the contact button. Group coverage in a readable way and give visitors a way to ask about a postcode near the boundary.
Choice two: one areas-served page
This can help when coverage needs more explanation than fits on a service page. It gives customers a central place to check where you work, which services travel and how to ask about an uncertain location.
Link it from the relevant service pages and keep it reachable through normal navigation. A coverage page should answer the question directly, not send every visitor through another page before showing basic information.
Choice three: selected location pages
Use these when individual areas have enough useful detail. Keep a shared layout if it makes the site easier to use, but write the information for the actual area.
A separate page should let someone understand the offer and contact you without needing to hunt for the real service elsewhere. It can still link to a main service page for deeper technical detail.
A worked example: one locksmith, three possible pages
The following business is fictional. Imagine a Fareham locksmith with one team, no customer-facing shop and the same domestic lock services across its normal patch.
Fareham: the main service page explains the work, the base area and how to request help. It states that there is no walk-in shop. That answers a question a customer could otherwise get wrong.
Warsash: the owner has no separate service, booking process or useful local evidence yet. A mention in the coverage section is enough for now. We would not commission a page just because a town keyword appears in a planning sheet.
A more distant area: the firm accepts planned work there but does not promise urgent attendance. That difference needs explaining. It could start as a clear note on the areas-served page; a separate page becomes an option if there is enough demand and useful detail to justify it.
Notice what did not happen: three pages were not created by default. The owner's service rules shaped the website. Search research can help choose priorities, but it cannot supply local facts the business does not have.
When repeated pages become a problem
Google describes doorway abuse as pages made to target similar searches while sending people towards a more useful destination. Its examples include substantially similar regional pages that funnel visitors elsewhere.
That does not make every shared layout a doorway page. The concern is the purpose and value of the pages. A real branch with its own visiting information is different from fifty copies of a sales pitch with changed place names.
Read two of your pages side by side. Hide the location names. If almost everything left is interchangeable, ask whether a combined page would serve the customer better. Changing adjectives will not fix a missing reason for the page.
Our local SEO work can help make that judgement alongside search evidence. The aim is useful coverage, not the largest possible count of indexed URLs.
Already have lots of town pages? Review before removing them
Do not delete a set of URLs just because they look similar. Some may have useful links, relevant visits or information customers rely on. Make a page list and review each URL before choosing an action.
- Keep: the page serves a distinct need and contains accurate, useful material.
- Improve: it has a clear job, but the evidence or service detail is weak.
- Combine: two pages answer the same need and neither needs a separate home.
- Remove: the business no longer offers the service or coverage, and the page has no useful replacement role.
Check search queries and visits by page, rather than relying on a site-wide total. Our guide to measuring local SEO results covers why those numbers need context. A quiet page may be new, hard to find or aimed at a very small audience; traffic alone does not settle the decision.
When combining pages, move useful information to the chosen destination. Arrange an appropriate permanent redirect where a relevant replacement exists, update internal links and check the sitemap. Google's URL-change guidance explains this process. Avoid sending every retired town URL to the homepage regardless of what it used to answer.
If a page is genuinely gone with no suitable replacement, handle that honestly rather than forcing an unrelated redirect. A developer or technical SEO review can check the response codes and links before the change goes live.
Make the next location decision on one sheet
Write the proposed area, the service offered there, the facts that differ and the evidence you have. Add the existing page that could cover the need. Then choose between improving that page and creating a new one.
If the sheet contains little more than a town name, hold the new page. Collect real questions and job information first. A smaller website with clear coverage can be easier for a customer to use and easier for you to keep accurate.
For help assigning topics to pages before writing, use our local keyword planning guide. Keep the final decision tied to the service you can deliver and the answer the visitor needs.