Website relaunch – a defined task
Website relaunch: Develop information architecture from user journeys
This section focuses on the structure of the new website: What page types are needed, how are they related, and what paths do different users take to reach their next relevant decision?
The focus is on hierarchy, navigation, page roles, naming conventions, and URL logic. Individual texts are developed only afterward; simply renaming old menu items does not constitute a new information architecture.
Classify the relaunchDedicated workspace for this URL
Group tasks
Related user questions are grouped into easily understandable sections. The company's internal organization is only relevant if it also explains the expected user journey.
Define Page Types
Overviews, detail pages, guides, and entry pages are assigned different roles. This separation prevents a single page from simultaneously providing orientation, a complete explanation, and a conclusion.
Test Pathways
The structure is tested with concrete entry points: direct product need, comparison, problem-solving, or existing customer relationship. Each path must lead to a suitable next action.
Test sequence for this relaunch component
Collect User Questions – A list of real orientation needs is created from search queries, sales questions, and service cases. This forms the basis for sections and page roles.
Define Terms Clearly – Navigation items use words that describe the expected content. Internal abbreviations or historically established categories are not adopted without review.
Limit Hierarchy – A level is only created if it meaningfully organizes multiple content areas. Unnecessary intermediate pages lengthen the navigation path; conversely, overly shallow collections hinder comparison and orientation.
Plan Cross-Connections – Users do not navigate exclusively via the main menu. Therefore, appropriate connections between services, examples, knowledge, and contact options are defined as part of the architecture.
Test Structure Before Layout – Page names and paths can be tested as a sitemap or simple click sequence. Only when the logic is clear is it implemented in navigation and page design.
Questions from Project Preparation
What is the concrete result of an information architecture?
The result is a well-founded sitemap with clearly named sections, defined page types, comprehensible hierarchies, and planned connections between related content.
Is the information architecture the same as the main menu?
No. The menu is just a visible access point. The architecture also includes page roles, URL structure, content relationships, and paths created via internal links or thematic entry points.
When should the new structure be tested?
It should be tested before detailed design and before all text is written. This allows unclear terms or missing page roles to be corrected without having to revert to a completed implementation.
How are different target groups taken into account?
Not every target group needs its own main section. The crucial factor is whether the tasks, information requirements, or next steps differ. Only then is a separate path within the architecture justified.
What happens to the old sitemap?
It serves as an inventory source, but not as an automatic template. Every existing element is checked against future user paths and page roles before it is adopted, moved, or deleted.
Suitable basis for the request
The existing sitemap, known user groups, and the most important tasks that visitors should complete on the new website are sufficient as starting material.