The short answer

On a large site, information architecture starts with a complete inventory of the existing content, takes shape around users’ real tasks and the words they use, is built as a sitemap and a naming system, is tested with users, and is protected by clear rules after launch. The order matters: designing the menu is the end of this process, not the start.

We explained what information architecture is and why it matters in our previous article. This one is about how it is done.

1. Know what you have: the content inventory

The first step is a list of every page, document and form. It sounds tedious, but on large sites this is where most of the surprises turn up: forgotten sub-sites, three different pages for the same application, hundreds of PDFs nobody owns.

For each item, record at least:

  • its address (URL) and title,
  • which department it belongs to and who updates it,
  • when it was last updated,
  • its traffic and how often it is searched for on the site,
  • which other pages link to it.

Then make a decision for each item: keep, update, merge or remove. Note the address of every page that is removed or merged; during migration this list becomes your redirect map.

2. Learn why people come

Most corporate sites are organized around how the organization sees itself: departments, directorates, internal processes. Visitors come to get something done. Before building a structure, you need to know what those things are.

  • Stakeholder interviews. Learn what each department needs the site to achieve, which content is critical and which problems keep recurring.
  • User interviews. Talk to people from different audiences: why they come, what they call the things they look for, and where they give up.
  • Existing data. The most visited pages, on-site search logs, and the questions that reach the contact centre and inbox. Search logs are especially valuable: they show what people look for, in their own words.

By the end of this stage you should have a short list of top tasks: the ten or fifteen things people most often try to do on the site.

3. Choose an organizing principle

Large sites are usually organized by one of these principles, or a combination:

  • By task: “Apply”, “Pay”, “Report a fault”. Often the clearest structure for organizations that provide services.
  • By topic: “Water and wastewater”, “Investor relations”, “Sustainability”. Suits information-heavy content.
  • By audience: “Individuals”, “Businesses”, “Employees”. Works when audiences’ needs really differ; when they don’t, it forces visitors to put themselves in a box.
  • By department: Follows the organization chart. Rarely the right main structure for users, but it can have its place within a section such as “About us”.

Rather than forcing one principle everywhere, choose one for the main navigation and use the others as secondary routes.

4. Build the structure and the names together

Structure and naming are not separate jobs; the right group with the wrong name still can’t be found.

  • Card sorting. Ask users to group content titles in a way that makes sense to them, and to name the groups. Open card sorting shows the groups in people’s heads; closed card sorting shows whether the groups you propose are understood.
  • Sitemap. Draw the first sitemap from the top tasks and the inventory decisions. Keep the main menu to a small number of clearly distinct headings.
  • Naming glossary. Choose one term for every heading, category and label, and write it down. Prefer the words people use in search logs over internal abbreviations and technical terms.

5. Test the structure before the design

Tree testing is the quickest way to test a structure without any visual design. You show users a text-only menu tree and give them real tasks: “You want to dispute your water bill. Where would you click?” It becomes clear where people take the right path, where they hesitate and where they go wrong.

Fix the structure and names based on the results, and test again if needed. A change at this stage is a few lines; the same change after design and development is far more expensive.

6. Design navigation, templates and search around the structure

Once the structure is clear, UX/UI design turns it into an experience people can see:

  • Navigation: main menu, sub-menus, section overviews and in-page links.
  • Page templates: shared layouts for recurring content types such as service pages, announcements, documents and department pages. Templates keep content consistent.
  • Search: how results are ranked, which filters are offered, how synonyms are handled. On large sites, search is as important a route as navigation.
  • Addresses: readable URLs that reflect the structure guide both people and search engines.

7. Migrate with a redirect map

When an existing site moves to the new structure, the inventory from step one pays off. Give every old address a destination: the new page, the page it merged into, or the closest parent page. These pairs are set up as permanent (301) redirects.

The aim is simple: no old address should land on an empty page. Bookmarks, shared links and search engine listings should all reach the new structure. After launch, watch the error logs and fill in any addresses that were missed.

We applied the same rule when we moved Efabrika’s own website to a new platform: every address on the old site redirects to its counterpart on the new one.

8. Protect the structure after launch

Information architecture tends to erode in the first years after launch: every department wants its own page, and new headings get squeezed into the menu. To prevent that:

  • Ownership: every section and content type has someone responsible for it.
  • Rules for adding content: a short guide to where new content goes and what it is called.
  • Regular reviews: check the structure against traffic, search logs and user feedback at set intervals, and retire content that has gone stale.

Common mistakes

  • Building the menu as a copy of the organization chart.
  • Starting a new design without an inventory.
  • Taking names from internal language.
  • Going straight to visual design without testing the structure.
  • Not redirecting old addresses during migration.
  • Not naming an owner for the structure after launch.

From real projects

  • İSKİ website. As the site was redesigned and moved to a new platform, content and data from previous systems moved into a new information architecture, served by a headless back end that also feeds other channels.
  • Ministry of Interior websites. The websites of the Ministry and six affiliated units were redesigned on a shared corporate identity. Their structure is organized around what citizens come to do, so they can find answers quickly and consistently on every site.
  • Yıldız One. Yıldız Holding’s employee and business portal, organized so that people in very different businesses can quickly reach data dashboards, HR services, operational tools and company information from one place.

All of them are on the Work page.

Checklist

  1. An inventory of all content, with a keep, update, merge or remove decision for each item.
  2. Stakeholder and user interviews, search logs and the most frequent questions.
  3. A list of top tasks.
  4. A main organizing principle.
  5. A sitemap and naming glossary shaped by card sorting.
  6. Tree testing and fixes.
  7. Navigation, page templates, search and URL structure.
  8. A redirect map covering every old address.
  9. Ownership, rules for adding content and a review schedule.

If you’re looking for help applying these steps to your own site, have a look at Research & Strategy or get in touch.