Start with the jobs visitors need to do
Navigation is the set of routes people use to move around your website. A menu is important, but it is only one part of the journey: in-page links, breadcrumbs, headings and a search function can also help someone find a useful answer. Start by listing tasks a new customer is likely to attempt, rather than listing the pages your team happened to create.
A local service business might expect visitors to understand its work, check the area covered and find a way to enquire. A shop might need visitors to find delivery information or opening hours. Ask staff who answer questions which details people struggle to locate, and test those tasks before changing labels.
Group information by customer language
Write the main topics on cards or a simple list and group pages that belong together. Use the names customers recognise for those groups. A service label that makes sense to an internal team may not tell a first-time visitor what is behind it. Compare your proposed words with the terms used in actual enquiries and supplier conversations.
Keep related details connected without making a visitor learn the company structure. Pricing guidance, for example, might belong with the service it describes rather than behind an ambiguous corporate heading. If several audiences have different needs, explain the choices clearly and avoid assuming everyone will know which department is responsible.
Choose clear, distinct menu labels
A small top-level menu can point to services, locations, information about the business and contact details where those pages are useful. The exact labels should fit the website. Avoid several headings that mean almost the same thing, or a vague label such as “Solutions” when a plain service name would explain the destination better.
Keep the label consistent with the destination page heading. If an item says “Website design”, the page should explain that service. A link to a contact form should be recognisable as a contact option, not disguised as a download or a promise of immediate support. Visitors should be able to make a reasonable choice without guessing.
A clear route through a service website
- FindChoose an understandable menu label
- UnderstandRead the service and coverage
- CheckFollow relevant supporting information
- ActUse a clear contact route
Plan menus for phones and keyboards
A compact menu button can save space on a phone, but it still needs a clear label, a visible open state and links that are easy to select. Check that the menu can be opened and closed using a keyboard and that focus remains visible. A control that responds only to hovering can exclude people using touch screens or keyboards.
Do not assume that every visitor begins on the homepage. Open a service page directly on a small screen and check whether a person can return to the broader service, find related information and reach the main menu. Test at different text sizes and avoid hiding the only important route inside an interaction a visitor may not discover.
Use supporting links where they answer a question
A service page can link to a guide that explains the work, a relevant location page and the appropriate contact route. Link text should describe the destination: “Read the website care guide” gives more context than several identical “Read more” links. Do not add a link simply because a phrase appears if the destination is not a useful next step.
Breadcrumbs can help on deeper pages by showing the path back to a broader section. They are not a substitute for sensible menu structure. When a page changes address, update links under your control and arrange an appropriate redirect where a close replacement exists. Check destinations directly rather than relying on the menu label alone.
An illustrative navigation review
Imagine a Hertfordshire garden-maintenance business with separate pages for regular care, one-off clearances and coverage. Customers regularly ask whether the team visits their area. The owner asks two colleagues unfamiliar with the site to find that information on a phone, without giving hints, and notes where they hesitate.
In this example the owner moves “Areas covered” to a clear location in the main navigation and adds a contextual link from each relevant service page. The business checks that coverage is truthful and current. The example demonstrates a review method, not a claim about measured results or a real client.
Review the structure after a change
When adding a new service, decide whether it needs its own useful page and where a visitor would expect to find it. Avoid placing every new page in the main menu. A well-organised overview page can introduce related options while leaving the navigation concise. Remove outdated links and check that redirects point to relevant replacements.
Keep a small page inventory with the URL, owner, purpose and review date. If two pages answer the same question, consider whether they should be improved, combined or distinguished. Explain any changes to staff who share links with customers, and check that downloaded documents or campaigns do not still point to a retired address.
A practical navigation checklist
Choose three realistic tasks and ask someone to complete them on a phone and a larger screen. Watch without directing the person and note the words they expected to see. Then test the menu and important links with a keyboard, including visible focus, opening and closing any menus, and the ability to return to the current page.
Review each label against its destination, keep the contact route understandable, and follow links from a page entered directly through search. Fix the most confusing obstacle first, then test again. A tidy navigation diagram is useful, but the meaningful result is that customers can find and use the information they need.
Sketch the route before editing the menu
Write the name of each important page on a card and ask a colleague to arrange the cards into groups they would expect to find together. Then give them a task, such as checking whether a service is offered nearby, and ask where they would look first. Note unexpected choices without telling them that they are wrong. Their language may reveal a better menu label or a missing explanation.
Turn the groups into a simple outline showing the homepage, service overview and supporting pages. Check that each destination can be reached from at least one meaningful route and that a visitor can return to the broader topic. After publishing, follow the same tasks on a phone and with a keyboard. Update the outline when the structure changes so a new editor can understand why the pages are arranged that way.
