Navigation, Content & Information Findability Audit

Module overview & learning objectives

A navigation and findability audit examines how easily users can locate the information they need to complete a task. It considers information organisation, navigation labels, content grouping, page presentation, links and search.

Complete information-finding tasks on desktop and mobile. Document the routes taken, identify points of confusion and map where the interface supports or obstructs access to essential information.

This audit builds on Module 1’s scope and key tasks and Module 2’s usability findings.

By the end of this module, you should be able to:

Assess information hierarchy and navigation labels.
Distinguish discoverability from findability.
Examine content grouping, scanability and link clarity.
Evaluate search within realistic task contexts.
Identify unnecessary cognitive demands.
Compare desktop and mobile navigation.
Produce an audit map supported by evidence.

Learning output

Navigation & Findability Audit Map

Navigation, discoverability & findability

Navigation helps users move through a website or application. Findability describes how readily users can locate specific information or functionality.

Every menu link may work, yet users may struggle to locate course fees because the information sits under an unexpected heading. Examine both the route and the information at its destination.

Central question

Can users identify a promising route, reach the required information and recognise that it answers their question?

Concept	Audit question	Example
Discoverability	Can users notice an available option?	Can prospective learners notice the course-comparison feature?
Findability	Can users locate a specific item?	Can prospective learners find the fee for a selected course?

These concepts can overlap. A comparison feature may be difficult to find because its entry point is visually hidden or uses an unclear label. Record the observable barrier before assigning a category.

Assessing information hierarchy

Information hierarchy determines how content is organised across the product and within individual pages.

Product-level hierarchy

Inspect main sections and their relationships.
Record the levels between entry points and essential information.
Check whether important content has a logical location.
Examine how users can understand where they are.

Page-level hierarchy

Inspect page titles and section headings.
Examine the order and prominence of information.
Assess the relationship between primary and supporting content.
Check whether details needed for decisions appear together.

For a course website, prospective learners may need the description, entry requirements, fees, duration and schedule before deciding to enquire.

Example issue

Fees appear in a general policy document rather than on the relevant course page. Users may need to search elsewhere and may be unsure whether the fee applies to their course.

Fewer clicks do not always mean a better experience. A clear route with meaningful steps may be easier to follow than a shorter route with ambiguous choices.

Menu labels & navigation cues

Navigation labels should help users predict what they will find after selecting an option.

Use language familiar to the target users.
Describe the content or action accurately.
Distinguish neighbouring options.
Keep labels consistent across pages and devices.

Orientation cue	What to inspect
Selected states	Can users identify the current page or section?
Breadcrumbs	Where appropriate, do they explain the location within a hierarchy?
Page titles	Do they match the route and content?
Return routes	Can users return to broader categories predictably?

Example issue

Resources, Information and Useful Links contain overlapping course information. Users may struggle to choose a route and repeatedly switch between sections.

Record what the label promises and what the destination actually contains.

Content grouping & scanability

Grouping brings related information together. Scanability helps users locate relevant details without reading every sentence.

Area	What to examine
Grouping	Whether related information appears together.
Headings	Whether headings describe the content beneath them.
Paragraphs	Whether long passages obscure important details.
Lists and tables	Whether they help users inspect requirements or compare options.
Emphasis	Whether essential information stands out appropriately.
Expandable content	Whether labels reveal what is hidden inside.
Terminology	Whether wording needs unnecessary interpretation.

Example issue

Entry requirements, fees and application instructions appear in one long paragraph under About Us. Users may overlook details or read unrelated content to answer a specific question.

Expandable sections can organise content, but their labels should indicate what they contain. “Fees and funding” communicates more than “More information.”

Reviewing links & search

Link clarity

Links should communicate a useful destination or action.

Use descriptive link text.
Distinguish links with different destinations.
Check whether destinations work and support the task.
Indicate downloads or external destinations where helpful.
Place links near relevant information.

Example: Several “Click here” links lead to different documents. Users must inspect surrounding text or open each link to determine its purpose.

Search effectiveness

Where search exists, test queries relevant to the selected tasks.

An exact course or service name.
A broader subject term.
A plausible alternative term.
A query that produces no results.

Inspect search visibility, result relevance, descriptive titles, filters and empty-result guidance.

Example: “Course cost” returns no results although fee information exists. Users may conclude the information is unavailable.

Evidence boundary

Record the exact query and returned results. One unsuccessful query supports a finding about that query and context, rather than a claim that search always fails.

Identifying cognitive load

Cognitive load refers to the mental effort needed to understand information and make decisions. Look for interface demands such as:

Remembering details from earlier pages.
Interpreting unclear categories or terminology.
Comparing information presented in different formats.
Choosing between many similar options.
Repeatedly checking whether a destination is relevant.

Example issue

Course comparison requires remembering fees and schedules from separate pages with different layouts. Users may revisit pages or take notes to complete the comparison.

Describe the demands you observe. Claims about how much effort users experience require research or testing.

Desktop & mobile navigation

Use the same information goals on desktop and mobile, while allowing the route to differ.

Desktop inspection	Mobile inspection
Visibility of primary and secondary navigation	Discoverability of the menu control
Dropdown or expanded menu behaviour	Nested or expandable menu behaviour
Titles and selected-state orientation	Orientation after opening and closing menus
Scanability across wider layouts	Content order in stacked layouts
Visibility of search and supporting links	Search visibility within limited screen space
Keyboard access to navigation	Touch interaction and relevant keyboard access

Record the browser, viewport and whether the mobile context uses a physical device or simulation.

Example issue

A fee link visible beside the course description on desktop appears far below promotional content on mobile. Mobile users may have more difficulty noticing or locating it.

Responsive presentation should preserve access to information needed for the task.

Information-finding tasks

Select tasks requiring specific information. Use Module 1’s goals and define what counts as a complete answer.

Task	Completion condition
Find the fee for a course	Locate the stated fee and identify inclusions or exclusions.
Check entry requirements	Locate requirements and assess the supplied qualification scenario.
Find the study schedule	Identify relevant class days or times.
Compare two courses	Locate comparable fees, durations and study modes.
Find eligibility support	Locate guidance or a contact route for an unresolved question.

Task walkthrough

Record the starting point and device context.
State the information sought and completion condition.
Follow a realistic route.
Record pages, navigation choices and search queries.
Identify hesitation points, dead ends or backtracking in your walkthrough.
Record whether the information was found and answered the question.

Whose behaviour?

If representative users perform the tasks, distinguish their observed behaviour from the evaluator’s own walkthrough.

Navigation & Findability Audit Map

The map connects user goals to routes, destinations and barriers. Use an annotated route diagram or structured table.

Map field	What to record
Task ID and goal	The information the user needs.
Starting point	Where the task begins.
Device context	Desktop or mobile, with relevant details.
Route taken	Pages, menu choices, links or queries.
Destination	Where required information appears.
Outcome	Found, partly found or not found.
Barrier	The observed navigation or content problem.
Evidence	Screenshots, labels, URLs or query results.
Potential impact	How the barrier could affect the task.
Improvement direction	A proposed change addressing the barrier.

Worked example: finding a course fee

Field	Example
Task	Find the fee for Business Essentials.
Starting point	Course website homepage.
Device	Mobile viewport.
Route	Menu, Courses, Business Essentials, Additional details.
Destination	Collapsed section on the course page.
Outcome	Found.
Barrier	The section label does not indicate fee information.
Evidence	Screenshot of the heading and expanded fee content.
Potential impact	Users looking for pricing may overlook the section.
Improvement	Use a descriptive heading such as Fees and funding.

Completion and friction

Successful task completion does not remove the need to record barriers encountered along the route.

Practical activity & submission

Audit navigation and findability within your existing scope.

Select three to five information-finding tasks.
Define the required information and completion conditions.
Complete each task on the included devices.
Record routes, labels, queries and destinations.
Identify barriers involving hierarchy, grouping, scanability or cognitive demands.
Consolidate evidence into an audit map.
Link relevant findings to Module 2’s issue log without duplicating the same problem.

Learning output requirements

Clear information goals and completion conditions.
Documented routes and destinations.
Desktop and mobile observations.
Findings supported by specific evidence.
Task outcomes and potential user impacts.
Practical improvement directions.
Explicit assumptions and evaluation limitations.

Quality check

Another evaluator should understand where essential information sits, how users can reach it and which barriers may obstruct the journey. The map supports Module 4’s consolidation and prioritisation.