Definition:
A navigation path is the sequence of pages, screens, or actions that a person moves through within a website or application during a visit. It may begin on an entry page, continue through menus, links, searches, or buttons, and end when the person leaves, completes a task, or interrupts the session.
The path may be an observed sequence in usage data or an intended route considered during design. It does not imply that there is a single correct path: different people may reach the same content from different entry points and decisions.
How it works
Each interaction may produce a transition from one state to another. On a traditional website, this is commonly recorded as a succession of page views. In an application, it may also include screens, searches, filters, menu openings, events, or steps that do not change the URL.
The path depends on the available structure and the person’s decisions. Menus, search, internal links, and recommendations open alternatives, while permissions, errors, forms, or unavailable content may interrupt them. The Back button can also create returns that form part of the actual path.
A measurement tool reconstructs the event order from the data it receives. Interpreting the sequence requires criteria for sessions, identity, time zone, events, and page changes. If implementation omits a screen or duplicates an event, the recorded path will not match the complete experience.
Types of paths
Paths can be classified according to the viewpoint used. These categories are not always mutually exclusive:
- Observed: a sequence reconstructed from pages, screens, or events that were actually recorded.
- Intended: the route proposed by the design for completing a task or reaching content.
- Hierarchical: movement between categories, subcategories, and detail pages at different levels.
- Exploratory: a path with branches, comparisons, searches, and returns rather than a fixed order.
- Transactional: a sequence associated with a process such as registration, booking, purchase, or inquiry.
An intended path can be used as a design hypothesis, but observed behavior may differ. Comparing the two can reveal alternative entry points, skipped steps, repetitions, and places where the path stops progressing.
Breadcrumbs do not necessarily represent the pages visited. They usually show the current page’s position within the site hierarchy. Someone may arrive from a search engine directly at a deep page and see the full hierarchy without having visited its preceding levels.
Navigability is a quality of the system: it expresses how readily people can orient themselves and move around. A path is the specific or modeled sequence. A site may support many paths while still presenting orientation, consistency, or accessibility problems.
A user flow commonly describes the designed steps for a task, while a customer journey covers a broader relationship that may include several channels and moments. A navigation path has a narrower scope and focuses on movements within a defined interface or digital environment.
Design does not force people through one sequence. Its role is to provide understandable options, preserve context, and allow people to move forward, go back, or change strategy according to their goal.
- Menus: present stable destinations and a recognizable organization across sections.
- Links: connect related content and offer continuations within the reading context.
- Search and filters: reduce available options without requiring the entire hierarchy to be traversed.
- Calls to action: a call to action indicates a possible action, but its presence does not guarantee selection.
- State and return: indicate location, previous selections, progress, and ways to return without losing information.
Titles, labels, and destinations should maintain a clear correspondence. If a control promises a different action from the page received, opens a broken path, or removes previous state, the route may become confusing even when its structure appears short.
Measurement and limitations
Path analysis can show entry and exit pages, preceding and following steps, repetitions, branches, and completed actions. These signals help formulate questions about friction and discovery, but they need context to be interpreted.
An exit does not necessarily demonstrate a failure: the person may have obtained the information required. A long path may likewise represent useful exploration or difficulty. Comparing segments, devices, and tasks avoids treating path length as a universal measure of quality.
Navigation data has limitations. Measurement blocking, device changes, consent, interrupted sessions, missing events, and several people using the same device can fragment the sequence. Aggregated reports also do not by themselves explain individual intent or the cause of abandonment.
When a path is associated with identified or identifiable people, minimization and transparency should apply. Purpose, retention, and access must be defined, especially when sequences are used to create profiles, personalize content, or make automated decisions.