How to build information architecture on a corporate site

Information architecture on a corporate site decides how many steps a visitor takes to reach the job they came for. Colour and type come later. If someone arrived for “industrial kitchens”, they should not get lost under “our solutions”. Architecture is not a list of pages. It is which intent is answered on which page, and how that page leads to a quote. A design drawn before this tree exists becomes a handsome maze.

At Yuz Medya we build the site from incoming work, not from the menu. The three services sales explains most often are the spine of the homepage and the menu. A rarely asked job can live on a deeper page. Putting everything on the same level hides what is urgent. The tree is the discovery step of a corporate website. Skip discovery and the design becomes a digital copy of the old brochure.

How many doors should the menu open?

The top menu stays short. Services, work or method, the company and contact are enough for most sites. A fifth or sixth door opens only when there is a genuinely separate intent. Piling vision, mission, history and policies under “corporate” tires the person who is searching. History can be read. It is not the job of the first screen. A menu label is the word a person would search, not the jargon the internal team uses.

The service tree

Each service deserves a page. Not every page has to be a menu row. Close services gather in a family, and their pages stay separate. The family page shows the path. The child page closes the quote. Melting both into one long page blurs the arrival for both ads and search. We tie which page an ad lands on to this tree in aligning the landing page with Google Ads. An ad is not pointed at a page the tree does not have.

The path to a quote

Every service page has a next step: a form, a phone number or a booking. The step should not disappear at the bottom. If the same form asks the same fields on every page, the page should still know which service the person came from. Sales should not have to sort “which form”. The thank-you screen says when someone will reply. If the reply time is a promise the site never states, the form is not honest.

Content is not poured on the tree afterwards

If a page opens with “text will go here”, the architecture stays on paper. The first screen of every page gets a one-sentence promise, who it is for and the next step. The longer story sits under that sentence. A thin page looks swollen in the menu and empty in search. We cover the search side of a service page in on-page SEO for service pages. Architecture also predicts the heading hierarchy. One page has one main subject.

Language is part of the architecture. Turkish and English can carry the same tree. They do not have to carry the same wording. An English page should not read like a leftover translation. A language switch with no matching page opens an empty door. An empty door lowers trust. The translation is finished before the page goes live, or that language link stays hidden.

Read the tree before launch

Before design sign-off, someone who does not know the site walks it. Can they reach the service in three clicks? Is the path to a quote visible? Does the menu promise a job you do not sell? That walk becomes a note. Without the note, the argument is about colour. Colour does not shorten the path.

• A short menu: words a person would search, not internal jargon.
• A separate page: a service with its own promise gets its own URL.
• A next step: a visible path to a quote on every service page.
• No empty door: every menu row has a live page behind it.

As the site grows, the tree is read again. A new service is not pinned to the old “other” page. If a service is retired, it leaves the menu too. A broken promise costs more than a new page. We check how this tree behaves on a phone in a mobile-first checklist for a corporate site.

Frequently asked questions

Should the homepage explain everything?

No. The homepage shows the path: who you are, the three jobs people ask for most, and the door to a quote. The detail of each service lives on its own page. Stretching the homepage makes the menu unnecessary and crowds the first screen. Direction is worth more than an encyclopedia.

Where does the blog sit in the menu?

The blog does not replace the service. If someone came to buy a service, the blog is not the first door. Articles link back to the relevant service page. A modest place in the menu is enough. Putting the blog in front of the main promise lengthens the path to a quote.

Can the tree change when an old site exists?

Yes. A rebuild is exactly for that. The old menu is a habit. It is not automatically the right structure. URLs that work are moved to the new tree on purpose. Changing addresses at random breaks incoming links and someone’s bookmark. The move is part of approving the tree.