Design & usability

Building a Website Sitemap Around Customer Questions

The first sitemap is often a list of pages copied from competitors. A more useful approach starts with customer questions and the decisions those questions support. A Website Developer Jakarta team can then plan navigation that reflects the business offer without reproducing its internal organisational chart.

By Web Developer JakartaPrepared 21 October 20262 min read
Project notes and planning papers arranged on a board.
Project notes and planning papers arranged on a board. Photo: Tima Miroshnichenko / Pexels. Illustrative stock photo.
On this page
  1. Group by the task the visitor recognises
  2. Choose when a separate page is justified
  3. Design relationships as well as menus
  4. An illustrative business scenario
  5. A practical checklist
  6. Questions about this topic

THE DIRECT ANSWER

An information sitemap groups content by visitor needs and shows how important pages relate. It is a planning tool for navigation and content, distinct from an XML sitemap used to list URLs for search engines.

Group by the task the visitor recognises

Collect real enquiry themes and arrange them into understandable groups. A customer may recognise installation or maintenance but not an internal department abbreviation. Use labels that make sense before the visitor has learned how the company is structured.

Choose when a separate page is justified

Create a page when it has a distinct purpose and enough useful information to answer a different question. Avoid separate pages that only change a location or repeat the same description. If two proposed pages cannot be explained differently, consider combining them.

Design relationships as well as menus

Not every important connection belongs in the main navigation. A service page can link to a relevant project, an article can explain a technical term, and a product can lead to an enquiry. Map those relationships so visitors can continue without returning to the homepage each time.

An illustrative business scenario

A business serving both procurement teams and homeowners may share company information but need different service explanations. The sitemap can show those paths explicitly while keeping contact details and brand information consistent across the site.

A practical checklist

  • Collect recurring customer questions.
  • Use labels visitors already understand.
  • Give each proposed page a purpose.
  • Map useful contextual links.

Questions about this topic

How many menu items should a website have?

Use the number needed to make key choices understandable. Test the labels and grouping rather than forcing every business into a fixed count.

Is this the same as sitemap.xml?

No. This sitemap plans information relationships; an XML sitemap lists selected URLs for search-engine discovery.

Plan your next website step.

Discuss your business, the visitor journey, and the work you need with Web Developer Jakarta. A short brief can help start a useful conversation.

Discuss Your Website ↗
← All articles