Direct answer
A good website structure answers three questions at a glance: where am I, how did I get here, and where can I go next.

Website structure: what to know
Each rule is listed with its source at the end of this page, read on November 12, 2026.
- Use a top navigation bar for three to seven top-level destinations and content-first sites such as marketing, docs and stores.
- Use a sidebar for app-like products with many destinations or nested sections; it scales vertically and supports group headers.
- Use one primary navigation pattern per screen width; a sidebar on desktop can become a bottom tab bar on a phone.
- Show no more than two navigation levels at once: primary plus secondary.
- Mark the active page with a treatment that differs from hover, and set aria-current="page" on its link.
- Use breadcrumbs only when the hierarchy is real and more than two levels deep; truncate a long trail from the middle, never the ends.
- An in-app back link goes to a known parent page; browser back returns to the previous page in history.
- Every link leads somewhere: no href="#", no loop and no page a visitor cannot leave.
- Give every topic a stable URL and list it in a visible table of contents.
- Do not hide every destination behind a menu button on a phone; keep the two to four most important ones visible and move only the rest into More.
- Put a Skip to content link first, and wrap each navigation region in a labelled nav landmark.
Which navigation pattern fits which site
| Pattern | Best for | Limit |
|---|---|---|
Top navigation bar | Best for Marketing sites, docs and stores | Limit About seven items, then a More menu |
Sidebar | Best for Apps, dashboards, editors and admin | Limit Group items under section headers |
Bottom tab bar | Best for Peer destinations on a phone | Limit Five tabs at most |
Breadcrumbs | Best for Hierarchies more than two levels deep | Limit A supplement, never the main navigation |
Command palette | Best for Keyboard users who already know the map | Limit Never the only way to reach a page |
Put Website structure into practice
- Build the pages first and design the navigation that connects them last.
- Count the top-level destinations and pick a top bar, a sidebar or bottom tabs.
- Group the rest into at most one secondary level under each section.
- Mark the active page and give every page a stable URL.
- Check every link and every back path on the rendered site at desktop and phone widths.
Website structure in four steps
The four steps, in the order you take them.

- Step 1: Build the pages
- Step 2: Pick the primary pattern
- Step 3: Add one secondary level
- Step 4: Check links and back paths
Caveats to keep in mind
- A top bar, a sidebar and tabs on one screen leave the visitor unsure which one says where they are.
- Breadcrumbs on a two-level site are decoration.
- An in-app back arrow that calls history.back() sometimes sends the visitor off the site.
- A tab kept only in page state disappears on reload and cannot be shared; keep it in the URL.
Steal this workflow
Run this guide in your own assistant. The prompt carries the guide link and the workflow summary, so the assistant can adapt it to your project.
Read the guide "Website structure: navigation that tells visitors where they are" at https://better-design.com/blog/website-structure and help me apply it to my project.
A good website structure answers three questions at a glance: where am I, how did I get here, and where can I go next.
Start by asking what I am building and which tools I use. Then walk me through the workflow step by step, adapted to my answers.Claude and ChatGPT open with the prompt filled in. Gemini copies the prompt to your clipboard first, so paste it when the app opens.
Questions
What is website structure?
It is the hierarchy that connects a site's pages, shown through its navigation. A good structure tells the visitor where they are, how they got there and where they can go next.
How many items should a top navigation bar have?
Three to seven. Past about seven, move the rest into a More menu before the bar wraps.
Can a coding agent apply these navigation rules?
Yes. Put these rules in the agent's instructions before it builds, then ask it to check the rendered screen against each one.
Where these rules come from
Each fact comes from Better Design's navigation guidance, the same guidance its MCP server gives coding agents, read on November 12, 2026.
Related
Build the interface in your own code instead
A coding agent such as Claude Code, Cursor or Codex can build these screens in your own code. Better Design gives that agent a design system, interface principles and review rules, so the result follows rules like these and looks designed.