A website's structure is one of the most important things about it, and yet planning it (sometimes called content strategy or information architecture) is often skipped. It's easy to assume the developer will sort out what goes where. Unless the site is only a few pages, that's only partly true.

Why it matters

When a site's structure is well planned:

  • Visitors find their way easily. They find what they came for, and the things you wanted them to see.
  • The site does better in search, because each page has a clear topic.
  • People stay. Confusion is the quickest way to lose a visitor.
  • The site actually does what you built it to do.

When the structure is cobbled together in a rush, you lose most of that.

Who should plan it

Ideally, planning happens before development starts. You can do it yourself and bring it to your developer, work with a marketing or content specialist, or work it through together with your developer. Whoever leads it, the developer should be involved early, because how a site is structured affects how it's built.

Here's roughly how it goes.

Step 1: Research

This is the most important step. Work out the words and phrases your customers type into search boxes, and use them to shape the site's pages and content. Look at your competitors too: who ranks well, which words they use, and how their sites are laid out. To find them, search for your own products and services the way a customer would.

Step 2: Draft the core pages

Start with the pages every site needs. Something like:

  • Home
  • About
  • Services, with a page for each service
  • Contact

That covers the essentials: a starting point, what you offer, who you are, and how to get in touch. A shop will add products, a cart and a checkout. For some businesses, this is all you need.

Step 3: Add what's left

Map your keywords onto those pages, and see what's left without a home. Common additions:

  • Privacy policy and terms
  • A login or account area
  • Articles, which are good for covering extra search terms and keeping the site fresh
  • FAQs
  • Specific forms, such as a quote request or a callback request

Step 4: Design and build

Now the draft goes to design and development. Expect suggestions: how a page is meant to work often changes where it should sit.

Step 5: Review and launch

Before launch, try the site on a staging copy. Check that what was in your head made it onto the screen, and that it works for your customers. Make the last structural changes, then go live.