SEO

URL Structure

Also called Site URL architecture, path structure

The pattern of folders and paths a site uses, deciding how pages are grouped and addressed across the whole site.

Quick facts: URL Structure

Category
SEO
Also called
Site URL architecture, path structure
Level
Intermediate
Affects
Crawling, internal linking, reporting by section, migration risk
Where to see it
A crawler such as Screaming Frog, Search Console page reports, CMS permalink settings
In this article4
  1. How URL structure works
  2. Why URL structure matters
  3. Where URL structure goes wrong
  4. Getting it right

How URL structure works

A single URL names one page. URL structure is the pattern behind all of them: which folders exist, what sits inside each, how deep the nesting runs and how a slug is formed. On a WordPress site much of this falls out of the permalink setting and the way pages are nested, which is how sites end up with a structure nobody actually chose.

Two decisions carry most of the weight. The first is grouping — whether services sit in one folder per family or all at the root, whether the blog has its own path, whether locations are folders or slugs. The second is stability: whether a path describes something that will still be true next year. A path naming a permanent category survives. A path naming a season, a campaign or a year does not.

Why URL structure matters

In practical terms it makes a site legible. A visitor can read a path and know roughly where they are, and so can you when you are staring at a report. Grouping by folder means analytics and Search Console can be filtered by section with no tagging work at all, so you can see how an entire service area performs rather than page by page.

It also shapes everything built on top of it. Breadcrumbs, internal linking patterns and the navigation all follow the structure, and a clean one makes those cheaper to build and to maintain. The direct ranking effect of any one path is modest; the indirect effect of a structure that keeps a growing site organised is not.

Where URL structure goes wrong

The expensive mistake is changing it on a site that already performs. Every altered path breaks its old links and bookmarks along with whatever value those links carried, and even a carefully redirected move takes time to settle. Restructure only for a real reason, and when you do, map every old path to its genuine replacement instead of sweeping everything to the homepage — that is the core of migration work.

The everyday mistakes are smaller and more common: nesting so deep that nobody can read or repeat a path, dates baked into evergreen pages, campaign parameters left in the canonical address, uppercase or underscored slugs that behave inconsistently, and near-duplicate paths for one subject that end up competing with each other. Trailing slashes belong on the list too — pick one convention and hold the whole site to it.

Getting it right

Plan the structure before the pages exist, alongside the sitemap and the keyword map. Write out the folders you intend to have, then check that every planned page has an obvious home in exactly one of them. A page that could reasonably sit in two folders usually signals two overlapping pages that should be one.

After that, hold the line. Keep each slug short, lowercase and descriptive, use hyphens between words, and resist adding words purely for search. When a genuine restructure is unavoidable, treat it as a project with a redirect map, a crawl before and after, and a period of watching rather than a quick settings change. That combination of planning and restraint is most of what technical SEO asks of a URL.

Do and do not

Do

  • Decide the folder pattern before publishing, not afterwards
  • Keep paths short, lowercase and hyphenated
  • Redirect every changed URL to its true replacement

Do not

  • Put dates or campaign codes in evergreen paths
  • Rewrite a working URL to add keywords
  • Let the CMS invent a structure nobody planned

Questions people ask about this

Should I change my URLs to include keywords?

Rarely, and almost never on a page that already performs. A descriptive path is worth getting right when you create a page, but rewriting a working URL trades a small, uncertain gain for a real cost in broken links and an unsettled period after the redirect. If the current path is readable and roughly accurate, leave it alone.

How deep should the folder structure go?

Only as deep as the meaning requires. Each folder should represent a grouping a visitor would recognise, not an internal filing habit. A couple of levels serve most sites comfortably. Once paths become too long for anyone to read or repeat over the phone, the structure has usually stopped describing the site and started describing the organisation chart.

Do trailing slashes matter?

They matter for consistency rather than for ranking. A path with a trailing slash and the same path without one are technically different addresses, so a site serving both can end up with two versions of every page. Choose one convention, have the server redirect the other, and make sure internal links and canonical tags use the chosen form.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.