Location Pages That Aren’t Thin: How to Build Them After the 2026 Updates

If you run a business with more than one branch, or you serve several towns, someone has probably told you to “build a page for every location”. Done badly, that advice creates dozens of near-identical pages that Google treats as doorways. Good location pages SEO is the opposite. It means one page per real location, each built around information a customer can only get from that page.

In this guide I cover where Google draws the line and what unique content every location page needs. I also cover how to structure and link the pages, how to mark them up, and when you should not create a page at all. Near the end there is a worked example outline you can copy.

Why Location Pages Get Flagged as Thin or Doorway Pages

Google’s spam policies define doorway abuse as pages made to rank for specific, similar searches. These pages lead users to in-between pages that are less useful than the final destination. One of the listed examples is having pages aimed at specific regions or cities that funnel users to one page.

That describes the classic city-swap template almost exactly. It’s the same 500 words, the same stock photo and the same contact form, with “Leeds” replaced by “Bradford” and then “Wakefield”. Each page exists to catch a “[service] in [town]” search, not to help anyone in that town.

A second policy often applies at the same time. Scaled content abuse covers making many pages mainly to manipulate rankings, with little value added for users. It doesn’t matter if this is done by AI tools, scraping or automatic rewording. Spinning 200 suburb pages with an AI writer falls right into that.

You can read both definitions in full in Google’s spam policies for Google web search. The key point is that Google is not against location pages. It is against pages that only differ by a place name.

What the 2026 Updates Mean for Location Pages

Google has already run core updates in March and May and spam updates in March and June this year. It did not name location pages as a target in any of them, and it published no new policy on doorways. If you are looking into a drop, the June 2026 spam update is the most recent one to check your dates against.

What has changed is the cost of getting it wrong. AI tools now make it very easy to produce hundreds of town pages. So templated local content is easier to spot as a pattern, and a large block of weak pages can drag down how a site is judged overall. My reading is simple: fewer, better pages beat many thin ones.

Location Pages vs Service Area Pages

People often mix up these two terms. The difference decides what you can honestly put on the page.

• Location pages are for physical premises that customers visit: a branch, clinic, showroom or office with staff and an address. Each one normally has its own Google Business Profile.
• Service area pages are for towns you travel to but have no premises in. They cannot show a local address, map pin or opening hours for a walk-in branch. So they need to earn their place with local jobs, response times and area-specific detail.

If you have no shopfront at all, the rules are different again. Our guide to service area business SEO covers how to rank without one. The rest of this article focuses on pages for real, staffed locations, though most of the content advice applies to both.

What Unique Content Every Location Page Needs

Here is the test I use. If you deleted the town name, could a reader still tell which location the page is about? If not, the page is too thin. These are the parts that make the answer yes.

Accurate Core Details

Start with the basics. Make sure they match the location’s Google Business Profile exactly.

• Branch name, full address and a local phone number that rings at that branch.
• Opening hours, including holiday and seasonal changes.
• An embedded map and a clear link to get directions.
• How to book or contact that specific branch, not a generic head-office form.

Directions, Parking and Access

In my experience, this is the most underrated section, and it is unique by its nature. Tell people which entrance to use, where to park and what it costs, the nearest bus stop or station, and whether there is step-free access.

Landmarks help. “Next to the library, opposite the Co-op” is more useful than a postcode alone. These details also answer the practical questions people now ask AI assistants before they visit.

Services Specific to That Location

Few multi-site businesses offer exactly the same thing everywhere. One branch may have the specialist equipment. Another may do evening appointments. A third may be the only one with a trade counter.

List what this branch really offers, and be honest about what it doesn’t. “Implants are done at our Harrogate clinic” is helpful. Pretending every branch does everything sends customers to the wrong door.

Real People

Introduce the branch manager and key staff with a name, role, short background and a real photo. For regulated professions such as dentists, solicitors or opticians, include registration details where relevant.

This is genuine first-hand detail no competitor can copy. I see it as one of the clearest signals that a real team works there.

Photos of the Actual Place

Use photos of the outside of the building (so people recognise it when they arrive), the inside, the team and the work done there. Stock photos of a generic smiling receptionist add nothing and are easy to spot.

Local Proof

Show that this branch serves this community.

• Reviews from customers of that location, shown honestly and not cherry-picked or faked.
• Short examples of recent jobs or projects in the area, with the customer’s permission.
• Local partnerships, sponsorships or accreditations tied to that branch.
• Anything that changes because of the local area, such as housing types, local rules or the common problems customers there bring in.

When you collect reviews to feature, stay within Google’s rules. Since April, review quotas for staff and asking customers to name staff are both banned. Our guide to the 2026 Google review policy explains what is still allowed.

Location-Specific FAQs

Write FAQs that only this branch can answer: “Can I park on site?”, “Do you take walk-ins on Saturdays?”, “Is the Riverside branch wheelchair accessible?”. Take them from what customers really ask the branch staff by phone and at the desk.

Don’t copy the same eight company-wide FAQs onto every page. They belong on your main service pages.

How Much Unique Content Is Enough?

There is no official percentage, and anyone quoting one is guessing. Some shared content is fine: your brand promise, a summary of your guarantee, or a short description of a service.

The test is whether the unique parts are big enough and useful enough on their own. The page should be worth visiting even if the shared parts were removed. If the only unique items are the address and a map, it fails.

How to Structure Location Pages and Link Them

URL Structure

Keep it simple and predictable. For most businesses that means a locations hub and one child page per branch:

• /locations/ for the hub or store finder
• /locations/harrogate/ for each branch
• /locations/york-clifton/ if you have two branches in one city

Large chains with hundreds of sites can add a region level, such as /locations/yorkshire/harrogate/. Only do that if the region pages are useful lists in their own right, not filler.

The Locations Hub

The hub is an index people can browse. It lists every branch with its address, phone, hours and a link to its page, plus a search or map for larger networks. This gives you the “clearly defined, browseable hierarchy” that Google contrasts with doorways.

Make sure the branch links are plain HTML links that load without someone typing a postcode first. A store locator that only shows results after a search can leave your location pages with no crawlable links pointing to them. This is one of the first things I check on a multi-location site.

Internal Linking

1. Link to the hub from your main navigation or footer.
2. Link each location page back to the hub and to its nearest one or two other branches (“Also near you: York Clifton”).
3. Link from each location page to the main service pages it offers. Link from service pages to the branches that provide that service.
4. Use descriptive link text such as “our Harrogate clinic”, not “click here”.
5. Add all location pages to your XML sitemap.

This follows the cluster approach in our internal linking strategy guide. The hub is the main (pillar) page and each branch is a cluster page.

Titles and Headings

A clear pattern works well. Use “[Service] in [Town] | [Brand]” for the title, and a heading that names the branch, such as “Northgate Dental, Harrogate”. I write each meta description by hand for the main branches, mentioning something specific like late opening or free parking.

LocalBusiness Schema for Each Location

Each location page should carry its own structured data (code that describes the business to search engines) for that branch, not the head office. Google’s local business documentation lists name and address as required. It recommends geo, openingHoursSpecification, telephone, url and priceRange.

Use the most specific type available, such as Dentist, AutoRepair or Plumber, not plain LocalBusiness. Give each branch a stable @id and connect it to the brand with parentOrganization.

{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "@id": "https://www.example.com/locations/harrogate/#dentist",
  "name": "Northgate Dental Harrogate",
  "url": "https://www.example.com/locations/harrogate/",
  "telephone": "+44 1423 000000",
  "image": "https://www.example.com/images/harrogate-front.jpg",
  "priceRange": "££",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Station Parade",
    "addressLocality": "Harrogate",
    "postalCode": "HG1 1AA",
    "addressCountry": "GB"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 53.99312,
    "longitude": -1.54011
  },
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "08:30",
    "closes": "18:00"
  }],
  "parentOrganization": {
    "@id": "https://www.example.com/#organization"
  }
}

A few rules that save headaches:

• Every value in the markup must match what is visible on the page and on the Business Profile.
• Give coordinates to at least five decimal places, as Google recommends.
• Don’t add aggregateRating built from reviews of your own business. Google doesn’t show review stars for self-serving reviews on LocalBusiness and Organization markup.
• Test each template with the Rich Results Test and watch for errors in Search Console after launch.

For the wider picture of how this fits with Organization and other types, see our schema markup guide.

Linking From Google Business Profile

Each branch should have its own Business Profile. Each profile’s website field should point to that branch’s location page, not your homepage. Google’s guidelines say the website you list should represent your individual business location. They also warn against links that redirect users elsewhere.

Linking profile to page has practical benefits. Searchers who click “Website” land on the hours, parking and team details they wanted. And the address, phone and hours on both are easy to keep in sync.

A few checks for each profile:

• Use the final URL of the page, without redirects. If you add UTM tags for tracking, keep the base URL the same.
• Check the business name, address, phone and hours match the page exactly.
• Update the page and the profile together when hours or services change.

The full rules are in Google’s guidelines for representing your business.

When Not to Create a Location Page

Saying no to a page is often the best local SEO decision you make. I’d skip one when:

• You have no premises there. Don’t invent a branch page with a virtual office, coworking desk or a relative’s address. That puts your Business Profile at risk as well as your rankings.
• You have nothing unique to say. If the only difference would be the town name, cover the area on a strong service page or a single “areas we cover” page instead.
• The places overlap. Separate pages for every suburb of one city, all served by the same branch, are a textbook doorway pattern. One page for the branch that mentions the areas it serves is better.
• There is no demand. If nobody searches for your service in that village and you get no enquiries from it, a page adds upkeep with no return.
• The branch has closed or is temporary. Redirect a closed branch’s page to the nearest open branch or the hub, and update the profile.

If you already have a pile of thin town pages, audit them. Keep and improve the ones that get traffic or enquiries. Merge the rest into fewer, stronger pages, and redirect the removed URLs to the closest relevant page.

Worked Example: A Location Page Outline

Here is an outline for a made-up dental practice, Northgate Dental, with three clinics in Harrogate, York and Ripon. This is the Harrogate page.

1. Title: Dentist in Harrogate | Northgate Dental Station Parade
2. Heading and intro: “Northgate Dental, Harrogate”. Two sentences on who the clinic serves and what makes it different, such as being the group’s implant centre and opening until 8pm on Thursdays.
3. Key details box: address, phone, hours, “Book at Harrogate” button and an embedded map.
4. Getting here: a five-minute walk from the railway station, which car park to use and its cost, the step-free side entrance, and nearby bus routes.
5. Treatments at this clinic: the services offered here, each linking to its main service page. A note that orthodontics is at the York clinic, with a link.
6. Meet the team: the principal dentist, hygienist and practice manager, each with a photo, role, registration number and a line about their background.
7. Inside the clinic: four to six real photos of the front, reception, treatment rooms and equipment.
8. What patients say: a handful of recent reviews from Harrogate patients, with a link to the clinic’s Google reviews.
9. Local involvement: the school dental-health visits the team runs, if they really do.
10. Harrogate FAQs: parking, emergency appointments, accepting new NHS patients, wheelchair access.
11. Other clinics nearby: links to York and Ripon, plus the locations hub.
12. Behind the scenes: Dentist schema for this clinic, linked to the Organization, and the Harrogate Business Profile pointing to this URL.

Notice how little of that could be pasted onto the York page. That is the goal.

How to Measure Location Pages SEO Results

Track each page on its own, not as a group. In Search Console, filter by page to see the queries and clicks each location earns. In your analytics, measure calls, bookings and direction clicks by landing page.

On the Business Profile side, the Performance report shows website clicks, calls and direction requests per location. Pages that get no impressions after several months usually need more unique substance or better internal links. Or you need to decide whether they should exist at all.

Conclusion

Location pages SEO comes down to one rule: build a page only where you have a real place and real things to say about it. Accurate details, directions, local services, real staff, real photos, honest reviews and branch-specific FAQs make a page useful. That is exactly what keeps it clear of Google’s doorway and scaled content policies.

My advice is to start by auditing the location pages you already have against the outline above. Fix or merge the weakest first. Then make sure every branch carries accurate markup, using our schema markup guide as a checklist.