Skip to main content Scroll Top

Build Week 2: Sitemap, Content Plan and Wireframes

In the second stage of our Build Week series, the conversation moves from what the business wants to how the website will be organized. This is the stage where the project gets its skeleton. It is far cheaper to rearrange a skeleton than to rebuild a finished body, so this week deserves careful attention.

Building the sitemap

A sitemap, in this sense, is a simple outline of every page the website will have and how they relate to each other. It might look like a tree diagram or a nested list. The goal is to decide what pages exist, what they are called and how visitors move between them.

Good sitemaps are shaped by the goals and audiences identified in week one. If most visitors come to book an appointment, booking should be easy to reach from everywhere. If the business offers several distinct services, each may deserve its own page. If the old site had pages that nobody visited and nobody misses, this is a chance to retire them.

Advertisement

Planning the content

Alongside the sitemap, the team usually creates a content plan. For each page, it notes:

  • The purpose of the page and the main action a visitor should take.
  • What content it needs: text, photos, videos, forms, testimonials or downloads.
  • Whether that content already exists, needs updating or must be written from scratch.
  • Who is responsible for providing or writing it, and by when.

Content is the most common reason website projects slow down. Identifying gaps now, rather than after design is done, gives everyone time to fill them.

Sketching wireframes

Wireframes are simple layouts that show what goes where on a page, without colors, photos or final styling. They often look like gray boxes and placeholder text. That plainness is deliberate. It keeps the discussion focused on structure and priority instead of whether a particular shade of blue is right.

Wireframes are usually made for the most important or most complex pages: the homepage, a typical service or product page, a contact or booking page and any page with unusual features. Many teams sketch phone layouts alongside desktop ones, since a large share of visitors will be on a small screen.

Giving useful feedback

This week asks the business to review the sitemap and wireframes. The most helpful feedback at this stage focuses on substance:

Advertisement
  • Is anything missing that customers regularly look for?
  • Does the order of sections on each page match what matters most?
  • Are page names in language customers would actually use?
  • Is any page or section unnecessary?

Save comments about colors, fonts and imagery for the design stage. They matter a great deal, just not yet.

Leaving week two

By the end of this stage, there should be an approved sitemap, a content plan with owners and deadlines, and wireframes that everyone agrees reflect the priorities of each page. With the structure settled, Build Week 3 turns to visual design.

A Sitemap Example for a Small Service Business

To make the idea concrete, here is what a simple sitemap might look like for a local business that offers a few distinct services and takes appointments:

  • Home
  • Services
    • Service one
    • Service two
    • Service three
  • About
    • Our team
  • Book an appointment
  • Frequently asked questions
  • Contact
  • Policy pages, such as privacy, terms and accessibility, usually linked in the footer

Notice what is not there: no separate page for every minor topic, no page that exists only because the old site had one. Each page earns its place by serving a goal or answering a real question. A business with more services, multiple locations or an online store will have a larger tree, but the same test applies.

Naming Pages and Menu Items

The words in your menu are some of the most read words on your website. Small choices here make a real difference.

  • Use the customer’s words. If customers ask about prices, a menu item called Investment may not register. If they say repairs, do not call it Solutions.
  • Keep menu items short. One or two words each, where possible, especially on phones.
  • Limit the top level. A main menu with a handful of clear choices is easier to scan than a long row of options. Secondary pages can live under a parent or in the footer.
  • Make the main action obvious. If booking or requesting a quote is the goal, it often deserves a distinct button rather than being one menu item among many.

Writing a Content Brief for Each Page

A content plan becomes much easier to act on when each page gets a short brief. Whoever writes the page, whether a staff member or a hired writer, can work from it. A useful brief answers:

  1. Who is this page for?
  2. What question brought them here?
  3. What do they need to know to take the next step?
  4. What is the next step, and where is the button for it?
  5. What proof or reassurance helps, such as photos of real work, credentials or a clear explanation of the process?
  6. What should this page leave out because it belongs somewhere else?

Briefs keep pages focused. They also make content review faster, because reviewers can check whether the page does what the brief promised.

Mistakes to Avoid at This Stage

  • Copying the old site’s structure by default. The old menu may reflect how the business was organized years ago, not how customers look for things today.
  • Organizing by internal departments. Visitors do not usually care how your team is divided. They care about what they need.
  • Leaving content ownership vague. A content plan with no names and dates beside each item tends to stall. Assign every gap to a person.
  • Approving wireframes without reading them on a phone layout. The order of sections on a narrow screen can change how a page feels. Review both versions.
  • Skipping the old site’s addresses. If the site is being replaced, note now which existing pages will move or disappear, so redirects can be planned later.

Questions Owners Ask

Can we add pages later?

Yes. A good structure leaves room to grow. It is usually easier to launch with fewer, stronger pages and add more once you see what visitors use than to launch with many thin ones.

Why do wireframes matter if the design will change everything?

Design changes how a page looks, not what it contains or the order of priorities. Agreeing on that structure first keeps the design stage focused on the visual layer.

Our clients