Have you ever stopped to think about why we say we “build” websites?

Traditionally, when we think of building something, we have very physical connotations. A hammer, some nails, and a little glue, and a bit of wood can become a birdhouse by the process of building.

On a larger scale, building a home involves gathering what the home’s residents will want, creating blueprints and mockups, and then getting to the physical acts of laying the foundation and building from there.

Building a website works the same way: gathering information, creating a sitemap, designing, then developing from a foundation up.

For every website we build, the sitemap is the blueprint. It has three main purposes:

  • Organize and clarify a website’s content.
  • Make sure all the necessary information has a home.
  • Eliminate unnecessary content.

A sitemap is usually displayed visually as a hierarchical chart, like this one:

Example of how to create a sitemap for a website, showing PHOS Creative’s site structure with main navigation pages, organized subpages, and footer links in a visual hierarchy.

You may also hear the term sitemap used in another context. It can also refer to an SEO tool that collects and displays pages hierarchically for a search engine to crawl. For our purposes here, we’ll refer to a sitemap as the initial content planning tool, sometimes called content architecture.

In this article, we’ll go over everything you need to know about how we think about, talk about, and create a sitemap.

Sitemap Terms to Know

  • Parent/child: for anything but a very basic website, pages will be organized in a hierarchy. The top-level page is called a parent, while the one below it is called its child.
  • Grandchild: in more complex websites, there may be a third level to the content hierarchy. A page underneath a child is called a grandchild.
  • Ancestor: in more complex websites (typically four or more levels), the top-level page is often referred to as an ancestor for clarity.
  • Masthead: a bar sometimes used above the header to provide extra navigation to important content.

Who Should Create the Sitemap?

If you’re working with an agency, you’ll likely have four main categories of people you’ll work with:

  • A project manager (sometimes called account executive)
  • A content lead (along with a content team)
  • The design team
  • The development team

The sitemap is under the domain of both content and user experience. The content lead will usually take primary responsibility for creating the sitemap, with input from the lead project designer.

Of course, the client has the final say. A good agency will walk you through the sitemap, knowing that you understand your business better than anyone.

How to Create a Sitemap

Step 1: Map Out Existing Content

Before creating a new sitemap, it may be helpful to map out the existing content structure.

At PHOS, we use a powerful tool called Slickplan, where we map out content, notate important features, plan what content lives on a page, and more (but we’ll get to all that later).

We will always begin by mapping out the organization of the old website. This helps us get an idea of what content exists, which can then be matched with analytics data to decipher how users navigate the old site – and where the content structure is failing them.

Here’s what we typically find:

Lack of Clear Planning

Many businesses simply have never put any thought into how users navigate their website. A semi-common symptom of a failure to plan is having a ton of links in the navigation with no content architecture at all.

An Overgrown Sitemap

As businesses grow, websites tend to grow. That’s a good thing! But even with good up-front planning, a website’s navigation can quickly get out of hand.

Often, different departments each want to add pages for different subcategories of content that they think merit their own home. That, and everybody wants to be on the homepage.

The result is the shell of a once beautifully-planned structure that’s been bogged down by more and more content placed in the wrong spots by people with entirely good intentions.

For one website we launched recently, the client came to us with stories about how each department had free reign over the website. Over the years, it grew into a disorganized array of poorly-thought-out content that became almost impossible to navigate.

When they came to us, the website had over 1000 pages. After the entire sitemap process, we were able to determine just 300 pages that were the right content to be on the site, in a clearly organized and easy-to-navigate content architecture.

Hidden Pages

Do you know about the hidden pages on your site?

Yes, really. There may be pages you didn’t even know about on your website (the same pages from the situation above) – or pages you know about, but didn’t know were hidden.

We’ll sometimes find that not every page is easy to find. Either it’s not linked in the navigation, or it’s only linked to by one obscure link on a particular page, or it’s not linked at all.

The solution is to rely on more than just the navigation. When we’re mapping out existing content, we use the main navigation, but we also look at each page for links, and crawl the website to find any hard-to-reach pages.

Step 2: Define User Personas and Goals

The next step is always to define and record user personas, their goals on the website, and the client’s goals for each user persona.

Note: This step is arguably more important than mapping existing content. I still prefer to do the mapping first, because it helps define each persona’s goals. If a page gets a lot of traffic, that tells you users expect to reach that content easily.

For each persona, decide which content matters most to them. Ask yourself:

  • Why are they visiting the website?
  • When they see a basic description of the company, what do they want to know next?
  • What questions do they have about the company, its products/services, or its industry?
  • How does the user need to engage with the company (purchasing, contacting, reading, attending, subscribing, requesting, etc.)
 
 

Remember: It doesn’t matter how much the content organization makes sense to our team or yours. What matters is how much it makes sense to the user.

 

Step 3: Begin the New Sitemap

Finally, about 1000 words later, we’re ready to begin the new sitemap.

This may mean beginning by reorganizing the existing content, or starting from scratch if necessary.

Before getting into too much detail, it’s important to save the new sitemap as a new version in Slickplan.

Top: tUse version control generously throughout the process. Save a new version whenever you change direction on part or all of the sitemap, and whenever your team or client gives feedback. This lets you go back to earlier versions and compare different approaches. 

Parents and Children

Start with the top-level parent pages. Use your user goals, priority content, and existing content to group information into easy-to-follow categories. Then plan the pages that belong in each category.

This parent-and-child structure is also the foundation of a strong SEO strategy. When related pages are grouped under a clear parent, both users and search engines can tell what each section is about. We explain how this works in our article on content clusters.

Avoid Duplicate Content

Duplicate content comes in two forms: first, if content from one page is very similar to another without important distinguishing factors, combine the pages.

Second, one page may be in multiple spots on the sitemap. It’s sometimes ok to have one page under multiple parents, especially in a complex website. This may be necessary if users expect to find the content under both parents.

When this is the case, make sure you have the right parents (are the content categories distinct enough?) and notate that they are the same page somehow. In Slickplan, an easy way to do this is by changing the color so the duplicates match each other.

Decide How Top-Level Pages Work

Here’s an interesting question: why is the first child page sometimes the same as its parent?

On some sites, you want users to click a top-level menu item and land on a real page. But you don’t want them to see a dropdown, jump straight to a child page, and miss important content on the parent. Repeating the parent as the first child solves that.

This is more common on small to medium-sized websites, usually with fewer than eight pages under any given parent.

It’s partly strategy and partly preference. If you want users to dive straight into specific content, the top-level menu items may not be pages at all, just category labels for the pages underneath.

Plan the Masthead and Footer

Use the masthead space to add pages (or external links) that are particularly important. These will typically be more action-based, potentially even direct calls to action. If the website requires a search function, this is typically a natural place to include it.

The footer varies widely. It may include important forms of engagement such as a link to the contact page or a list of resources. It may also mirror content from the masthead or links to the parent pages.

Note: footers often hold information like an address or phone number. Those are important for user experience, but they aren’t part of the content organization, so you don’t need them in the sitemap.

Step 4: Notate Functionality

Notation is one of the most important ways to increase efficiency and collaboration between the content planning stage or a website and design and development stages. Notate pages that will have special design considerations or functionality. Some examples include:

  • Image galleries
  • Pages centered around a form
  • Portfolio pages
  • Team pages
  • Calendar page
  • Videos pages
  • Articles
  • Interactive pages
 
 

The more specific a sitemap is, the easier it will be to communicate with designers and developers how a specific page or set of pages is supposed to look or function.

 

Step 5: Write Your Page Content

Once the sitemap structure is finalized, start writing the actual content for each page directly in Slickplan’s Content Planner. Each page in the sitemap has its own content area, where you can draft headings, body copy, and calls to action, and attach images or files.

Writing content inside the sitemap keeps every page tied to its place in the structure. Your team, designers, and developers can see exactly what each page will say before design begins, and it’s easy to spot pages that are thin, overlapping, or missing.

When content is finalized, it can be exported or migrated into the website build, so nothing gets lost between planning and launch.

Step 6: Gather Feedback and Suggestions

Before the sitemap goes to design and development, get feedback from the team, especially the lead designer, along with anyone else important to the project. A missing page, a confusing category, or a feature nobody planned for is easy to fix in the sitemap. It’s much harder and more expensive to fix once pages are designed or built.

Once the sitemap is created, finalized, and approved, you have your blueprint! Now it’s time to design the house, lay the foundation, and start building.

Sitemap FAQs

What’s the difference between a sitemap and an XML sitemap?

A sitemap like the one in this article is a planning tool. It organizes your content before the website is designed. An XML sitemap is a file on a live website that lists its URLs so search engines can find and crawl them. WordPress generates a basic XML sitemap automatically, and SEO plugins can create more detailed ones. You need both: one to plan the site, and one to help search engines index it once it’s live.

How many pages should my website have?

There’s no magic number. A website should have as many pages as your users need and no more. That’s why defining user goals comes before building the sitemap: every page should help a specific user do something specific. As the 1,000-page example above shows, more pages often make a site harder to use.

What tools can I use to create a sitemap?

We use Slickplan because it combines visual mapping, notes, content planning, and version history in one place. Other teams use whiteboarding tools or even a simple spreadsheet. The tool matters less than the thinking behind it.

Does a sitemap affect SEO?

Yes, indirectly. A clear content structure helps search engines understand what each section of your site is about and how your pages relate to each other. It also makes it easier for users to find what they need, which keeps them on your site longer. Planning your structure up front is one of the most effective things you can do for long-term search engine optimization.

Planning a New Website?

A sitemap is the first step in every website we build. If you’re ready to plan a site that’s organized around your users, from discovery and sitemap through design and launch, see how our web design and development process works.

Anna Golubykh

Anna approaches search marketing at the intersection of data, empathy, and innovation. Grounded in customer-centric strategy and the Jobs-To-Be-Done framework, she blends deep industry research with emerging tools to craft strategies that resonate. She doesn’t just optimize for search engines — she optimizes for people. For Anna, great marketing starts with uncovering a brand’s core truth and translating it into a digital presence that drives sustainable growth and authentic connection.When she’s not fine-tuning SEO roadmaps or mapping user journeys, Anna finds joy in paddling Florida’s hidden springs, hosting game nights with friends, or getting lost in a museum or symphony hall. She’s an energetic, open-minded adventurer — the kind of friend who always says “yes” to a spontaneous idea. With travels across more than 20 countries and 6 U.S. states, Anna is constantly seeking out new cultures, fresh perspectives, and meaningful experiences.