Mapping Your Website's Core Navigation User Journeys Before a Redesign

Identify Top Visitor Actions

When planning a website overhaul, business owners often debate visual styling while overlooking how visitors move through the pages. If the underlying structure is unclear, users may struggle to locate key service details or contact pathways.

To start a redesign effectively, consider identifying the top three actions visitors want to take on your specific site. For example, a local service business might find that users primarily want to check pricing, read service details, and book a consultation.

Listing these core goals clearly helps focus your planning on practical visitor needs, though opinions across an internal team regarding priority actions can sometimes vary.

Audit Existing Page Paths

Once you outline what visitors are trying to achieve, audit your existing page paths to measure current click depth. Count how many clicks it takes to reach important service pages from your homepage.

If finding pricing details requires navigating through multiple nested menus, some users might leave before finding what they need. However, visitors react differently depending on intent, and deeply nested paths do not always cause drop-offs if the content is deemed uniquely valuable.

Keep track of content gaps where information is completely missing or hidden inside long blocks of text.

Draft a Simplified Menu Structure

After auditing your old paths, draft a simplified menu structure using a hypothetical navigation audit worksheet. This worksheet lists top user goals, required click counts, and content gaps to guide your layout choices.

Here is a hypothetical example for a service business worksheet:

1. User Goal: Book a consultation. Required click count: 1 click from main menu. Content gap: Online calendar link missing from mobile view.

2. User Goal: View pricing plans. Required click count: 2 clicks. Content gap: Pricing buried inside a PDF download.

Structuring navigation around user tasks rather than internal corporate departments can sometimes require cross-team compromise on menu labels. Alternatively, an organisation with a single decision-maker might assign labels quickly without debate, though this approach carries the risk of overlooking staff input.

Test Proposed Pathways Early

Before making any code or layout changes, test your proposed pathways with non-technical staff or friendly contacts. Ask them to complete simple tasks like finding a contact form or checking a service list.

Watch where they hesitate or click the wrong menu items. This quick test can highlight confusing labels before you spend time and money on full development work.

Documenting user paths and addressing dead ends before updating a website helps clarify information pathways for visitors, keeping in mind that external factors like market conditions or pricing can still influence visitor behaviour over the long term.