A planning sitemap and wireframes let the team agree what a website must contain before investing in detailed styling. They solve different questions: the sitemap organises pages, while wireframes organise information and actions within representative pages. Use them to expose missing content and conflicting expectations early.
This guide covers page inventory, customer journeys, representative layouts and content-decision ownership. Discuss the relevant requirements through ITZ’s Website Design service.
Page and content inventory
List required pages and the purpose of each. Identify existing content to retain, material to create and pages that need distinct templates. Separate a planning sitemap from the XML sitemap used for search discovery.
List existing pages, proposed pages and the unique purpose of each. Mark content to keep, combine, replace or retire, with a decision owner. Distinguish this planning document from an XML sitemap used for search discovery. Google's sitemap guidance describes the latter's technical role; it does not decide which services your customers need to understand.
User journeys
Map how visitors find services, compare information and contact the business. Include relevant language, device and accessibility requirements so that navigation supports actual tasks.
Map a few important journeys from arrival through evaluation to the next action. Include language, branch and device requirements where relevant. A page list alone does not show whether a visitor can complete a task. Walk through the proposed paths with staff who receive customer enquiries and can identify questions the structure overlooks.
Plan Your Sitemap and Wireframes to discuss page inventory, customer journeys, representative layouts and content-decision ownership.
Wireframe review
Use simple layouts to assess content order, key controls and page relationships. Confirm mobile priorities and representative desktop behaviour before investing in detailed visual styling.
Use low-detail layouts containing realistic headings, sample copy and controls. Review mobile priorities before decorative detail distracts the discussion. A wireframe should show what matters and what depends on user input, including empty or error states for important functions. It need not imitate a finished visual design to reveal that the information order is wrong.
Design handover
Record the approved structure, required content and outstanding decisions. The visual design and development stages should use these requirements as a reference, with changes reviewed for their effect on scope.
Record approved structure, content responsibilities and unresolved questions. Explain the impact of later changes on templates, navigation and content work. A template can accelerate delivery once its suitability is assessed; it cannot replace deciding what the page should communicate. Keep the planning artefacts current enough to guide implementation rather than treating them as an abandoned workshop output.
A practical example
Illustrative example: a team approves a visual homepage, then discovers that customers must choose a branch before seeing service availability. A simple journey map and mobile wireframe could expose that dependency earlier, allowing the team to resolve the content model before polishing a layout that assumes the opposite order.
Your review checklist
- Give each page a distinct purpose and content owner.
- Walk through representative customer journeys.
- Review realistic mobile layouts and important interaction states.
- Record approvals and the effect of subsequent scope changes.
Frequently asked questions
Can an existing template replace wireframe planning?
A template can accelerate implementation, but it does not establish the required content or user journeys. Review its suitability against the business requirements before adoption.
References and further reading
Related services and guides
Discuss the next step
Plan Your Sitemap and Wireframes. Use the form below to discuss page inventory, customer journeys, representative layouts and content-decision ownership. Share the relevant goals and existing arrangements; do not include passwords, private records or access tokens.
Plan Your Sitemap and Wireframes ↗
Reviewed and expanded on 15 October 2026. Examples are illustrative; the appropriate approach depends on your business requirements and existing systems.
