Skip to content
Interface language: English
Design / Signal

B2B website information architecture: organise services and content paths

Plan services, navigation and links for a B2B website using audience questions, a content map, tests and ownership.

Article language: English

Aeneia world concept: a designer tests movable wall modules and benches on open terraces overlooking the water.
In this article

A visitor came to check your services and found a puzzle: what is the difference between “Solutions”, “Capabilities” and “Possibilities”? Information architecture should spare them that effort. It is a plan for content, its names and the connections between items. Start with the visitor's questions, give each page a specific job, and see whether the answer can be found without a guide from your company. The menu follows from that work; drawing tabs alone will not do it.

A well-organised site lets people distinguish a service from an article, terms of engagement from a brand statement, and a way to contact you from a download. It does not require visitors to learn the company's internal organisation chart. The workshop below helps establish that order. It is a recommended design process, not a Google rule for the number of menu items.

Start with the visitor's decision, not the company's departments

Write down three concrete situations that bring someone to the site. For example, they may be looking for a team to build a new website, planning to rebuild an existing one, or needing to assess a completed project. These are working scenarios, not customer stories. For each one, add the questions: does the company handle a similar need, what result does it deliver, and what should the visitor prepare for a conversation?

Do not begin with a catalogue of “strategy, creative, technology”. It may reflect how the team works, but the visitor still cannot tell where to find information that addresses their need. Check whether a menu label makes its contents predictable without an extra explanation. An original name can remain part of the brand if a clear description explains its function.

Decisions about the audience, scope and desired action should already appear in the premium website brief. Without them, the map will reflect the designer's assumptions. In that case, review questions from real sales conversations without copying personal information or confidential details into the project. For more context, see the article on preparing a premium website brief (in Polish).

Inventory the content, including the awkward parts

Collect existing URLs, documents, service copy, forms, articles and downloads. For each item, record its owner, the date it was last checked, its purpose and the decision: keep, improve, combine or retire. A page does not deserve to stay simply because it has existed for a long time. An old appearance does not mean its content has lost value either.

Separate public content from material provided only after a conversation. A detailed price list may need context, but the basic approach to pricing should have a planned place. A document describing an outdated service scope must not remain an accidental second source of truth just because someone once linked to it in the footer.

If URLs are changing, maintain a migration map of old and new pages alongside the content inventory. The editorial decision “we are combining two services” has a technical consequence: the old link still needs a meaningful response. Do not leave that dependency until the evening before launch. The related topic is explained in the article on planning a website migration without losing URLs (in Polish).

Give each page one main job

For each planned page, write one sentence beginning “After reading this, the visitor can...”. A service page can help someone assess fit and scope. An article explains a specific problem. A contact page lets someone choose how to start a conversation. If one sentence contains seven independent goals, you are probably mixing several types of content.

Then assign the main question, the content needed to answer it and the next step. For a website design service, these include the result of the work, the client's contribution, the boundaries of the scope and how the work will be reviewed. A detailed typography guide can remain an article that the service page links to at the appropriate moment.

This separation helps decide when a landing page is enough and when a company website is needed (in Polish). You do not need more URLs just to fill a catalogue. A separate page makes sense when it answers a distinct question and can be maintained as a current, self-contained piece.

Build a hierarchy and test labels without a mockup

Put topics on simple cards. Ask someone who is not involved in the project to find where information about timing, scope or preparing materials belongs. Observe their choice and reasoning. Do not correct their answer during the exercise. If you have to explain that “Laboratory” means services, the label may be the problem rather than an inattentive reader.

A text-only page tree is enough for the first test. Give the participant a task and let them choose the next item at each step. Record the first decision, any hesitation and where they go back. Do not turn a few conversations into percentage claims about effectiveness. Use them to find ambiguity and prepare the next version.

W3C WAI explains the value of a logical page structure: regions and headings help people orient themselves and navigate. This supports a clear structure; it does not require a particular number of menu levels. Record the chosen depth as a team decision that can be checked in a user scenario.

Aeneia conceptual photography

Design paths between pieces of content

Visitors do not always start on the home page. They may open an article or a service page directly, or follow an old link in a message. Each important page should explain its context on its own and offer a useful next step. A heading such as “Our method” that does not name the service often becomes unclear outside the sequence its author planned.

Design at least three paths: from a problem to a service, from a service to evidence, and from a specific resource to contact. A link should follow from a question in its paragraph. A list of ten random articles under every piece does not replace that work. Further reading should help the visitor make a decision, not merely keep them on the site.

Google describes how to make links understandable and crawlable. Use ordinary links with an address and a description of the destination. “Scope of a service-page project” says more than a repeated “read more”. But there is no need to turn every link into a long phrase packed with keywords.

Turn the map into content outlines and ownership

Only now prepare an outline for each page: title, questions for its sections, required material and onward links. At this point it is easy to notice a missing description of the result or three repetitive introductions. A separate service-copy writing workshop can help before the empty boxes in a mockup are filled with random slogans. This is discussed further in the article on writing copy for a service page (in Polish).

For a key service, plan the service-page structure and credible evidence. The architecture of the whole site does not yet determine whether the client will understand the result of the work on that page. Two levels of review are useful: the map identifies the right place, and the individual page outline checks whether the answer is complete. For the related method, consult the article on a B2B service-page structure and evidence (in Polish).

Give every important item of content an owner. That person confirms the scope, whether the information is current and when it should be reviewed. Without ownership, even a good map gradually becomes a collection of exceptions. Add a new service using the same rules instead of creating another menu item simply because a new campaign has started.

How do you resolve a dispute about a separate page?

Suppose, as a working example, that the team wants to offer a “brand identity refresh” and a “new website” separately. Check whether they serve different audiences, produce different results and have different starting conditions. If each can be purchased independently and understood without reading the other service's page, separate places may be justified. A shared process or similar appearance does not rule that out.

The reverse happens when three names describe stages of the same order. Separate pages may then suggest three independent services. Instead of expanding the menu, show the stages on one service page and prepare articles explaining the harder decisions. The way the service is purchased and the visitor's task settle the question, not the size of an image in a presentation.

Also record what would justify a later change. It could be the actual emergence of a separate scope, a distinct sales process or recurring questions that the current structure does not serve. The map then remains open to change without requiring the whole site to be redesigned for every new proposal.

What should be reviewed before screen design?

Conduct the final review using the documents, without a decorative presentation. Give someone a visitor's question and ask them to find the answer. Also check the reverse path: someone lands on an article and wants to learn who can help with the problem it describes. A missing connection can hurt more than a small difference in wording.

  • Every important item has a purpose and an owner.
  • Labels make it possible to predict page contents.
  • Answers to key questions can be found without relying solely on files.
  • Service pages do not compete for the same job.
  • Links lead to a justified next decision.
  • Changes to old URLs have a recorded way of being handled.

The workshop should produce a working document: a map, a content inventory, three described paths and open questions with responsible people. That is a better basis for discussing the work with a contractor than simply saying “let's simplify the menu”. Simplification then means a concrete change to the visitor's path.

Before handing over the map, choose one item of each type and note its minimum information. A service needs its scope, an article needs a question and an answer, and a document needs a name and an explanation of its use. If the site offers many documents, prepare a resource library that identifies each file's version and intended use. The guide to organising a resource library (in Polish) explains how to make choosing a file follow the same logic as choosing a page. This short template protects the structure as the site grows: a new team member does not have to reconstruct the whole logic of the site to add one useful page. If the site includes a shop, extend the template into a product-catalogue content model with separate attributes, variants and related materials. The guide to modelling product-catalogue content (in Polish) explains how to organise those elements.

Want to organise your site before design begins? Prepare a list of your services and current URLs, then explore the scope of Aeneia Design.

For a deeper hierarchy, also refine the breadcrumb navigation (in Polish). It should show a page's place in the hierarchy rather than blindly copy the visitor's click history. This is especially helpful when someone arrives from a search engine directly at a detailed service page.

On a larger site, also check how visitors search for answers and the path through the mobile menu (in Polish). The map may look clear on paper while still losing people who use a particular way to navigate. Further guidance is available in the article on internal search on a B2B website (in Polish).

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear