# Internal Links Between Location Pages

> The three links every location page needs, why the plain list page matters most, link patterns to avoid, and how to check what actually links where.

Source: https://localseoaudittool.co/internal-links-between-location-pages/  
Site: LocalSEOAuditTool  
Updated: 17 November 2026

---

Short answerLocation pages need three kinds of link to work: a link from a plain list that every page can reach, links from the services those branches provide, and a small number of links between nearby locations. What they do not need is a block of 60 town links in the footer. Links are how a crawler finds pages and how a customer gets to the right branch, and on most local sites both of those jobs are being done by a map widget that does neither.

Internal links between location pages sound like an abstraction until you look at a site where the Manchester page can only be reached by typing a postcode into a search box.

## The three links every location page needs

-
### From a locations list
A plain page listing every branch with an ordinary link to each. Linked from the main navigation or the footer so it is reachable from anywhere.

-
### From the relevant service pages
If the Leeds branch does MOTs, the MOT page should link to it, and to every other branch that does them.

-
### From nearby locations
Two or three, not twenty. "Our nearest other branches are X and Y" helps a customer who is in the wrong place.

A list page, the relevant services, and two or three nearby branches.

## Why the list page matters most

It is the page that makes the rest reachable. Without it, each location page depends on being linked from somewhere else, and in practice that means nothing links to them at all. A list page also gives Google a sensible place to understand the shape of the business: one brand, these branches.

Keep it plain. Name, address, one line, link. A map can sit above it for humans. The links below the map are what everything else depends on.

## What not to do

Pattern | Problem |

60 town links in the footer | Reads as an attempt to catch searches, and dilutes every page on the site. |

Links only inside a map widget | A crawler sees a script. Customers see a map they have to interact with. |

A dropdown of locations | Often fine for humans, often invisible as links, depending on how it is built. |

Every branch linking to every branch | Noise. Nobody in Exeter needs a link to Aberdeen. |

Keyword-stuffed link text | "Emergency plumber Leeds 24 hours" as a link looks exactly like what it is. |

## Link text that helps

Use the branch name and place: "Leeds (Mill Road)" or "Our Leeds branch". That is clear to a person and descriptive to a crawler, and it does not read as an attempt to stuff a phrase into a link.

The same applies from service pages: "MOTs at our Leeds branch" is a better link than "click here" and better than "Leeds MOT cheap best".

Sixty town links in a footer is not internal linking.

## Services crossed with locations

The useful pattern for larger businesses is a grid: service pages link down to the branches that provide the service, and branch pages link across to the services available there. That gives both kinds of visitor a route, and it keeps the number of links on each page small and relevant.

Resist building a page for every combination of service and town unless each combination is genuinely different. The links can exist without a separate page behind every pairing.

## Checking what links exist

Three quick checks, none of which need a tool. Open a branch page in a browser with JavaScript disabled and see what links survive. Use Search Console's links report to see which internal pages link to a given location page. And click through from the home page as a customer would, counting the clicks it takes to reach a specific branch.

If the answer to the last one is more than two, the structure is the problem rather than the content.

## Orphan pages

An orphan is a page nothing links to. On local sites they appear in two ways: a branch added to the content management system without being added to the list, and a page left behind when a template changed. Both are invisible until somebody compares the list of published pages with the list of linked pages, which is a five minute job and is worth doing once a year.

## A worked example

A regional bakery with nine shops. The site had a map on the home page and nothing else linking to the shop pages. Search Console showed two shops indexed, both of which happened to be linked from a blog post about a refit.

Three changes: a shops page listing all nine with addresses and links, a footer link to that page from every page, and a line on each shop page naming the two nearest other shops. No new content, no new pages beyond the list.

Seven of the remaining shops were indexed within a month. The ninth, in a shared unit with no separate address, needed a different fix entirely.

## Navigation versus body links

A link in the main navigation reaches every page and is worth having for the locations list. Links buried in body text are worth more per link, because they carry context: a sentence explaining what the branch does before the link to it.

The practical split for most local sites is one navigation link to the locations page, and body links from the service pages, the about page and any blog post that mentions a branch. That gives breadth from the navigation and specificity from the content, and it avoids the usual failure where the navigation is the only linking the site has ever done.

## Breadcrumbs

On a site with a locations section, breadcrumbs do a quiet job: they link every branch page back up to the list, on every page, without anybody having to remember. They also help a visitor who arrived from search understand where in the site they are, which is most visitors on a location page.

## Keeping it tidy as the business changes

Every opening and closure should touch the list page, the service pages and the nearby-branch lines on two other pages. Write that down, because it is exactly the sort of maintenance that gets missed, and a list page with a closed branch on it is worse than no list at all.

### See how your pages connect
Audit internal links to every location page and find the branches nothing points at.

[Run an audit](/tools/gbp-audit-tool/) [Store locator](/tools/store-locator/)

## Frequently asked questions

**Q: How should location pages be linked?**
From a plain list page reachable site-wide, from the service pages relevant to that branch, and from two or three nearby locations.

**Q: Is a map enough to link my location pages?**
No. A map widget usually produces no links a crawler can follow, so the branch pages end up reachable only by people who use the tool.

**Q: Should every branch link to every other branch?**
No. Two or three nearby branches is useful. A full cross-link between forty locations is noise for customers and crawlers alike.

**Q: What link text should I use?**
The branch name and place, such as "Our Leeds branch" or "Leeds (Mill Road)". Keyword stuffed link text reads exactly as what it is.

**Q: How do I check which pages link to a location page?**
Disable JavaScript and see which links survive, use the links report in Search Console, and count the clicks from the home page as a customer would.

## Sources
The Google documentation behind the guidance on this page. Google changes these pages without notice, so check the date on any figure before you rely on it.

- [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide)
- [Consolidate duplicate URLs with canonicals](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
