How to Structure a Website

A website’s structure is the set of decisions about what pages exist, how they nest, what the URLs look like and how someone navigates between them. It gets decided quickly at the start of a project and then lived with for years, which is a poor ratio of thought to consequence. A good structure makes adding a page obvious. A bad one makes every addition a debate about where it goes, and eventually produces the miscellaneous section that nobody can navigate.

Start From Intent, Not From Your Org Chart

The most common structural mistake is organising a site the way the business is organised. Visitors do not know your departments and do not care which team owns which service. They arrive with a task.

So begin by writing down the five or six things people actually come to do. For a business like ours that is roughly: work out whether you can solve my problem; see whether you have done it for someone like me; understand roughly what it involves; check you are real; and get in touch. Every page should serve one of those, and a page that serves none of them is a page to question.

The Shape That Works for Most Businesses

Two rules keep this honest. Depth: anything a customer needs should be about three clicks from the homepage; if something is five levels down, either it does not matter or your categories are wrong. Breadth: a navigation menu with fourteen top-level items is not a structure, it is a list — group until it is five to seven.

And segment pages only where the need genuinely differs. Duplicating a page per town with the name swapped is the single most common way to build a structure that neither people nor search engines respect.

URLs: Decide the Pattern Before You Build

• Readable and descriptive. /uk/website-development/ tells a person and a crawler what is there. /page?id=4471 tells neither.
• Lowercase, hyphenated, no spaces or underscores. Boring and universally understood.
• Short, but not cryptic. Drop filler words; keep the meaning.
• Reflect the hierarchy, once. /uk/erp/ is useful. /services/software/erp/systems/uk/custom/ is a filing accident.
• No dates in evergreen URLs. A guide with 2024 in its URL looks stale in 2026 even after you update it.
• Pick a trailing-slash convention and enforce it, with the other form redirecting. Two URLs serving one page is a duplicate you created yourself.
• Do not put the format in the path unless it is genuinely a file. .html in a URL commits you to a technology choice for as long as the URL lives.

The reason to settle this before building: once a URL is published and linked, changing it costs a redirect and a little risk every time. It is the cheapest decision to get right and one of the more annoying to reverse. See redesigning without losing SEO for what that reversal involves.

Navigation, Breadcrumbs and Internal Links

Three different jobs, often conflated.

• The main navigation is for the handful of routes most people need. It is not a site map, and it should not contain everything.
• Breadcrumbs tell someone who arrived from search where they have landed and what the parent category is. On a site more than two levels deep they are genuinely useful, and BreadcrumbList structured data makes them useful to search engines too.
• Internal links in the body carry the real weight: they route people to the next thing and pass authority between your pages. This is the part most sites leave entirely to the template — see internal linking done properly.
• The footer is where the long tail belongs: everything legitimate that does not deserve main navigation.

One check worth running: pick your three most commercially important pages and count how many internal links point at each. If the answer is one, the structure is not supporting them regardless of how the menu looks.

The Three-Year Test

Every structure looks fine at launch, when the page count matches the plan. The real test is what happens as things get added, so run it in advance:

• A new service launches. Does it have one obvious home, or does it need a new top-level item?
• You expand to a new market. Does the pattern extend, or does it require a parallel structure?
• Fifty articles get published. Are they findable by subject, or only by date?
• A service is retired. Is it clear what to redirect it to?
• Someone joins and has to add a page. Could they work out where it goes without asking?

If the answer to the last one is no, the structure will decay no matter how carefully it was drawn. Write the rule down — where things go and why — and keep it with the site. See UK web development for how we settle this before design starts.

Frequently Asked Questions

How should I structure a website?

Start from the five or six things visitors are actually trying to do, not from your internal departments. Give each thing you sell one deep hub page, add segment pages only where the need genuinely differs, keep anything a customer needs within about three clicks, and group the main navigation down to five to seven items.

How many levels deep should a website be?

Anything a customer needs should be reachable in about three clicks from the homepage. If a page sits five levels down, either it does not matter enough to exist or your categories are wrong. Depth also shows up in URLs — a path with six segments is usually a filing accident.

What should website URLs look like?

Lowercase, hyphenated, readable, and descriptive of the page. Reflect the hierarchy once, keep them short without being cryptic, avoid dates in evergreen URLs, pick one trailing-slash convention and redirect the other, and avoid committing to a file format in the path. Decide the pattern before building, because changing a published URL costs a redirect and some risk.

How do I create my own website structure from scratch?

Write down the tasks visitors arrive with. List every page you think you need and delete any that serves none of those tasks. Group what remains into five to seven top-level areas. Draw the URL pattern. Then apply the three-year test: could a new colleague work out where a new page goes without asking?

Do breadcrumbs matter?

On a site more than two levels deep, yes — they tell someone who arrived from search where they have landed and what the parent category is, and BreadcrumbList structured data makes that legible to search engines. On a flat five-page site they add little.