What is information architecture?

Information architecture is the way a website is organised: which pages exist, how they are grouped, what they are called, and how a person moves between them. A clear structure means a visitor can find the product, the pricing, or the article they came for without hunting. A crawler can follow the same paths and understand which pages matter.

It is not a wireframe and it is not a visual design system. It is the skeleton those things hang on: the sitemap, the labels in the navigation, the URL pattern, and the relationships between a parent section and its child pages.

Why does information architecture matter?

When the structure is vague, teams add landing pages in the wrong place, invent a second blog, or hide important pages three clicks down. Search engines then struggle to find those pages, and your own colleagues struggle to brief new ones. A redesign that changes URLs without first agreeing the structure also makes the redirect map harder and riskier.

Good information architecture also makes a content management system easier to live with, because editors can see where a new page belongs instead of inventing a one-off.

How does Goodspeed handle information architecture?

We start with the current sitemap and a short set of jobs the site has to do, such as "book a call", "understand the product" or "read the latest change". We propose a structure, agree names and URL patterns with you, and only then design the templates. On a website migration, that signed-off structure is what the redirect map is built against.

This work sits inside a build or a migration, which start from $10,000, rather than as a separate slide deck. A website audit can expose a structure that is already getting in the way.

What does a typical information architecture pass look like in practice?

A company has a marketing site with a top nav of nine items, two overlapping resource sections, and product pages whose URLs do not match the names the sales team uses. We cut the nav to the jobs the site actually has to do, give resources one home, and line the product URLs up with the names already in use. New landing pages then have a parent to sit under, instead of being added as one-off experiments at the root.

What are the common mistakes?

1. Designing pages first and inventing the sitemap at the end.
2. Using internal team names in the navigation, so visitors cannot find the thing they call it.
3. Creating a new section every time someone wants a campaign page.
4. Changing URL patterns during build after the redirect map was already signed off.
5. Hiding important pages behind a footer-only link and expecting them to rank.

Common questions

What is information architecture on a website?

Information architecture is the way pages are grouped, labelled and linked so a person, and a search engine, can find the right page without guessing. It covers the sitemap, navigation, URLs and the relationships between sections.

Is information architecture the same as navigation design?

Navigation is the visible part. Information architecture also includes the hidden structure: what has a URL, what is a parent, what is a filter, and how a new landing page will sit in that system six months from now.

When should information architecture be decided on a project?

Before visual design is finished, and before anyone writes a redirect map. If you invent the structure at the end, you usually have to rename URLs, rewrite navigation and reopen signed-off pages.

How does Goodspeed work on information architecture?

We map the current site, agree the new structure with you, and lock the URL list before we design every template. That structure then feeds the redirect map, the CMS model and the navigation. Migrations and new builds start from $10,000.

Which related terms should you read next?

• Website redesign
• Website migration
• Technical SEO
• Content management system
• Redirect map
• The rest of the glossary

You can also browse the glossary, the resources hub, try the migration planner, or book a call.