If the only difference between your Manchester page and your Leeds page is the word "Manchester," you haven't built two location pages. You've built a doorway page set, which is a policy violation rather than a grey area — and it's the outcome of nearly every templated approach to this.
The line, defined properly
Most guides say "add unique content" and move on, which is useless because it doesn't say what unique means. Here's a workable definition.
A legitimate location page contains things only that location could truthfully say. Not rewordings of the same claims — facts that are specific to that place and would be false on any of your other pages.
The practical test: can you name three?
| Genuine | Not genuine |
|---|---|
| Named staff at that location | "Our expert team in [City]" |
| Photographs taken there | The same stock image on every page |
| Work completed for named local customers | "Trusted by businesses across [City]" |
| Access, parking, transport specifics | A generic map embed |
| Reviews mentioning that location | Company-wide review average |
| Conditions particular to that area | The same service list, reworded |
If you can't produce three items from the left column, the honest conclusion is that you shouldn't publish that page — not that you should generate filler until it looks long enough.
The test that settles it Would this sentence be false on any of your other location pages? If no sentence on the page passes that test, the page isn't about a location. It's about a template.
The functional requirement
A recent change that turns a location page from a description into an asset, and it's enforceable.
Reporting on Google's link policy indicates an expectation that a page linked from a business profile is functional — a visitor should be able to contact the business, book, or complete a meaningful action without needing to log in or pass a CAPTCHA. Links to social profiles, shortened URLs, and destinations that redirect may be removed automatically.
Two consequences. First, linking every location on your profile to one generic homepage is now a weaker setup than it used to be — each location needs its own destination. Second, a page that describes the location without letting anyone do anything is failing a requirement, not merely underperforming.
That connects directly to the profile side of the work, since the link destination is a profile field and the profile is where the enforcement pressure sits — the territory covered in optimising your Business Profile.
Two audiences, unequal weights
The page serves retrieval systems and a person who arrived with high intent, and those need different things — but not in the proportion most people assume.
Analysis of local ranking factors has placed on-page signals at a relatively modest share of local pack weight while carrying a noticeably larger share of AI visibility decisions. Which produces a counterintuitive conclusion: your location page matters more for how AI systems describe you than for whether you appear in the three-pack.
The pack is assembled largely from profile data, reviews and proximity — the mechanics behind why local rankings swing. The page is where a system assembling an answer finds something specific to quote.
Practically, that means clear stated facts rather than atmospheric copy, accurate structured data describing the business and location, and consistency with what your profile and directory listings say. Conflicting details across sources reduce confidence, which is the mechanism in generative engine optimisation applied locally.
GeoTargetly
Redirects website visitors to location-specific pages based on their geographic location
Best for: Geo Redirect & Targeting
The four things above the fold
Local intent converts fast and impatiently. Someone searching "plumber near me" at 8pm is not reading your brand story.
- What you are and what you do — the specific service, not a slogan.
- Where you are, so they can judge proximity themselves. Address for a premises; served areas named explicitly for a service business.
- Whether you're open now — current status, not a table of hours they have to interpret against the clock.
- A tappable phone number. Most local searches are on mobile, and a number that isn't a tap target is a friction point on the highest-intent action available.
Anything that requires scrolling before those four are answered is costing you conversions from people who arrived ready to act. The wider hierarchy principles in landing page design all apply — this is the local-intent version of the same discipline, compressed because the visitor's patience is shorter.
The service-area problem
The hardest version of this, and the one that produces most doorway pages.
A business without a physical presence in an area has no address to anchor the page and little genuinely local to say beyond a willingness to travel. Proximity also works against you structurally, since the pack weights distance from the searcher.
Which creates the temptation: generate a page for every town you'd like to serve. That reliably produces thin, templated pages — the doorway pattern described above, at scale.
What works better is fewer pages built on genuine evidence:
- Areas where you've actually completed work, described specifically — the job, the constraint, the outcome.
- Named customers in that area who'll let you say so.
- Conditions particular to the area — property types, regulations, access issues, common problems you encounter there.
- Honest coverage information — travel time, whether there's a call-out difference, response times.
The uncomfortable implication is that your page count should follow your actual footprint rather than your ambitions. Five substantial pages covering places you genuinely work will outperform forty thin ones, and they won't put your site at risk.
What to include, beyond the essentials
Assuming the four above-the-fold items are handled, these earn their place.
Location-specific reviews. Reviews mentioning that branch or that area are both persuasive and genuinely unique content. This is often the easiest of the "three things" to source.
The team, named and photographed. Local buying decisions involve trust in people more than in brands, and a real photograph of the people who'll turn up outperforms a stock image comprehensively.
Practical arrival detail. Parking, the entrance to use, which floor, accessibility, what to bring. Genuinely useful, impossible to template, and it answers questions people would otherwise phone to ask.
Local work or case studies. The strongest form of location-specific content and the hardest to produce, which is exactly why it differentiates.
Accurate structured data. Business type, address, hours, phone, and area served — matching what's on your profile exactly.
What to leave out: a paragraph about the history of the town, which is a recognisable filler pattern and helps nobody. If you're writing about the city's founding date, you've run out of things to say about your business there.
Where these pages sit
Structural decisions that are cheap now and expensive later.
Give them a consistent, predictable URL pattern and put them one click from the main navigation. A locations index linking to every page, and each page linking back, means they're findable by people and crawlable in a single hop — the practical overlap with information architecture.
Interlink neighbouring locations where it genuinely helps someone — "also serving X, 20 minutes away" is useful navigation, not link stuffing.
Watch for self-competition. Location pages covering overlapping areas can compete with each other for the same queries, which is the cannibalisation pattern described in topic cluster planning — check Search Console to see whether more than one of your location URLs appears for the same search.
For anything beyond a handful of locations, the scaling questions — consistency, governance, reporting, keeping profiles and pages aligned — are a programme rather than a page problem, and they're covered separately in scaling local rankings across branches.
The common failures
- One generic contact page for every location. An address in a footer is not a location signal, and it no longer satisfies the functional expectation either.
- Hours tables instead of open-now status. Making the visitor do arithmetic at the moment of highest intent.
- An untappable phone number, or one rendered as an image.
- Details that contradict the business profile. Inconsistency reduces confidence in everything.
- Pages for places you don't serve. They attract enquiries you have to decline, which costs time and produces poor reviews.
- Publishing and forgetting. Staff change, hours change, phone numbers change. A stale location page is a live customer-experience problem, not just an SEO one.
That last one deserves a review cadence. Location pages decay in a way most pages don't, because the facts on them are operational rather than editorial — and nobody notices until a customer arrives somewhere that closed.
A build sequence
- List the locations you can genuinely write three specific things about. That's your page list. Not the list of places you'd like to rank in.
- Gather the raw material per location — photos, named staff, local reviews, a piece of local work, access details. This is the actual work and it can't be shortcut.
- Build the above-the-fold block to answer the four questions immediately.
- Add the location-specific substance, then check the "would this be false elsewhere?" test line by line.
- Add structured data matching your profile exactly.
- Confirm it's functional — someone can contact or book without a login or a CAPTCHA.
- Link it from the profile and from a locations index, and run the 8pm test on a real phone.
- Set a review date. Twice yearly minimum, and immediately whenever anything operational changes.
Step one is where the discipline lives. Everything else is execution, and the sequence only produces good pages if the list is honest.
If the constraint is that you have forty locations and the raw material for six, that's a content-gathering problem rather than a build problem — and it's worth resolving before publishing anything, since a small set of strong pages beats a large set that puts the site at risk. The surrounding local fundamentals are stepped through in a practical local SEO checklist.
The short version
A location page is legitimate when it contains at least three things only that location could truthfully say — named staff, its own photographs, local work, real access detail. If you can't produce three, don't publish the page rather than padding it, because a set of templated pages differing only by place name is a doorway pattern and a policy violation. Make the page functional, since the link destination is now expected to let someone act without a login or CAPTCHA. Answer four things above the fold: what you do, where you are, whether you're open now, and a tappable number. And note the page matters more for how AI systems describe you than for pack position, which makes stated specifics and consistent structured data the priority over word count.
Location pages that describe your business but don't convert anyone?
We build local pages with the substance to rank and the clarity to turn searches into calls.
Explore Web Development →Frequently asked questions
When does a local landing page become a doorway page?
When the only thing distinguishing it from its siblings is the place name. A set of pages generated from one template with a city variable swapped in has no substance specific to any of those places, which is the definition of a doorway page and a policy violation rather than a grey area. The workable test is whether the page contains at least three things that only that location could truthfully say — named staff, its own photographs, specific service area detail, local work, or genuine access information.
Do location pages need to be functional to satisfy Google?
Increasingly, yes. Reporting on Google's link policy indicates an expectation that a page linked from a business profile lets a visitor complete a meaningful action — contacting the business, booking, or ordering — without needing to log in or pass a CAPTCHA. Links to social profiles, shortened URLs and destinations that redirect may be removed automatically. That makes a location page a functional asset rather than a description, which is a meaningful change from treating it as a place to put an address.
Should a service area business create a page for every town it covers?
Only for places where it can say something genuine, which is usually far fewer than the list of places it would like to serve. Without a physical presence there is no address to anchor the page and no local detail to write about beyond the fact that you are willing to travel. Pages built on that alone are thin by construction. The more productive approach is fewer pages covering areas where you have completed work, have customers who will be named, and can describe conditions specific to that area.
What should appear above the fold on a local landing page?
The four things a local searcher needs to act, because local intent converts quickly and impatiently. Those are the specific service or business type, the address or service area so the visitor can judge proximity, current opening status rather than a table of hours they have to interpret, and a phone number that is tappable on a mobile device. Anything requiring scrolling before those four are answered is costing conversions from people who arrived ready to contact someone.
How much do location pages matter for AI answers about local businesses?
More than their weight in map pack ranking suggests. Analysis of local ranking factors has placed on-page signals at a modest share of local pack weight but a noticeably larger share of AI visibility decisions, which means the page carries greater importance for being described accurately in an AI answer than for appearing in the three-pack. Accurate structured data, consistent details across sources, and clearly stated specifics are what those systems can use and repeat.
