Content inventory
List current URLs, page purposes, important assets, and ownership. Identify pages to retain, combine, replace, or retire.
Make your website easier to navigate and extend.
Norml organizes website pages, navigation, content types, and internal links around your offers and the questions visitors need answered.
Book a callA growing website needs clear relationships between its pages.
Services overlap across several pages.
Navigation labels make sense internally but need explanation for visitors.
New content has no obvious place in the website.
Editors need a consistent structure for recurring pages.
What our Information architecture services include.
We map the existing page inventory and the planned content, then define how each part relates to the others. The output connects navigation decisions with content models and page requirements.
Page hierarchy
Group services, products, resources, and proof around visitor needs and clear parent-child relationships.
Navigation and journeys
Define labels and paths that connect discovery, evaluation, supporting evidence, and contact.
Content model requirements
Describe recurring content types, shared fields, and relationships for the design and CMS teams.
Information architecture deliverables.
The agreed scope identifies which of these deliverables your project needs.
- 01
A current and proposed page inventory.
- 02
An annotated sitemap.
- 03
Navigation labels and grouping rules.
- 04
Priority visitor paths.
- 05
Content-model and internal-link requirements.
Our process
How our Information architecture process works.
Inventory the website
Collect pages and available evidence about their use.
[ 01 ]
Organize the content
Group related topics and identify distinct page purposes.
[ 02 ]
Review the journeys
Walk through the structure using representative visitor questions.
[ 03 ]
Document the decisions
Prepare the sitemap and requirements for writing, design, and development.
[ 04 ]Information architecture questions.
Is an XML sitemap enough?
An XML sitemap lists URLs for search engines. Information architecture also defines page hierarchy, navigation, content relationships, and user journeys.
Can this work with our current CMS?
Yes. We review its constraints before recommending structures that editors will need to maintain.
Does this include redirect implementation?
We can identify URL changes and prepare a redirect map. Implementing and testing those redirects is a separate development task.
Do you need to rewrite every page?
No. The inventory distinguishes content that can remain from pages that need a different purpose or new copy.
See how this work fits into our website strategy service.