If the menu consists of as many headings as the designer could fit on the screen, there’s no information architecture. Most corporate web projects start with a design draft; as the site grows, new services fall under “Other”, sector pages into the footer and blog posts into unrelated categories. Two years later, nobody can explain why a page is where it is. Information architecture prevents this mess from the start by organizing content according to the user’s task. This guide explains content inventory, card sorting, menu depth, URL hierarchy and service–content linking for web teams, marketing owners and project managers, independent of platform.
Why information architecture comes before design
Design is the visual expression of information architecture. A home page drawn before it’s clear which pages there will be, how they will link to each other and which path the user will follow breaks a little more with every new piece of content added. The practical results of getting the order right:
- The number of templates becomes clear: Once page types such as service, sector, solution, reference and guide are settled, a template is designed for each; design isn’t done page by page.
- The menu is built right from the start: Menu headings are derived from content groups, not from the horizontal space in the design.
- URLs become permanent: Since the hierarchy is clear from the start, there’s no need to change URLs in the first year.
- Migration risk drops: In redesign projects, mapping existing URLs to the new structure is done at this stage.
If the redesign is also a migration project, the preventing SEO loss when migrating a website guide is the direct continuation of this work for URL mapping and the redirect plan. Without a mapping table, there’s no migration.
Content inventory and user tasks
The first step is a list of all existing pages. With a crawl tool or a list exported from the CMS, the following information is put into a table for each page: URL, title, page type, owner, last update date, organic traffic and number of incoming internal links. A decision column is added to each row: keep, merge, rewrite or remove. Compare the number found by the crawl tool with the number of published items in the CMS; the difference usually reveals orphan pages cut off from the menu and forgotten campaign pages.
The second step is writing down the user tasks the site serves. On a corporate IT services site, the tasks are usually these:
- Finding the service that will solve a specific problem (“do they offer server backup services?”).
- Seeing experience relevant to their own sector.
- Researching a technical topic and assessing the source’s expertise.
- Requesting a quote or getting in touch.
- Reaching the support channel as an existing customer.
Every page in the inventory should serve at least one task. A page that can’t be linked to any task is either merged or removed. If several pages meet the same task in the same way, that’s content cannibalization; the search engine can’t tell which one to show either.
Card sorting and category naming
In card sorting, content headings are written on cards and participants are asked to group them. There are three types:
| Type | How it’s done | When |
|---|---|---|
| On | Participants create and name the groups themselves | Discovering a new structure |
| Off | The groups are predefined, participants place the cards | Testing a proposed structure |
| Hybrid | Predefined groups exist, new groups can be added | Improving an existing structure |
Choose participants from the target audience: IT managers on the customer side, procurement owners and, if possible, existing customers. If you work only with participants from inside the company, the organization chart gets carried into the menu. Users don’t search for “Systems Department”. They search for “Servers and backup”.
After card sorting, tree testing validates the proposed hierarchy. The participant is shown only the menu tree as text and given tasks such as “You want to have the restorability of your backups tested; where would you look?” A task that leads to the wrong branch shows that the category name or position is problematic. It’s done when there’s no design yet, which is why it’s cheap.
The naming rules are simple: choose the term users use in searches and conversation, avoid internal abbreviations, and write headings at the same level in the same grammatical structure. Don’t put two headings with overlapping meanings, such as “Solutions” and “Services”, in the same menu; if you do, define the difference and explain it the same way on both pages.
Menu depth and mega menu decisions
The main menu doesn’t have to show all the site’s content; it should show the shortest path to the core tasks. Five to seven headings at the first level is a manageable range for most corporate sites. A practical rule for depth: the user should be able to reach a service page with at most two menu selections. Deeper content is offered from the relevant category page.
| Status | Recommended setup |
|---|---|
| 2–6 destinations under a heading | Simple dropdown |
| 8+ groupable destinations under a heading | Grouped mega menu |
| Each group with 10+ pages of its own | Group heading in the mega menu, details on the category page |
| Specialist site on a separate subdomain | A clearly labeled transition link in the main menu |
Mega menus tend to grow uncontrollably. If every new page is added to the menu, within a few months the menu turns into a sitemap. Show only group headings and the most-used destinations in the mega menu, and list the whole group on the category page. Accessibility is also part of the architecture decision: the menu should open with the keyboard, the aria-expanded state should update correctly, and touch targets on mobile should be large enough. A situation we often see in audits is a menu that opens only on mouse hover. It doesn’t work on touch screens or with the keyboard.
If there are several specialist sites in the network (such as a main corporate site and topic-based subdomains), users should understand which site they’re moving to. The label of the link to the subsite should show this clearly; a shared top navigation or an “other sites in the network” section should sit in the same place, in the same form, on all sites.
URL hierarchy and permanence
A URL is the content’s permanent address and should be thought of independently of the menu. The W3C principle “Cool URIs don’t change” still holds today: information that may change over time (department name, campaign year, file extension, CMS page ID) isn’t put in the URL. An example sitemap:
/ Home page
/services/ Services category page
/services/server-backup/ Service page
/services/network-security/ Service page
/sectors/ Sectors category page
/sectors/automotive-supply/ Sector page
/guides/ Content archive
/guides/backup-rule/ Guide article
/about-us/
/contact/
Points to note in this structure:
- Service addresses are in the category folder but at a single level. When a sub-service is added, a third level isn’t opened; if necessary, it’s added as a sibling page.
- Guide articles don’t carry the category name in the URL; when the article’s category changes, its address doesn’t.
- Slugs are without Turkish characters, lowercase and hyphenated; the same rule applies across the whole site.
- Whether to use a trailing slash is decided, and the other form is consolidated into a single form with a permanent redirect. If both forms return 200, every page has two copies.
Breadcrumbs are the visible counterpart of the URL hierarchy and can be marked up with structured data (BreadcrumbList). Managing filter and parameter addresses you don’t want indexed is the subject of the canonical, noindex, robots.txt and sitemap article; if a multilingual structure is planned, see the multilingual site architecture guide for how to add language folders to the hierarchy. The primary source for search engine recommendations on URL structure is the Google Search Central documentation.
Linking service pages and content
On corporate sites, guide and blog content usually stands disconnected from the service pages. An article gets traffic but doesn’t direct the reader to the relevant service; the service page doesn’t link to content that goes deeper into the topic either. There’s traffic, but no requests. The linking setup defines this relationship from the start:
- For each service page, a content cluster is defined that covers the problems the service solves.
- Each article in the cluster gives at least one in-context link to the relevant service page.
- The service page links to the two or three most comprehensive articles in the cluster with a “related guides” section.
- Articles in the same cluster link to each other at points where they complement the topic without repeating it.
- Category and tag archives are defined to align with these clusters; random tags aren’t added to every article.
How this is implemented in the CMS is a separate decision. In WordPress, if services are set up as a custom post type, related articles can be associated with a custom field and listed automatically in the template; we explained this approach for Elementor-based sites in the scalable site structure with Elementor article. For the setup to hold up, which service cluster each new article belongs to should be decided in the content calendar before publication.
The output of the work should be in writing: the content inventory table, the list of user tasks, the approved sitemap, the menu structure, URL rules and the service–content cluster mapping. These documents are the shared reference for both the design team and content editors. A decision that isn’t written down is forgotten. For planning information architecture and site structure, you can review our corporate website design and technical SEO and site architecture services, and for connecting editorial processes to this structure, our corporate content management service.
Frequently asked questions
Is information architecture work necessary for a small corporate site too?
Yes, at a smaller scale. Even for a fifteen-page site, the content inventory, user tasks and menu decision can be put in writing with a few hours of work. The real benefit is that when the site grows, where a new page will be added is known in advance.
Is using a category folder in the URL required for SEO?
No. Search engines crawl flat URLs without any problem. The benefit of a folder structure is aimed more at users and site management: reporting on content groups, writing redirect rules, keeping breadcrumbs consistent. What matters is that the chosen structure is permanent.
When is using a mega menu the right decision?
When there are many destinations that can be grouped under a first-level heading and the user needs to see the options together before choosing. If there are only a few sub-links, a simple dropdown is faster and more accessible.
Should URLs change when the menu structure changes?
No. The menu is the navigation path offered to the user and can change over time; the URL is the permanent address. Changing the URL because of a change of position in the menu creates a redirect burden and link loss. Change the URL only when the content itself changes, and with a redirect plan.