The process of defining the complete list of pages a website will contain, how they are grouped and named, how they relate to each other hierarchically, and how users and search engines will navigate between them — before any design or development begins.
A sitemap defines the scope and architecture of the project. Starting design without a defined page list leads to scope creep, inconsistent navigation design and structural revisions mid-project. The sitemap is the foundation on which every subsequent decision is built.
A visual sitemap is a planning document — a diagram showing the page hierarchy and navigation structure used in the design and development process. An XML sitemap is a technical file submitted to search engines to help them crawl and index the finished site.
By mapping every service, product or content category the business needs to represent, considering the user journeys different audience types will take, assessing the SEO keyword opportunities for each topic area and reviewing competitor sites for structural benchmarking.
Defining the logical path structure for each page (e.g., /services/category/specific-service) that is descriptive, consistent, SEO-friendly and scalable as the site grows. URL structure affects search engine rankings and user navigation, and changing it later requires redirects.
An orphan page is one with no navigation path leading to it. If a page is planned in the sitemap but not linked from the navigation or other pages, it may be missed by both users and search engines. All pages in the sitemap should have at least one defined navigation path.
By defining page templates — standardised layouts that serve the same function across multiple similar pages (e.g., service page template, team member template) — so the design and build process creates a template once and populates it many times rather than building each page individually.
Primary navigation contains the most important destination categories, typically displayed in the main menu. Secondary navigation (footer links, sidebar menus, utility nav) handles less frequently visited pages. Sitemap planning should define which pages belong in each navigation zone.
A logical hierarchy signals content importance to search engines (pages closer to the home page receive more ranking authority), enables effective internal linking and ensures every important page is reachable within three clicks from the homepage — a widely accepted accessibility and crawlability standard.
Yes, but changes after design has begun can be costly. Minor additions may be straightforward; structural changes that affect navigation design or template scope require revision of completed work. Thorough planning reduces mid-project structural changes significantly.
