How to plan a website’s structure around customer tasks
A website’s structure is the path between the visitor’s question and the answer that lets them proceed. A beautiful menu loses value if people cannot find a service. Start with tasks, organise pages that resolve them and test that map before investing in the complete visual composition.
By the end, you can:
- Separate pages according to real decisions
- Build menus and contextual links
- Check journeys before designing everything
Gather tasks and possible entry points
Write what people need to do: check whether you provide a particular service, compare options, understand terms, view work or request information. Collect real questions from the team and support channels. If you do not yet have that history, label hypotheses as hypotheses and test them; do not turn an imagined list into completed customer research.
Also record where each journey may begin. A visitor may land directly on a guide, product or form without passing through the homepage. Every important page should explain enough context and offer a next step. Design the architecture for those side entrances: the homepage is one door, not the only way into the website.
Give each page a responsibility
Group tasks using the same information and leading to a similar decision. Separate pages when services, terms or questions differ enough. A short section may suffice for a simple variant; an offer with its own process, materials and criteria may justify a page. The final number should come from content, not an arbitrary page package.
Create an inventory with a provisional name, question answered, materials, owner and next action. Two different names may hide the same function: “Solutions” and “Services” need an understandable distinction. If nobody can explain it, simplify. A page without its own content or a connection to the journey deserves review before being added to the menu.
| Question | Possible page | What it needs to contain |
|---|---|---|
| Does this company solve my problem? | Service | Scope, process and suitability criteria |
| How does the work happen? | Process or service section | Stages, responsibilities and approval |
| What information should I send? | Contact or request | Necessary fields and request destination |
| How do I prepare materials? | Guide | Steps, example and reusable worksheet |
Example: a fictitious maintenance company
Fictitious company Ponto Norte provides preventive maintenance and corrective interventions. Visitors need to understand the difference before requesting an assessment. The map includes a services page presenting both options, a page for each option, a process section and a form preserving the chosen service. A guide to preparing a visit helps those still organising information.
In the example, “Corrective intervention” does not promise an immediate response: availability will be confirmed by the team. Navigation shows “Services”, “How we work”, “Guides” and “Contact”. Service pages link directly to the corresponding request. This relationship matters more than putting every address in the main menu; readers find the next stage beside the information they have just consulted.
- Services
Compare preventive and corrective maintenance.
- Chosen service
Understand scope, materials and process.
- Preparation
Gather information to assess the request.
- Contact
Send context to the right owner.
Organise the inside of the page too
Each page has an internal structure: heading, sections, lists, tables, actions and footer. Headings should describe their section’s subject and form a coherent hierarchy. Visual size must not be the only criterion for choosing a heading level. Regions and semantic elements help distinguish navigation, main content and complementary information.
Try reading only headings and button names. Is the journey still understandable? Then move through the page with a keyboard and check that focus order follows the expected order. Visually rearranged content may remain in a different sequence for assisted reading. The map should guide composition and implementation, especially when desktop columns become a single column on mobile.
Test tasks without explaining the menu
Show the structure to someone uninvolved in the project and give a specific task: “You want to confirm what to prepare before requesting preventive maintenance”. Observe where they start, hesitate and which destination they choose. Do not name the expected page. A simple drawing with links already permits this test; photographs and animations need not be finalised to discover a confusing label.
Record the task, chosen path, questions and result. If two people interpret a label differently, investigate the word and grouping. Common errors include organising the menu around the internal organisation chart, creating empty categories, hiding contact details in a submenu and duplicating pages with small differences. Correct one hypothesis at a time and repeat the affected journey. The test informs decisions without claiming to prove commercial results.
Deliver a map the team can carry out
Approve the inventory and main journeys together. Every page should have an owner, planned materials and next destination. Keep decisions to merge or remove pages so the map does not grow again without criteria. During development, use the worksheet to confirm the implementation still answers the original task, including direct entries from search.
Worksheet for your project
Audience and priority task: Possible website entry points: Page / question answered / next step: Available and missing materials: Owner of each page: Main menu and reason for each option: Contextual links needed: New, retained and changed addresses: Task used in the test: Observed path and questions: Chosen change and new test: Map approval criterion:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
