Structure is the cheapest thing to get right before a build and among the most expensive to change afterwards. Design can be revised repeatedly at low cost. Moving pages later breaks addresses, redirects, internal links, accumulated search value, and the habits of anyone who bookmarked something.
Why it comes first
Design decisions are reversible. A colour, a typeface, a layout, even a full visual redesign can be changed without touching anything underneath.
Structural decisions are not. Where a page sits determines its address, and its address is what every link, bookmark, and search listing points at. Changing it later means redirects, a period of instability, and a real risk of losing accumulated value, which is the most damaging item in the redesign mistakes that hurt search visibility.
So the structure conversation happens before anyone opens a design tool, and it takes an hour or two rather than a week.
What the conversation has to settle
The page list
Every page the site will have at launch, and the ones expected within a year. Planning for the second group is what prevents an awkward retrofit when the fourth service page arrives.
The hierarchy
Which pages are top level and which sit beneath others. For a small business this should be flat: most pages one level down, very little two levels down, and nothing three levels down. Depth buries pages from both visitors and crawlers.
The addresses
Short, readable, and describing the page rather than its position in a menu. Decided now because they are permanent, and the reasoning is set out in URL structure decisions.
What goes in the navigation
Not everything. Navigation is for the routes most visitors need, which is usually five to seven items. Everything else lives in the footer or is reached from within a page.
What each page is for
One sentence each, stating who lands there and what they should do. Pages without an answer are usually pages that should not exist, and this is where they get caught.
The navigation decision specifically
Menus grow because everyone wants their section represented, and a menu representing internal structure rather than visitor tasks is the most common navigation failure.
Two principles keep it manageable. Group by what the visitor is trying to do rather than by how the business is organised. And use words customers use, which is a harder discipline than it sounds and is examined in what unclear navigation labels cost you.
The footer takes the pressure off. Legal pages, secondary information, and anything needed occasionally can live there without competing for space in the main menu.
Leaving room
The structure has to accommodate a business that will change. Three provisions cover most of it.
- A services section that can take more services without the menu becoming unusable at eight items.
- A locations pattern that works for one area and for six, so the third one is not a redesign.
- Somewhere for articles to live even if none exist yet, so adding them later does not require inventing a section and a URL pattern under time pressure.
Who should be in the conversation
The owner, whoever will update the site, and whoever answers the phone. That last person is usually excluded and knows what customers actually ask for and in what words, which is exactly what the structure has to reflect.
It is a short conversation with a long shadow. An hour spent here removes most of the revision cycles that otherwise appear during design, because a great deal of what feels like a design disagreement is an unresolved structural question surfacing as an argument about a layout.
The artefact
The output is a single page: every page listed, indented to show hierarchy, with its address and a one-line purpose beside each.
That document is what the design is built against, what the content is written into, and what gets checked at launch to confirm nothing was quietly dropped. It also becomes the reference for the next change, so the person adding a page in two years can see the pattern rather than guessing at it. For a small business site the whole thing fits on one side of paper, which is a fair indication of how much the exercise costs relative to what it prevents.
Frequently asked questions
What is site structure and why does it matter?
The page list, the hierarchy, and the addresses. It matters because design changes are cheap and reversible while structural changes break links, bookmarks, and accumulated search value.
How deep should a small business website be?
Flat. Most pages one level below the homepage, very few two levels down, and nothing three levels down. Depth buries pages from both visitors and crawlers.
How many items should be in the main navigation?
Usually five to seven. Navigation is for the routes most visitors need, and everything else can live in the footer or be reached from within a relevant page.
Should I plan pages I do not have yet?
Yes, for the ones expected within a year. Leaving room for more services, more locations, and an articles section prevents an awkward retrofit later.
Who should be involved in planning site structure?
The owner, whoever will update the site, and whoever answers the phone. The last of those knows what customers ask for and in what words, which is what the structure should reflect.
What should the planning produce?
A single page listing every page, indented to show hierarchy, with its address and a one-line purpose. It guides the design, the content, and the launch check, and it fits on one side of paper.
West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.
Starting a build and not sure where to begin?
We settle the structure first, in a short session, so the design has something solid to sit on and the project does not circle through revisions.
Start a Conversation