Looks like you're in . Want the local site?
Ignited Nepal audits, rebuilds, and documents the page hierarchy, navigation, and content structure of UK B2B and professional services websites before a single design asset is created. We diagnose why visitors cannot find what they need, then build the structure that fixes it.
You started with a clean site three years ago. Since then, every campaign, every new service line, and every department request has added pages. Nobody deleted anything. Your navigation now has seven top-level items and four of them have dropdowns with twelve links each. Your bounce rate from the navigation is worse than from paid traffic. The site is not broken technically. The structure is broken.
You are moving from an outdated CMS to a modern platform and you have the budget and the appetite to do it properly. You know from experience that migrating content without fixing the structure first just means the new platform inherits the old chaos. You want an information architecture document that tells the development team exactly what pages exist, what they are called, how they relate to each other, and what URLs they live at before the build begins.
Your navigation has been debated in three board meetings and no decision has been made because different stakeholders want different things. You need an independent audit that grounds the conversation in user data and search behaviour, not internal politics. A documented IA gives you something to present, defend, and build from.
Most UK professional services websites have navigation that reflects internal organisational structure rather than how clients think about their problems. Legal firms navigate by practice area. Consultancies navigate by methodology. IT businesses navigate by product name. Visitors arrive with a problem to solve. If they cannot map their problem to your menu labels within three seconds, they leave.
CMS sprawl produces two specific technical problems. First, multiple pages competing for the same keyword reduce the ranking potential of each individual page. Second, pages that exist but are not linked from anywhere accumulate no authority and serve no user. A content audit exposes both. Most sites we assess have between twenty and forty percent of their pages in one of these two categories.
URL structures that use numeric IDs, temporary campaign slugs, or inconsistent folder hierarchies make it harder for search engines to understand the relationship between pages and harder for users to understand where they are on the site. A URL is a navigational signal. Most sites treat it as a technical afterthought.
The page template that was designed for a service overview is now being used for case studies, team biographies, news articles, and resource downloads. Each content type has different structural requirements. When all content is forced into the same template, important elements get cut, buried, or omitted. The user experience suffers and so does conversion.
We run a structured workshop with your key stakeholders to establish what the site needs to do, who the primary audiences are, what tasks those audiences come to complete, and what content currently exists versus what needs to be created. This produces the brief that every subsequent deliverable is built against.
We catalogue every page on your current site: its URL, its title, its purpose, its traffic, and its relationship to adjacent pages. We flag duplicates, orphans, thin pages, and pages that are competing with each other. You receive a spreadsheet that becomes the master record of your content inventory.
We document the three to five primary journeys a visitor takes through your site: from arrival, through consideration, to conversion or contact. For each journey we identify the pages that should exist, the content each page needs, and the navigational connections required between them. This is the functional brief for the sitemap.
We produce a sitemap that lists every page in the new structure: its position in the hierarchy, its parent page, its proposed URL slug, its content type, and its priority for the build. The sitemap is the single source of truth for the information architecture. It is reviewed and approved before any design or development work begins.
We write and test the navigation labels for primary and secondary navigation. Labels are assessed against three criteria: clarity for a first-time visitor, alignment with search intent for pages that need to rank, and consistency with the language your target clients actually use. We do not name navigation items after internal job functions.
For each content type in the new site, we produce a structural outline: the sections a page of that type contains, the content purpose of each section, and the interaction points such as CTAs, forms, or related content links. These outlines go to the design team with enough detail to design from without prescribing visual style.
We document the URL logic for every page and every content type. Folder hierarchy, slug format, handling of pagination and filters, treatment of legacy URLs that need to be preserved or redirected. The URL structure document becomes the instruction set for the development team and the SEO team.
We map the internal links that need to exist between pages: which pages link to which, what anchor text those links use, and what priority those links carry. Internal linking is how you transfer authority from high-traffic pages to conversion pages. It is also how search engines understand the relationship between your content. Most sites do it ad hoc. We plan it.
We package all deliverables into a design handover document: sitemap, user journeys, page template outlines, navigation labels, and URL structure. The design team receives a structural brief that tells them what to design, not just that something needs designing.
We assess your current site against five criteria: navigation clarity, content duplication, page hierarchy depth, URL logic, and internal linking coverage. We produce a one-page findings summary that identifies the three to five structural issues most affecting your site's performance. This takes five working days and is the starting point for every engagement.
We run a half-day workshop with the stakeholders who own the site, the content, and the business objectives. We establish audiences, tasks, content inventory, and priorities. The workshop output becomes the brief for the IA document.
We catalogue existing content, map the primary user journeys, and identify the gaps between what exists and what the journeys require. This stage produces the content inventory and the journey documentation.
We produce the sitemap, navigation labels, and URL structure. These are presented for stakeholder review and revised until approved. Nothing moves forward until the structure is agreed.
We produce structural outlines for each content type. These are reviewed alongside the sitemap so stakeholders can see both the structure of the site and the structure of the pages within it.
We map the internal linking architecture and document it in a format the development and content teams can implement directly.
We package all deliverables and brief the design team. We remain available during the design phase to answer structural questions and review designs against the IA document.
A content audit and IA diagnostic are standalone services. Not every site needs a full rebuild. In some cases the structure is broadly sound and only specific sections need restructuring. The diagnostic tells you what category you are in before you commit to a larger scope.
For a site with up to 150 pages, the full process from diagnostic to design handover typically takes four to six weeks. Larger sites or organisations with multiple stakeholder groups take longer. We agree a timeline at the start of each engagement based on your site size and internal decision-making pace.
You do not need a design brief. The IA process produces the structural input that a design brief is built from. Most clients use the sitemap and page template outlines as the foundation for their design brief.
Stakeholder disagreement on navigation is one of the most common reasons organisations commission an IA. We document competing views during the discovery workshop and ground the final recommendation in user research, search data, and business objective alignment. The documented rationale makes it easier for one view to prevail.
Yes. The URL structure document includes redirect mapping from old URLs to new ones. This is handed to the development team as part of the design handover and is essential for preserving search rankings through a relaunch.
Not a black box. Real specialists you can call, with their names on the work.
If your navigation has grown by committee, your content is duplicated across the site, or you are about to replatform and want to do it properly, the IA Diagnostic is the right first step. We assess your current structure, identify the specific problems, and give you a clear picture of what the fix involves before any commitment is made.
Ignited Nepal
Growth engineering · replies within 1 business day
By continuing you agree to our privacy policy.
