Skip to content

Arquitectura web

What Is a Sitemap, and Why Is It Defined Before Design Starts?

Equipo Artisma

Agencia de Marketing B2B

7 min read
¿Qué es un mapa de sitio y por qué se define antes de empezar a diseñar?

The company distributed industrial refrigeration equipment and wanted a website that showed its full catalog. The designer presented a home page that everyone liked, and with that approval, development began. Three weeks later, the sales manager asked for each product line to have its own section, with downloadable spec sheets and a separate form for spare parts.

The new sections caught everyone off guard. The menu as designed had five options and now needed twelve. The pages already built had nowhere to hang, and the single form that had been programmed could not tell a request for new equipment from a request for spare parts. The project stopped so everything could be reorganized, and the launch date slipped by two months.

When the website finally went live, buyers looking for a specific spare part still could not find it from the home page. The catalog was there, but the path to each product had been decided on the fly, and it showed.

A sitemap is the outline of every page on your website and how the pages connect to one another. It is defined before design because the menu, the forms and the buyer's paths all depend on it.

Designing without a sitemap means rebuilding the website every time a new page appears

A sitemap is a simple document: a hierarchical list of every page the website will have, with the name of each one, its level in the menu and how it relates to the others. It resembles a company's org chart, with the home page at the top and the sections, subsections and detail pages hanging below it. It is worth telling it apart from the XML file submitted to search engines, which shares the name and serves a different purpose. Here we are talking about the map you draw to plan the website.

Structure holds up the design, and design cannot hold up the structure

A design is the visual form of a structure. The main menu shows the top-level sections, the cards on the home page lead to the most important sections and the footer gathers the secondary paths. If the structure changes after design, all of those pieces change with it: a five-option menu is built differently from a twelve-option one, and a home page meant to send traffic to three sections becomes confusing when it has to send it to eight.

That is why the sitemap comes first. When the designer receives the approved sitemap, they know how many templates are needed, how deep the menu goes and which type of page deserves the most attention. Without the sitemap, they design an assumption, and every later correction is paid for in hours of redesign and reprogramming.

What the sitemap decides before a single screen exists

A well-built sitemap answers questions that would otherwise be settled late and at a higher cost. These are the decisions it locks in.

How many pages there will be and which template each one needs

Listing every page reveals the content types that repeat: product sheets, service pages, case studies, blog articles, branch pages. Each type is designed once as a template and reused. A sitemap with forty pages may need only six templates, and that count defines the real scope of the project, its timeline and its price.

Which section answers each way your buyers search

Buyers of an industrial company reach the website by different routes. One is looking for a technical capability, another for an industry served, another for a service and another wants to know where the nearest plant is. The sitemap decides whether the website is organized by product, by industry, by the problem it solves or by a combination, and that decision determines whether buyers find what they need in two clicks or give up.

How deep each page sits and how many clicks it takes to get there

Each level of the sitemap adds a click. A product sheet sitting at the fourth level gets fewer visits than one at the second, and search engines also treat it as less important. The sitemap lets you see that depth before anything is built and bring the pages that sell the most closer to the surface.

Where the forms go and what each one asks

A B2B website usually needs more than one form: a quote for new equipment, a spare parts request, technical support, job openings. Each one asks for different information and reaches a different person. The sitemap shows which pages carry each form and where it is sent, and that detail prevents the single form that mixes purchase requests with warranty complaints.

What address each page will have from day one

With the sitemap approved, you define each page's address, the names shown in the menu and the words a buyer would use to search for each section. Those addresses stay in place for years and appear in quotes, spec sheets and emails. Changing them after launch means setting up redirects and watching that your rankings hold.

How to build the sitemap for a company that sells to other companies

The sitemap is built from information that already exists in your company, and putting it together takes days rather than weeks. This is the process we follow.

  • Inventory of what exists. Every page on the current website is listed with its visits and rankings, to decide what to keep, what to merge and what to retire.

  • Interview with sales. The sales team explains how a buyer asks, which documents they request before a quote and which questions come up on every call.

  • List of real searches. We review the words your buyers use to look for products and services like yours, so each section has a name someone would actually type into a search engine.

  • Grouping and hierarchy. Pages are grouped by the criterion that best serves the buyer and each one is assigned its level, with a maximum of three clicks from the home page for the pages that sell.

  • Validation with decision makers. Management, sales and marketing review the sitemap in a single session and approve names, levels and forms before anyone opens the design software.

The result fits on a single page and becomes the project's reference document. Every screen designed afterward corresponds to a page on the sitemap, and every new page that comes up during development is evaluated against it.

Signs that your current website was built without a sitemap

If your website already exists, you can spot a missing sitemap in a few minutes. A menu with more than seven top-level options suggests that sections were added without a hierarchy. Two pages covering the same service under different names show that nobody decided which one was the main page. A single form for every type of request, pages you can reach only through a link buried in the footer and key products four clicks from the home page complete the picture.

In most cases, those signs can be fixed without rebuilding the website. Redrawing the sitemap and rearranging the existing pages restores clarity without changing the design.

At Artisma, the sitemap is the first deliverable of every web project, and it is approved before the design team opens a single screen. We build it with your sales team, with your buyers' real searches and with the history of your current website, so every section has a purpose and a clear path. From the sitemap, we define the templates, the forms and the addresses you will keep for years.

Frequently Asked Questions

Is a sitemap the same as the XML sitemap submitted to Google?

They share a name and little else. The sitemap we discuss here is a planning document drawn before design, and it shows the page hierarchy to the people building the website. The XML sitemap is a technical file generated once the website exists, and it tells search engines which addresses to crawl. The first one gives rise to the second.

How many levels deep should my company's website go?

The pages that sell, such as product sheets and services, should sit no more than three clicks from the home page. The rest of the content, such as articles, legal notices or support documents, can go deeper without any problem. More than a fixed number, what matters is that buyers find what they are looking for without having to guess which section it was filed under.

What happens if a page that was not on the sitemap comes up during the project?

It is normal for one or two to appear. The approved sitemap helps you place them with clear criteria: you decide which section they belong to, which template they use and whether they displace another page. What the sitemap prevents is every new page being added to the menu without any order. If many appear, it is worth pausing to check whether the initial inventory was incomplete.

If your company is about to start a new website or feels that the current one grew without order, the sitemap is the starting point. Schedule a free 15-minute call and we will review with you the structure your website needs so every buyer reaches what they need in a few clicks.

BOOK YOUR CALL

Pick a time