A keyword tool can place Brighton Station, Hove and Kemptown in adjacent rows. A business should not assume those rows deserve adjacent landing pages. The names can perform different jobs, and none automatically creates a distinct service.
TL;DR
- A neighbourhood page earns a URL only when the place changes the buyer's decision: premises, access, delivery, eligibility or proof.
- Brighton Station is usually an access question, Hove can be four different things, and Kemptown's boundary is not a business fact.
- Search demand is a clue, not publication permission.
- Remove the place names and compare what remains. If it matches an existing page, merge.
Neighbourhood SEO becomes useful when the place changes the buyer’s decision. It becomes doorway-page production when only the place name changes. My test is not “can we optimise for this area?” It is “what does a buyer need to know here that the broader Brighton page cannot answer accurately?” If the business cannot supply a different answer, operating condition, proof set or action, the neighbourhood probably belongs in a section, profile fact or ordinary page copy, not a new URL.
Three place names, three different jobs
Before drafting anything, name the decision each place actually represents for this business. The same three names carry very different jobs:
Access
Brighton Station
An access decision. Matters when a customer, patient, guest or attendee needs to reach real premises: route, entrance, appointment model, parking alternatives, what happens on arrival. For a mobile trade or remote consultancy it may change nothing.
Premises or coverage
Hove
A location, a territory, a market or just how a customer describes home. The page job depends on which of those the business can prove. Do not build Brighton and Hove pages from the same offer, process, examples and call to action.
Boundary
Kemptown
A boundary with humility. A resident's Kemptown, a property listing's Kemptown, a council ward and an internal delivery zone overlap without being identical. State the scope that controls the business claim.
Those relationships are not interchangeable. Serving Kemptown does not prove premises in Kemptown. Being near Brighton Station does not prove relevance across Brighton. A Hove address does not mean every service is available throughout the whole city.
Decide what the place means before choosing a page
A location label can describe at least five relationships between a business and a place:
Before drafting, complete one factual sentence:
[Business]provides[service]to[eligible customer]in[defined area]through[premises, mobile, remote or delivery model], subject to[material condition].
If the team cannot complete and evidence that sentence, the page is premature. Website design cannot rescue an unresolved operating claim.
When a separate page earns its place
Use station language only if you can finish the sentence “Brighton Station matters to this customer because…” without theatre. “Because people search for it” is demand evidence, not the answer. Official status does not help either: Brighton & Hove City Council says the Hove Station Neighbourhood Plan was formally made on 28 March 2024 and forms part of the city’s planning framework (Hove Station Neighbourhood Plan), but that does not mean every company near Hove Station needs a Hove Station landing page.
A separate page earns its place when…
- The company has genuine customer-facing premises there
- Availability, delivery or attendance differs
- A meaningful area-specific service or product range exists
- The buyer needs local access, collection, parking or appointment information
- Approved projects or customer evidence support a different local decision
- A separate accountable branch or team operates there
It is a merge candidate when the only differences are…
- The opening location
- A list of landmarks
- Headings and title tags
- Stock photography
- A map embed
- A paragraph of local history
- An unsupported fast-response claim
Do not borrow specificity from the existence of a place name. The evidence must belong to the business and service being described. Google’s spam policies describe doorway abuse as pages created to rank for similar queries that funnel users towards substantially similar destinations (Google Search spam policies). Editorial judgement should intervene before a policy debate is required. If a page has no independent job, it should not exist.
Run the different-decision test
A neighbourhood page needs a decision that survives after the place name is removed. Ask which exact reader the page is for, what situation makes the neighbourhood relevant, which question the wider service page cannot answer cleanly, what operating fact changes in this area, which first-party or authoritative evidence supports that difference, what action the reader should take, and whether the content would remain useful with no organic traffic at all. Then choose one of four treatments:
| Finding | Content decision |
|---|---|
| Place changes access, delivery, scope, eligibility or proof materially | Consider a distinct page with a complete decision job |
| Place adds useful detail without changing the main service decision | Add a bounded section to the existing owner |
| Place is only a coverage fact | State it accurately in service-area or contact information |
| Place changes nothing except query wording | Do not create the page |
No arbitrary score can replace this judgement. Three weak local details do not become a strong page because a template says three is enough.
What a location page has to prove, in order
- DecisionWhat the buyer chooses on this page that the wider page cannot answer
- EvidenceProof that belongs to this business, kept in its own lane
- OperationPremises, access, coverage or eligibility that actually differs
- PlaceThe name itself, last, and only where it changes the decision
Search demand is a clue, not permission
Query research can show that people combine a neighbourhood with a service. Inspect the result types, language and apparent intent. Check first-party Search Console data where the site has enough visibility. A high-volume phrase can still be wrong for the offer. A low-volume phrase can matter when it reflects a high-consequence access or delivery question. An empty tool can miss sparse local demand. None creates local proof.
Google Business Profile cannot turn coverage into premises either. Google says local results are mainly based on relevance, distance and prominence (Google Business Profile local-ranking guidance), and its representation rules require a profile to reflect the real-world organisation and distinguish customer-facing locations from service-area operations (representation guidelines). Keep three facts separate: where the business is physically based, where customers can visit, and where the business travels or delivers. A service-area selection is not a collection of virtual branches.
Local evidence must change confidence, not just vocabulary. Mentioning the seafront, Regency architecture or a popular coffee shop does not prove that a company understands the buyer’s problem. Local detail earns its place when it affects access, delivery, method, risk or choice.
Keep proof within its lane: a customer review reports that customer’s experience; a project record supports the work actually documented; a photograph proves only what its provenance and caption establish; a professional credential supports the named holder and scope; a route description supports access, not service quality; an address supports location, not market leadership.
One strong area owner can beat three micro-pages
Suppose a mobile professional serves central Brighton, Hove and Kemptown under the same availability, price basis, process and response conditions. Three pages would divide one answer into place-flavoured copies. One service-area owner can define coverage, explain the operating model and carry the common proof without pretending each location is a separate offer.
Same offer everywhere
- One service-area page owns coverage, operating model and proof
- Neighbourhood names appear as accurate coverage facts
- Fewer pages, one authoritative answer that ages well
Materially different relationships
- Premises in Hove get a premises page with access facts
- A Brighton Station appointment venue gets its own operational page
- Kemptown as mobile coverage stays a coverage fact, not a branch
This is the real architecture decision: not how many keywords exist, but how many materially different business relationships the website must explain. For customer acquisition, fewer pages can be the more ambitious strategy.
Planning local pages for Brighton and Hove? We will run the different-decision test on your area pages and tell you which deserve a URL, which need a section, and which should merge.
Measure a better local decision, not more indexed pages
For a distinct page, observe its intended query group, landing-page visits, suitable calls or forms, service-area fit, directions or bookings where relevant, and the questions people still ask before acting. Keep the observations separate. A direction request is not a completed visit. A form is not a qualified enquiry. A ranking is not a customer.
The most valuable result may be fewer wrong assumptions: fewer visitors arriving at a non-public address, fewer enquiries outside the service area and fewer calls asking whether the company actually covers the neighbourhood. That is useful conversion rate optimisation. It improves fit instead of celebrating a larger pool of confused traffic.
Start with the business relationship, not the location keyword. Make the place claim small enough to be true.
Good to know
FAQs
Only when the place materially changes the buyer’s decision: premises, access, delivery, eligibility or proof. If the offer, process and evidence are identical, one clearly defined area page will usually serve better than three near-copies.
It becomes one when only the place name changes. Remove the location words and compare what is left. If the proposition, evidence and call to action match an existing page, it is a merge candidate rather than a new URL.
They do different jobs. A service area states where you travel or deliver; it does not create premises or a branch. Keep where you are based, where customers can visit and where you travel as three separate, truthful facts on both the profile and the site.
Not by pages indexed. Track the intended query group, landing-page visits, suitable calls or forms, direction requests where relevant and the questions people still ask. Fewer wrong-fit enquiries can be the most valuable result.
Next step
Planning local pages for Brighton & Hove?
We run the different-decision test on your area pages and tell you which deserve a URL, which need a section, and which should merge.