Location page URL structure: /plumber/brighton/ or /brighton/plumber/?

Short answer

Neither ranks better: Google’s SEO Starter Guide says keywords in a URL path have hardly any effect. Match how your site is organised. Use /plumber/brighton/ when each service has a hub page listing its towns, /brighton/plumber/ when each town is a branch offering several services, and keep it once chosen. A flat /plumber-brighton/ suits a small set.

The order of words in a location page’s address is one of the smallest decisions in local SEO, and one of the most expensive to change later. What matters is that the address matches how the site is organised, because in WordPress the address is the organisation: a page’s parent decides its path.

This guide covers the address only. For which location pages to build in the first place, see multi-location SEO in WordPress; if you are about to create many at once, decide the pattern before you bulk create the pages.

What does Google say about URL structure?

  • Keywords in the path barely count. Google’s SEO Starter Guide lists keywords in the domain name or URL path among the things not to focus on, saying they have hardly any effect beyond appearing in breadcrumbs.
  • Readable words, separated by hyphens. Google’s page on URL structure best practices recommends readable words rather than long ID numbers, hyphens rather than underscores, words in your audience’s language, and one consistent case.
  • Folders can help on larger sites. The Starter Guide adds that grouping topically similar pages in directories can help Google learn how often the URLs in each directory change. Crawl budget for local sites covers when that starts to matter.

Nothing in either page prefers the service before the town or the town before the service. The words in an address matter to people, who see it in a shared link or as breadcrumbs in the results. The order is yours to choose.

Which structure suits which business?

PatternExampleSuitsThe parent page is
Flat/plumber-brighton/A small set, or addresses that already rankNone
Service first/plumber/brighton/One base, several services, many towns: most service-area businessesThe service page, listing its towns
Area first/brighton/plumber/Branches, where each town has premises offering several servicesThe branch page, listing its services
Under one section/areas/brighton/One main service across many towns, or a list of branches“Areas we serve” or “Locations”

Service first fits most trades. The service page is the hub: it links to every town, and each town page links back up to it. Area first fits a business whose towns are places customers visit, because the town page is then the branch page, the one its Google Business Profile links to, with each service beneath it. Business Profile or location pages explains which profile should link where. Service page or location page covers the different job each one does, and internal linking for local pages shows how the links run in each shape.

Flat is not a lesser option. It is the simplest, and the right one for a handful of pages; what it lacks is a folder that groups the set, which matters more as the set grows. Whichever you choose, use one pattern for the whole set. A site with /plumber/brighton/ and /hove/plumber/ leaves visitors, and whoever maintains the site, guessing.

How do WordPress parent pages shape the URL?

In WordPress, a page’s address is its parent’s address followed by its own slug. The editor’s help text for the Parent setting puts it plainly: child pages inherit their parent’s URL structure. So /plumber/brighton/ is a page with the slug brighton whose parent is the page at /plumber/.

  • Slugs only have to be unique among siblings. WordPress checks a page’s slug against pages with the same parent, so /plumber/brighton/ and /heating/brighton/ can both use brighton.
  • It needs readable permalinks. Under Settings, Permalinks, any option except Plain. With Plain, pages are addressed by ID and the parent never shows.
  • A parent’s slug is part of every child’s address. Rename /plumber/ to /plumbing/ and every town page beneath it moves too.
  • Custom post types work differently. A post type gets its base, such as /locations/, when it is registered, and its entries sit under that base rather than under a page.

You set a page’s parent in the editor’s settings sidebar, or for several pages at once with Quick Edit in the Pages list. How to create location pages in WordPress walks through it.

How do you change the structure later without losing ground?

First, ask whether you need to. If the current addresses rank and bring enquiries, a tidier pattern is rarely worth the disruption: Google’s guide to moves with URL changes warns that visibility may fluctuate temporarily during a move. If you do have a reason, such as merging two sites or opening branches, work through it in this order:

  1. Map every old address to its new one. Export the current URLs from your sitemap or Search Console and write the new address beside each.
  2. Make the change on a staging copy first, if your host gives you one.
  3. Add a permanent (301) redirect from each old address to its new one. Google treats a permanent redirect as a signal that the target should be the canonical address. The Redirection plugin, with over two million active installs, can import the old-and-new list as a CSV.
  4. Point everything at the new addresses: internal links, menus, and the website link on each Google Business Profile, so none of them goes through a redirect.
  5. Keep the redirects for at least a year, which is Google’s guidance for site moves, and watch Search Console for addresses that now return 404. Measuring location pages shows what else to read there in the weeks after.

Do not leave the redirects to WordPress. It keeps a record of a post’s old address when its slug changes, but not a page’s. For a missing address it guesses from the last part of it, and in our test on WordPress 7.1.4 the guess found the right page when we moved one page under a new parent. It failed on a structure change: after we moved /plumbing/lewes/ and /heating/lewes/ to /lewes/plumbing/ and /lewes/heating/, WordPress sent both old addresses to the same unrelated page, another page with the slug lewes.

Which URL patterns does Townsmith support?

Local Pages Engine, which we make, sets the pattern once, under Local Pages, Settings. It has four, under these names in the plugin:

  • Flat: /boiler-repair-leeds/, with no parent page.
  • Hierarchical: /boiler-repair/leeds/, each page nested under its service’s hub page. This is service first.
  • Area first: /leeds/boiler-repair/, each page nested under its area’s landing page.
  • Custom: one parent page you choose, with the slug written as a template from {service} and {area}, such as /locations/boiler-repair-leeds/. It exists to reproduce a structure you already rank with.

Hierarchical and area first need a hub page for each service or each area, chosen on the same Settings screen; a page without one falls back to a flat address rather than landing somewhere broken. A custom template without {area} would give every page the same slug, and the settings screen warns you before that happens.

Switching pattern does not move pages that already exist; it applies to the pages you generate next, and on the free plugin existing pages keep their addresses. Pro can move existing pages to the new pattern in bulk, either serving a 301 from each old address itself or reporting each move to your redirect manager. Its built-in redirects keep the 500 most recent moves, so for a larger set, let a redirect plugin hold them. The URL structure documentation has the detail, and service area pages shows the plugin as a whole.

Common questions

In a flat URL, should the town or the service come first?

Google’s documentation does not prefer either. Pick whichever reads naturally, boiler-repair-leeds or leeds-boiler-repair, and use it for every page.

Should the URL include the county or a postcode?

Only where a town name is shared, such as Newport, and then the county reads more clearly than a postcode district. Otherwise keep the address short.

How many levels deep should location URLs go?

Two cover almost every business: a hub and the pages beneath it. A third level, such as region, then town, earns its place only if the region pages are real pages people use. How many location pages to build helps decide what exists at all.

Will moving to a nested structure improve my rankings?

Not by itself, given how little Google says the words in a path count. Change structure for a reason you can name, and budget for the redirects and the dip that can follow.

Checked against Google’s documentation and WordPress 7.1.4 on 5 November 2026. Written by Stephen Evans, who makes Local Pages Engine.