Strategy & Planning 5 min read

Planning your site map before design starts

The structure of a website decides how easy it is to use. How to plan it before anyone designs a page.

On this page 12 sections

Many website projects start with design: colours, fonts, a homepage mock-up. The structure, meaning which pages exist, how they are grouped and how visitors move between them, is often decided along the way. That is backwards. Structure shapes navigation, content, SEO and even the cost of the project, and it is much harder to change once pages are designed and built.

A site map, sometimes called an information architecture plan, is the blueprint for the website. This guide explains how to plan one before design begins, in a way that works for both visitors and search engines.

The short answer

To plan a site map:

  1. Start from visitors’ tasks, not your organisation chart.
  2. List the pages you need, including content you already have.
  3. Group pages into a small number of clear sections.
  4. Name sections in your customers’ words.
  5. Plan URLs and languages so the structure is consistent.
  6. Test the structure with real people before design starts.

The result is a simple diagram or list showing every page, how it is grouped and how it connects to the rest.

Why structure comes first

  • Navigation depends on it. You can’t design a menu until you know what goes in it.
  • Content planning depends on it. Each page in the map needs content, which affects timelines and cost. Our guide to planning website content picks up from here.
  • SEO depends on it. Clear sections, sensible URLs and good internal linking help search engines understand which pages matter.
  • Budget depends on it. The number and type of pages is one of the biggest drivers of a website’s price.

Step 1: start from visitors’ tasks

Write down who visits the site and what they come to do. For a service business, typical tasks include:

  • understand what you offer and whether it fits them;
  • compare options and prices;
  • check your experience and past work;
  • contact you or book a call;
  • find practical information as an existing client.

Every important task should map to a clear page or route. If a common task has no obvious home, the structure needs work.

It helps to rank the tasks. The two or three most common tasks deserve the most visible routes: a place in the main menu, a link from the home page and a clear call to action. Rarer tasks, such as finding a privacy policy or a job vacancy, can sit in the footer. Ranking tasks early stops the menu from filling up with pages that matter to the business but not to visitors.

Step 2: list the pages you need

Make a list of candidate pages from several sources:

  • your services and products;
  • questions customers ask in sales calls and emails;
  • pages on your current site that still perform well, using your analytics and Search Console;
  • legal and practical pages, such as privacy, contact and accessibility.

If you are redesigning, start with a content audit of the current site. Our guide to content audits explains how.

Step 3: group pages into sections

Group pages by what visitors are trying to do, not by how your organisation is structured. Visitors don’t care which department owns a service.

A typical service-business structure looks like this:

Section Pages
Home Overview of what you do, for whom, and the next step
Services A hub page, plus one page per main service
Work Case studies or examples
Pricing Packages, starting prices or how pricing works
About Approach, people, values
Insights Articles and guides, grouped by topic
Contact Contact options, a form, and booking

Keep the top level to around five to seven sections, and avoid going more than three levels deep for important pages.

Step 4: name sections in customers’ words

Labels such as “Solutions”, “Offerings” or “Our world” are vague. Use the words customers would type or say: “Services”, “Pricing”, “Contact”. If you have specialist services, check which terms people actually search for. Our guide to website navigation design covers labelling in detail.

Step 5: plan URLs and languages

Decide on URL patterns before pages are built:

  • short, readable, lower-case URLs, such as /services/website-redesign/;
  • folders that match sections, so the URL shows where a page sits;
  • one consistent pattern for articles, such as /insights/topic-name/.

On a multilingual site, decide early how languages are separated, usually by a folder such as /th/ or /en/, and whether every page exists in every language. Our multilingual SEO guide explains the options.

Step 6: test the structure

You don’t need a finished design to test a structure. Two simple methods:

  • Card sorting: give people the page names on cards, physical or digital, and ask them to group them in a way that makes sense. It shows how visitors expect content to be organised.
  • Tree testing: give people a task, such as “Where would you find the price of a maintenance plan?”, and ask them to find it in a text-only version of the menu. It shows whether your structure works before design hides the problems.

The Nielsen Norman Group’s introduction to tree testing explains the method. Even five to ten participants will reveal the biggest issues.

Show how pages connect

A site map is more than a list. Mark the important links between pages:

  • each service page linking to relevant case studies and pricing;
  • articles linking to the services they relate to;
  • every page offering a clear next step, usually contact.

These connections become your internal linking plan. Our guide to internal linking and site structure explains why they matter for SEO.

Common mistakes

  • Copying the old site’s structure without asking whether it still works.
  • Organising by department rather than by visitor needs.
  • Too many top-level sections, which makes the menu crowded.
  • Pages without a purpose, added because competitors have them.
  • Leaving languages to later, which leads to inconsistent structures.

Frequently asked questions

Is a site map the same as an XML sitemap?

No. A planning site map shows the structure for people and the project team. An XML sitemap is a file that lists URLs for search engines. The planning map comes first; the XML sitemap is generated from the finished site.

How detailed should the site map be?

Detailed enough to list every page and its section. For each page, a one-line purpose and its main call to action are helpful. Design details come later.

Who should be involved in planning the structure?

The decision-maker, someone who talks to customers regularly, and the website designer or developer. Testing with a few real customers adds an outside view.

What to do next

List the five tasks visitors most often come to your site to do, then sketch the sections and pages that serve them. Test the result with a few customers before any design work starts.

Our website design and development projects start with discovery and a site map, so design builds on an agreed structure. If you are rebuilding an existing site, our website redesign service begins with an audit of what you have.

Written by the PORVIX team

The people who design, build and maintain websites for growing businesses. We write about the questions that come up on real projects, in plain language, and update articles when the advice changes.

Published

How we work

Is your current site costing you enquiries?

A free, plain-language audit, by email within 2 business days.

Get a free audit
Get a free audit

Keep reading

More plain-language guides.

More on strategy and planning first, then other guides worth reading next.

All insights

Start here

Let’s build a website that brings in business.

Tell us about your project. You’ll hear back from a real person within one business day, with honest advice either way.

  • Free consultation
  • Fixed written quote
  • Your details stay private