Menu

IA

Taxonomy Review

A practical information architecture method for auditing an existing taxonomy and improving the parts that create confusion, inconsistency, or poor findability.

How to use taxonomy review to assess an existing structure, find where it breaks down, and improve categories, labels, and hierarchy without starting again.

4 min read

What it is

review is a UX and IA method used to assess how well an existing content or product structure performs.

It focuses on evaluating categories, , labels, and relationships to identify gaps, inconsistencies, and areas of confusion.

Unlike , which creates structure, a review audits what already exists and improves it.

It typically combines , analytics, and to understand where the structure is breaking down.

The goal is to make the existing clearer, more consistent, and easier to navigate.

Taxonomy review is most useful when the structure already exists, but users are still struggling because that structure is no longer working clearly or consistently.

When to use it

Use this method when you already have a structure but it’s underperforming.

It is most useful when:

Users struggle to find content or products
Navigation feels inconsistent or confusing
Categories have grown organically over time
Search is being used as a workaround
You are preparing for a redesign or optimisation

It is less useful when:

You need to create a taxonomy from scratch
There is very little content or structure
You need deep behavioural research
Taxonomy review is often used before taxonomy redesign or optimisation work.

Key takeaway

Use taxonomy review when the structure is already there, but you need to understand why it is failing before deciding how much to change.

How to run it

Set up properly

Be clear on which parts of the are in scope, what you have, and what a good outcome looks like. Reviewing everything at once produces a list nobody can act on.

Gather analytics, and any existing before you begin. A review based only on inspection will find what is untidy rather than what is failing.

Run the method

review is analytical and structured. Unlike designing one from scratch, you are diagnosing a that is already carrying live content and live .

  1. Audit the existing structure and categories as they are actually populated, not as the documentation describes them.
  2. Identify inconsistencies and overlaps: categories that duplicate each other, or that were clearly added under pressure.
  3. Analyse real and against the structure. Where people route around a category, it is not working.
  4. Review labels and terminology for drift. decay through well-meant additions more often than through bad initial design.
  5. Highlight gaps and redundancies, and separate the two. A gap needs content; a redundancy needs a decision nobody has wanted to make.

Focus on how the performs in practice. A structure can be logically immaculate and still fail every task put through it.

Capture and make sense of it

The value comes from identifying breakdowns. Look across the findings to identify:

  • Categories that confuse, attract everything, or attract nothing
  • Duplicated or overlapping content, and which people use
  • Gaps where real user needs have no home
  • Misalignment between the structure and observed

Use this to inform improvements. A review earns its cost when it produces a prioritised set of changes, not a critique of the current state.

What to look for

Focus on:

Clarity: whether categories are understandable
Consistency: alignment across the structure
Redundancy: duplicate or overlapping categories
Gaps: missing areas in the taxonomy
Behaviour: how users actually navigate

Where it goes wrong

Most issues come from:

If the structure isn’t aligned with users, it will continue to fail.

Reviewing the documented structure rather than the one carrying live content
Inspecting without analytics, which finds what is untidy rather than what fails
Renaming categories while leaving the overlap that caused the confusion
Adding a category to solve each problem, which is how it decayed
Producing a critique instead of a prioritised set of changes

What you get from it

Done properly, this method gives you:

Categories that confuse, or that absorb everything, or that attract nothing
Duplicated content, and evidence of which version people actually use
Gaps where a real user need has no home
A work plan rather than an assessment

Key takeaway

It helps you fix what’s already there instead of starting again.

Get in touch

If this sounds like something you need, we can review your structure and fix what’s not working.

No guesswork. No assumptions. Just clarity and consistency you can build on.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is a taxonomy review in UX?

It is a method used to evaluate and improve an existing content structure.

When should you run a taxonomy review?

Use it when users struggle to navigate or find content.

How is it different from taxonomy design?

Taxonomy design creates structure, while taxonomy review improves an existing one.

What data is used in a taxonomy review?

Analytics, search logs, user behaviour, and expert review.

Does taxonomy review improve UX?

Yes. It makes existing structures clearer and easier to use.

Quick take

If your structure exists but isn’t working, use a taxonomy review to fix it.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer