Business website information architecture defines where information belongs and how visitors reach it. List tasks such as finding a service, checking a specification or requesting a quote, then group the pages and choose navigation labels. Test whether people can find those tasks instead of copying the organisation chart into the menu.
List the jobs people need to complete
Collect customer questions from sales emails, support records and meeting notes. For each task, identify the entry point, information needed and expected destination. “Which machines do you maintain?” requires service and model information; “How do I enquire?” requires a clear contact route.
Map these tasks to a page inventory. Mark duplicates and questions without an answer. Use the main navigation for frequently needed groups, a service hub for specialist pages and contextual links for detail. Every URL does not need a top-level menu item, but important pages need a relevant route into them.
Connect service, need and sector paths through clear roles
Services can explain what you do, solutions can explain the problem addressed, and sector pages can provide context. Avoid repeating the same text under three headings. A visitor arriving through an industry page should be able to reach the relevant service, while the service page can point to useful applications.
Imagine a hypothetical technology company providing integrations, customer portals and process automation. A visitor may begin with the need to reduce operational workload but still needs to understand which services apply. The solution page can guide that choice while the service page explains delivery scope.
| Page role | Question answered | Connection |
|---|---|---|
| Service hub | What do you provide? | Relevant service details |
| Service detail | What does this engagement include? | Process, related solution and contact |
| Solution page | How can this business problem be approached? | Services addressing the need |
| Sector page | Do you understand my context? | Real sector needs and relevant services |
| Resource centre | What can I investigate further? | Relevant guides and documents |
Give people a task without explaining the menu
Give someone an outcome-based task, such as finding the scope and contact details for industrial pump maintenance. Do not tell them which menu to open. Record their first choice, backtracking and interpretation of labels; begin with a suitable person who does not already know the site.
If the same label repeatedly leads to wrong choices, revise its wording or grouping. If people reach the page but cannot find an answer, fix the content rather than the navigation. Retest the revised structure with a comparable task and check that the route remains clear in the mobile menu.
Verify how the navigation works
W3C's menu guidance addresses meaningful structure and keyboard operation for expanding navigation. Make current-page, expanded and focus states understandable. On a phone, reaching a submenu should not depend on an unclear icon or a precise gesture.
Assign responsibility for reviewing the architecture when new pages are added. Placing every request in the main menu can gradually undermine the original structure. If a page's purpose, relationship and route cannot be explained, revisit the content decision before choosing its position.