A Town Name Cannot Prove You Work There The Location Page Permission Test

A town name is not local evidence. Repeating it in a title, heading and service paragraph does not prove that a business operates there, understands the customer’s situation or can fulfil the next action.

The customer’s question is practical: can this business do this work here, under these conditions, and what evidence makes that promise credible? Most location-page templates answer a different question: how many times can we make Brighton, Hove or Worthing sound relevant without admitting that the page is identical?

My rule is that a location page needs permission to exist. Search demand can trigger the investigation, but only a distinct local decision, publishable evidence and a maintainable operating claim can authorise the URL. Sometimes the strongest local page is no local page at all.

Search demand discovers an opportunity; it does not create a fact

A keyword tool can show that people search for a service in a town. It cannot establish that the company has premises there, routinely serves the area, offers every service under the same conditions or possesses useful local experience. This distinction matters because a location query contains an implied service-and-place claim. A page optimised for service + town is not merely discussing a topic. It is inviting the reader to believe that this provider has a meaningful relationship with the requested place.

Google’s spam policies describe doorway abuse as pages created for similar search queries that funnel visitors towards the same useful destination, including multiple pages targeted at regions or cities (Google Search spam policies). A location page is not automatically a doorway. A page whose sole function is intercepting a place-name query is uncomfortably close to that pattern.

The commercial problem exists even before a search policy becomes relevant. Thin local pages create a public promise the delivery team has to inherit. If operations cannot explain what changes for the town, marketing has created geographic confidence from typography.

Name the operating model without euphemism

The operating model controls what the page may claim.

Do not blur these categories. Serving Lewes and our Lewes office describe different businesses. A selected service area in Google Business Profile is not evidence of premises, ranking coverage or completed work. Clear branding depends on preserving that difference. The brand should make the operation easier to understand, not make a distributed service sound physically present everywhere.

Use the reason-without-Google test

Ask one question before drafting:

The answer may be yes because the page contains:

• A documented local project or meaningful portfolio pattern
• Real branch-specific people, services or access
• A genuine delivery, travel or attendance difference
• Local eligibility, property or service constraints
• A defensible sector concentration
• Location-specific questions repeatedly encountered by the business
• A different next action or response route for the area

Those are reasons for a page. Competitors have one is a reason to inspect the opportunity. The keyword has volume is a reason to evaluate demand. Neither supplies local value. If the customer learns nothing additional, strengthen the service or coverage owner. One useful shared answer is better than ten underwritten promises.

I would rather decline a promising town keyword than publish a page whose only original contribution is the town name. The cost is a speculative landing page. The benefit is avoiding content debt, claim drift and another customer acquisition route designed to attract people the business has not properly qualified.

Write from the evidence outwards

Do not begin with a confident local promise and send the writer searching for proof afterwards. Begin with what the business can support: services genuinely available in the area; routine, conditional or unavailable coverage; a real location or operating base described accurately; approved local work at an appropriate privacy level; photographs with known origin and context; reviews attributed to the correct source and business; travel, response, pricing or access conditions; an accountable contact route; and observation and review dates for facts likely to change. Then decide what the page is allowed to say.

Google says local results are mainly based on relevance, distance and prominence, and that complete and accurate Business Profile information helps it understand what a business does and where it operates (Google Business Profile Help). Website content can clarify relevance and operating truth. It cannot rewrite physical distance or manufacture prominence.

For AI search optimisation, the same evidence discipline applies. A clear relationship between organisation, service and place may make the public business easier to interpret. It does not guarantee inclusion, recommendation or citation in an AI answer. AI readiness is improved by cleaner claims, not louder geography.

Local flavour is not local substance

The classic weak location page opens like a tourism leaflet. Brighton has a pier. Lewes has a castle. Crawley has excellent transport links. Somewhere beneath the local colour sits a form and the same service paragraph used on every other page.

Use place information only when it changes the service decision. Parking and access may matter to removals or a clinic visit. Conservation constraints may matter to relevant property work when supported by appropriate guidance and actual service implications. Opening hours matter to a branch. A landmark may help somebody find a hard-to-see entrance. None of those details should be invented. None proves local expertise merely through association.

Apply the noun-swap test: if a sentence can move to another town unchanged after replacing the place name, it is probably template filler. The test is intentionally harsh. Website design systems make duplication easy; editorial judgement must decide when reuse is useful and when it conceals an absent reason.

Make the first passage carry the local claim and its limit

The opening should answer five things quickly: what service is available; for whom or what problem; through which operating model; under which condition or exclusion; and what local evidence supports the relationship. A schematic example might read:

Example Roofing provides planned roof inspections in Hove through a mobile team based elsewhere in Sussex. Attendance depends on access and survey scope. This page documents two approved Hove projects and explains how the company checks an address before booking.

That is not a real company claim. Its value is structural. The passage does not invent a Hove branch, guarantee attendance or stretch two projects into universal local expertise. The limitation stays beside the promise because it may change the reader’s decision. Hiding it near the bottom may produce more form submissions, but it weakens conversion rate optimisation by asking unsuitable people to progress further before learning the truth.

Make proof carry only the weight it can bear

Local evidence becomes misleading when a small observation is promoted into a large operating claim. A project photograph can show work at a known place and time if its origin is documented. It cannot establish a permanent branch. A local review reports one customer’s experience. It does not prove every service is available throughout the area. A map pin shows a marked location; it does not prove customer access, staffing or opening hours. A trade membership may support a bounded status; it does not certify every marketing claim.

Use a simple evidence ledger:

The does not support column matters. Without it, genuine evidence becomes raw material for overclaiming.

Separate neighbouring page owners

Location-page cannibalisation is an ownership problem before it becomes a keyword problem. The core service page owns suitability, method and central scope. The coverage hub owns the general geographic footprint. The branch page owns the real premises, visit model and branch operation. The town page owns a distinct local decision. The project record owns evidence for completed work.

A location page can summarise connected information, but it should not reproduce every owner in full. Equally, narrow ownership cannot amputate the title’s promise. If the page has nothing useful to say beyond we also serve this town, merging it is better than starving it into a micro-page. This is a growth marketing decision, not housekeeping. Competing pages fragment attention, measurement and maintenance. More indexed inventory can create less organisational clarity.

Apply the location-page permission test

Before creating the URL, answer:

1. What exact local decision does this page own?
2. Which business entity and operating model does it describe?
3. Which local evidence can be published responsibly?
4. Which material conditions and exclusions apply?
5. How does it differ from the coverage hub, service page and neighbouring towns?
6. Which search and customer demand justifies investigation?
7. Who updates the page when coverage, people or proof change?
8. What action should a suitable customer take next?
9. Where does that action arrive operationally?

Return one of four decisions:

Do not add publish now and improve later. Placeholder pages become permanent remarkably quickly, especially after the agency or employee who promised the second phase has moved on.

Sometimes no location page is the growth decision

Imagine a business routinely accepts work across Sussex but has no branch, no documented projects and no service difference in one target town. Search demand exists. Competitors publish pages. A writer can certainly produce 1,500 words. None of that creates local evidence.

The stronger move may be to improve the coverage hub, make the address-check process clearer and collect approved project evidence as genuine work occurs. Google Ads or another controlled acquisition channel might help test service demand if the operation and budget justify it, but paid traffic still cannot turn an unproven local claim into a fact. This is not surrendering a keyword. It is sequencing business growth. First prove that the operation can serve the market and learn what local customers need. Then decide whether the evidence and decision deserve a permanent page.

I would change my recommendation when the business can show a stable delivery difference, recurring local question, meaningful project pattern, genuine branch or other evidence that changes what the page can do. Until then, absence is cleaner than fabricated presence.

Review the cohort without rewarding page volume

Measure location pages using separate search and commercial evidence:

• relevant impressions and clicks;
• suitable enquiries;
• accepted jobs or appointments where responsibly tracked;
• out-of-area and wrong-service dispositions;
• engagement with decision-grade local proof;
• changes in operating facts;
• maintenance failures;
• overlap with neighbouring pages.

A page can attract traffic and still mislead. A low-volume branch page can remain important to a real customer route. Sessions alone cannot settle the decision. Review location pages as a cohort. If every town page attracts similar queries and produces the same poor-fit enquiries, the system is revealing a structural problem. If one succeeds because it contains credible proof and a useful local condition, preserve that mechanism. Do not copy its prose and call the multiplication a strategy.

A location page earns publication by proving a service-and-place relationship the customer needs to understand. State the operating model. Carry the evidence. Keep the limit beside the promise. Give the page an owner. If the town name is doing all the work, the page has not yet earned the URL.