Before rewriting menu labels or commissioning a navigation redesign, collect the current menu links, the content of their destination pages and three tasks visitors need to complete. Use those inputs to test whether people can choose a sensible first step—not simply whether reviewers like the wording.
This guide proposes a small, task-based review for website owners and marketers. The supplied Navigation page reference contains only a title and URL, so it does not establish any problems with the current website or verify an existing AIM navigation tool. The workflow below is a proposal to test, not a diagnosis or a report of completed work.
Start with destinations, not menu preferences
A useful review begins with what visitors want to accomplish. Before showing participants the menu, ask where they would expect to go to complete a task. Then compare those expectations with the available labels and destinations.
Choose three priority tasks using customer questions, campaign briefs or other evidence available to your team. If those inputs are missing, document the tasks as assumptions and validate them before treating findings as representative.
Write each task without borrowing the menu wording. For example, asking someone to find out whether a service fits their requirements is more neutral than asking them to click a menu item named “Services.” Agree in advance which destinations would reasonably satisfy each task; more than one route may be valid.
Build a small task-to-destination worksheet
Keep the first review narrow: one menu, up to ten links and three tasks. This is a proposed pilot scope, not a rule for every website. Record each link’s visible label, destination, page purpose and relationship to the selected tasks.
For each task, capture the participant’s expected destination, first menu choice, time taken and any difficulty continuing. Include space for uncertainty: a plausible choice that leads to incomplete content is different from an unclear label.
Review the destination content as well as the menu. If a page does not answer the visitor’s question or explain the next step, changing the label alone would leave that content gap unresolved.
Run a focused first-click pilot
One proposed pilot is to involve ten people whose roles, needs and technical confidence resemble the intended audience. That audience fit needs checking; convenient colleagues should not automatically be treated as representative visitors.
Give participants a neutral task script and avoid coaching them toward a preferred link. Record their first choice and task time, and note accessibility blockers separately. Make the prototype keyboard-accessible and include keyboard completion in the review. First-click findings alone should not be treated as a complete accessibility assessment.
If comparing current and proposed menus, vary which version participants encounter first. Also note when repeated tasks may let participants remember an earlier route. With a small pilot, use the findings to identify questions and possible fixes rather than claim a definitive improvement.
Hypothetical example: a promising label, an incomplete destination
Hypothetical example: A service business wants visitors to check suitability, understand pricing and contact the right team. Its menu includes “Solutions,” “Resources” and “Connect.” These labels and this business are illustrative, not observations about AIM Engine.
For the pricing task, the review would record which link each participant selects and inspect whether the destination provides useful pricing information or a clear way to request it. If participants choose different links, that could justify testing clearer wording. If the intended page lacks pricing guidance, the proposed fix would also need to address its content.
The worksheet might recommend testing a more explicit pricing label. That recommendation would remain unvalidated until tested; it would not establish that enquiries or sales will increase.
Rank fixes without deleting useful routes
Turn observations into a short list of proposed changes. For each finding, state the task affected, what happened, the suspected cause, the proposed fix and what evidence would confirm it. Separate observed difficulty from the explanation you want to test.
Give attention first to blocked essential journeys, then ambiguous choices and avoidable steps. Flag repeated destinations for review rather than automatically removing them: two links to the same page may serve different contexts. Require owner approval before removals and check that essential routes remain available.
A smaller menu involves trade-offs. Removing a choice may simplify one task while making another harder. Retest affected journeys rather than assuming fewer items are always better.
Reuse findings for campaign and team handoffs
The same worksheet can support a campaign review. Map each campaign promise to a supplied landing page, then check whether that page explains the promised offer and next step. This does not require advertising-platform access, but it does require the campaign brief and page content.
A mismatch is a review finding, not evidence of lost conversions. Assign each proposed change an owner, an approval requirement and a retest date. Before building imports or integrations, verify which content-inventory and campaign tools already exist so the workflow does not duplicate them.
Measure the pilot before expanding it
Establish a baseline for first-click success, task time and reviewer effort. No baseline is available in the supplied material. A possible pilot target is a 15-percentage-point improvement in first-click success without increased median task time; this is a proposed threshold, not an expected result.
Begin with three documented findings and a retest plan. Expand into automation only after checking whether reviewers can complete the setup, understand the uncertainty and use the findings to make decisions. The immediate aim is a clearer basis for navigation changes—not an unsupported promise of better rankings or business results.

Add an example, conclusion or question.
Short, specific responses help AIM Community improve future articles and product decisions.