How to Plan a Small Business Website Sitemap Before You Write the Copy

BySophie Turner

Writing website copy before deciding which pages you need can lead to repeated explanations, gaps in important information and navigation that keeps growing. A sitemap gives you a plan first: what the pages are, how they fit together and what visitors should be able to do on each one.

For a small business, this does not need to be a complicated diagram or a technical document. A simple list or spreadsheet is often enough. The useful work is deciding what deserves its own page, what belongs together and how a customer will move from a question to a next step.

This guide walks through planning a small business website sitemap before you write the copy, with a worked example and a checklist you can adapt.

What a website sitemap is—and what it is not

A website sitemap is an outline of the pages on your site and the relationships between them. It can show which pages sit under others, what appears in the main navigation and where visitors can go next.

Here, “sitemap” means the planning document used to organise a website. It is different from an XML sitemap, a file that helps search engines discover URLs. You may create an XML sitemap when the site is built, but it will not decide whether your services are organised in a way customers can understand.

A sitemap is also not a promise to publish every possible page. It is a way to make deliberate choices before copy, design and development make those choices more expensive to change.

Start with the people and tasks the site needs to support

Begin with your customers’ questions, not a list of pages borrowed from a competitor. A local accountant’s clients may want to check whether the firm handles their type of tax return, understand the first appointment and ask about fees. A visitor who cannot find those answers may leave even if the site looks polished.

Write down the main types of visitor and what each one is trying to do. Keep the list short enough to be useful; a small business may have two or three important audiences rather than a dozen finely divided personas.

  • A prospective customer wants to understand the service and decide whether it is suitable.
  • An existing customer needs contact details, opening hours or help with an ongoing job.
  • A referral wants to confirm the business is credible and works in their area.

Then note the questions that matter to each group. These become evidence for pages and sections. If several customers ask about service areas, that information may need a clear place on the site. It does not automatically need a separate page for every town.

Make a page inventory before organising the menu

List the information the site needs to provide without worrying yet about the final navigation. Include existing pages if you are updating an older site, as well as essential information that is currently missing.

For each possible page, record four things: its intended visitor, the question it answers, the action it should support and whether the information is distinct enough to justify a page of its own. A spreadsheet with one row per page is a practical starting point.

Use a page purpose, not just a page name

“About” is a label, not a purpose. A useful purpose might be: “Help a first-time customer understand who runs the business, what experience is relevant and how the company approaches a project.” This makes it easier to decide what belongs on that page—and what does not.

Similarly, a Services page should help visitors compare what is offered and choose a relevant next step. If you offer several genuinely different services, separate detail pages may help. If the differences are small, one well-structured page may be clearer than a row of near-duplicate pages.

Group pages around how customers make decisions

Once you have an inventory, group related information into a simple hierarchy. A page that answers a broad question can link to more specific detail. The main navigation should expose the most useful destinations without turning into a catalogue of every page.

For example, a small home-renovation company might start with this structure:

  • Home
  • Services
    • Kitchen renovations
    • Bathroom renovations
  • Projects
  • About
  • FAQs
  • Contact

That structure makes sense if the two services involve different processes, costs or customer questions. If the business offers only one kind of renovation, a single Services page may be enough. The sitemap should reflect the real shape of the offer, not an assumption that every business needs the same pages.

Think about the next step from each page. Someone reading a project example may want to ask about a similar job. A visitor comparing services may need to understand the process or request an estimate. Links between related pages can support those journeys without making every item part of the main menu.

Decide which pages belong in the main navigation

The main navigation is a short route to the pages most visitors need. It is not a storage area for every useful URL. If it becomes crowded, consider grouping related pages under a clear label, moving supporting information into page sections or using contextual links instead.

Give menu labels a quick plain-language test: could someone unfamiliar with your business guess what they will find? “Our approach” may be meaningful to you, but “How it works” could be clearer if the page explains the steps in a project. Labels should set an accurate expectation, not sound clever at the cost of clarity.

Also plan for the mobile version. A navigation menu that fits comfortably on a wide screen may be awkward on a phone. Keeping the primary destinations focused makes both versions easier to use.

Check whether a topic needs its own page

Creating a page for every service, location or customer type can seem attractive, especially when you are thinking about search visibility. But a page is useful only if it offers distinct information and helps a visitor make a decision. Pages with nearly identical wording and only a place name changed can confuse visitors and create extra maintenance work.

Before adding a page, ask:

  • Does this audience have a meaningfully different question or need?
  • Can we provide specific, accurate information for this page?
  • Will visitors have a clear reason to land here rather than on a broader page?
  • Can we keep the information current?

If the answer is mostly no, keep the topic as a section on a broader page for now. You can split it out later if customers need more detail or the service develops into a distinct offer.

Plan URLs and page types while the structure is still flexible

Give each planned page a short, descriptive URL, such as /services/kitchen-renovations/. A clear URL helps people recognise the destination when they see or share a link. Keep names consistent and avoid building a deep hierarchy unless it genuinely helps explain the site.

It is also useful to note the likely page type. A service page, project story and contact page have different jobs, even if they share the same visual branding. Identifying these patterns early can help you reuse layouts rather than design every page from scratch.

If you are replacing an existing site, record the current URL beside the proposed page. Important old URLs may need redirects when the new site launches, particularly if they have been shared, bookmarked or linked to from elsewhere. Do not delete an established page without checking what it contains and whether visitors still rely on it.

Use the sitemap to create a copy brief

Once the structure is stable, the sitemap becomes a writing plan. Add a short brief for each page: its audience, main question, key details to include, supporting links and intended action. This prevents the Home page from carrying every message simply because it is the first page you write.

For a contact page, for instance, the brief might include the business address, service area, phone and email options, expected response times and any details a customer should provide when enquiring. The copy can then answer practical questions instead of simply saying, “Get in touch.”

Do not try to write every heading in the sitemap. The goal at this stage is to confirm coverage and relationships. You can refine page titles and wording once you know what each page needs to accomplish.

Review the sitemap before moving into design or writing

Walk through the structure as if you were a new customer. Can you find the services? Is it clear whether the business is suitable for your situation? Can you locate contact details without guessing? Are important answers buried several clicks away?

Ask someone who is not involved in the business to try a few realistic tasks using the page names alone. For example: “Find out whether we work in your area” or “See what happens after you request a quote.” This is not a formal usability study, but it can reveal labels and groupings that make sense only to people already familiar with the business.

Finally, check that every planned page has a clear purpose and an owner who can keep its information accurate. Remove pages that do not support a visitor need or business task. Add missing content only when you can explain why it matters.

A simple sitemap planning checklist

  • List the main visitor groups and the questions they need answered.
  • Inventory current and proposed pages before deciding on navigation.
  • Write a clear purpose and next step for each page.
  • Group related pages in language customers will recognise.
  • Separate topics only when they have distinct information and value.
  • Note proposed URLs and any existing URLs that may need redirects.
  • Use the approved structure as a brief for writing and page design.

A small business website sitemap does not need to be elaborate to be useful. A well-considered outline can keep the site focused, reduce duplicated copy and make it easier for visitors to find a sensible next step. Start with what people need to know, then let the page structure follow.

Frequently asked questions

How many pages should a small business website have?

There is no ideal number. Include the pages needed to explain the offer, build confidence and support useful actions. A focused site with a few well-developed pages can serve customers better than a larger site full of repetitive or outdated content.

Should every service have its own page?

Only if each service has enough distinct information to help visitors understand it and decide what to do. If the services are closely related and the differences are easy to explain together, one page with clear sections may be more useful.

Is a sitemap the same as a website menu?

No. A sitemap plans the site’s pages and their relationships. The menu is one way visitors navigate those pages. Some pages may be linked from within relevant content rather than appearing in the main menu.

Should I include a blog in the sitemap?

Include one if you have a realistic reason and capacity to publish useful, maintained articles. A blog is not essential for every business. If you do plan one, decide how it supports customer questions and who will manage older posts.

When should I make an XML sitemap?

Usually after the site’s pages and URLs are established. Many website platforms generate an XML sitemap automatically. Check that it includes the pages you want search engines to discover and excludes drafts or pages you have deliberately kept out of search results.