How to Plan Your Website Structure Before You Build It
Plan your site map, navigation and page hierarchy first. A simple structure helps visitors find what they need and helps search engines understand your site.
Most small business websites grow by accident. A page is added for a new service, another for a promotion, and a year later nobody can find the price list. Planning the structure before you build costs an afternoon with a pen and paper and saves months of awkward rework. This guide shows a practical way to do it without any specialist tools.
Start from questions, not pages
Ask what your visitors are trying to do. A plumber's customer wants to know: do you cover my area, can you come soon, what will it cost, how do I reach you. A consultant's prospect asks: what do you do, have you worked with companies like mine, how do we start. Write ten to fifteen real questions on sticky notes. If you have a support inbox or a phone log, use the actual questions people ask; they are better than any you will invent.
Group the notes into sections
Sort the questions into piles. Each pile is a candidate section of your site. Typical piles for a service business are:
- What we offer (services or products)
- Who we are (about, team, values)
- Proof (case studies, reviews, certifications you genuinely hold)
- How to buy or get started (pricing, process, booking)
- Help (FAQ, contact, delivery or support information)
If a pile has only one note, it probably belongs inside another section. If a pile has thirty, split it.
Keep the hierarchy shallow
A good rule is that important pages should be reachable within two or three clicks from the homepage. A simple three-level structure covers most small businesses:
- Homepage: the summary and the doorway to everything else.
- Section pages: for example "Services" or "Shop".
- Detail pages: a single service, product or article.
Deeper nesting is rarely needed. If you find yourself drawing a fifth level, consider whether the content should be a filtered list instead.
Design the main navigation
Navigation labels should use the words your customers use. "Solutions" means little; "Boiler repair" is clear. Limit the main menu to roughly five to seven items, and put the action you want most (such as "Get a quote" or "Book") in a visually distinct position. Keep utility links like login, cart and language switcher separate from the main menu so they do not compete with it.
Footer navigation is the place for legal pages, secondary links and contact details. People do look there, particularly for contact information and policies.
Plan URLs at the same time
Addresses should be short, readable and stable. A structure such as /services/boiler-repair tells both visitors and search engines where they are. Avoid dates, IDs and long strings in addresses where you can. Once pages are published and linked from elsewhere, changing their URLs requires redirects, so choose carefully now.
| Poor URL | Better URL |
|---|---|
/page_id=482 | /services/boiler-repair |
/our-amazing-services-for-you-2024 | /services |
/blog/2023/05/12/post-title | /blog/post-title |
One page, one job
Each page should target one main topic or intention. If two pages could answer the same search ("plumber in Leeds" and "Leeds plumbing services"), merge them or clearly differentiate them. Overlapping pages compete with each other in search and confuse visitors. Equally, avoid one giant page that tries to cover everything; separate services deserve separate pages so each can describe what is included, who it is for and how to start.
Link pages to each other
Navigation is only one path. Inside page text, link to related pages naturally: a service page can link to the matching case study, and an article can link to the service it supports. Internal links tell search engines which pages matter and help visitors continue their journey. Use descriptive link text ("see our boiler repair prices") rather than "click here".
Sketch before you build
Draw the structure as a simple tree, one box per page. Then do a quick test: pick three tasks a visitor might attempt and trace the clicks needed. If someone cannot find your contact page or your pricing in three clicks, redraw. Show the sketch to a customer or a friend and ask where they would click to find something specific. This takes ten minutes and often exposes labels that make sense only to you.
Finally, keep a living document of the structure. When you add a page, decide where it belongs first. Review the map twice a year and remove or merge pages that no longer serve a purpose.
Plan for growth and change
A structure should survive the next two years. Ask yourself what you might add: a shop, a blog, a second language, a members area. You do not have to build these now, but leave room for them in the map and in the navigation. For example, choose a section name like "Resources" rather than "Latest news" if you expect to publish guides, case studies and updates together. Think also about who will maintain the site. If a colleague will edit pages, a simple structure with clear names is far easier to keep tidy. When the site becomes larger, the knowledgebase style of grouping, with short categories and clear titles, is a good model for help content.
Build on a flexible foundation
A well-planned site structure is easy to implement on any content management system, but you want hosting that lets you add sections, languages and a shop later without a painful migration. Zebra Hosting's WordPress hosting and shared plans run on Plesk, and you can move up to a VPS when the site grows.
