
Ready for a better website?
Serious about growing your business online?
Build the main menu around buying questions, with a separate route for existing clients.
Use the header for frequent decisions and the footer for a broader, clearly grouped directory.
Choose labels that predict the destination. A distinctive visual design does not require mysterious wording.
Test mobile, keyboard and expanded-menu behavior on real pages, including long titles and small screens.
Measure whether visitors complete useful journeys, not whether a redesigned menu receives more clicks.
A visitor should not need to understand your company structure to find the service they need. Yet a website menu often reflects internal departments, favourite brand phrases and pages added over several years. The result can look tidy while making a simple decision unnecessarily difficult.
Good service business website navigation starts with the visitor's next question. What do you do? Have you handled work like mine? Do you serve my area? What happens if I contact you? Give those questions clear destinations before deciding how the menu should animate.
Start With Tasks, Then Choose Pages
Write down the questions people ask before becoming a suitable enquiry. Use actual sales conversations, support requests and existing site content where available. Avoid inventing a complex audience model when the business already hears the same practical questions every week.
For a hypothetical cabinetry company, the tasks might be to compare custom cabinets with a standard range, inspect completed kitchens, understand the installation process and arrange a consultation. A returning customer may instead need to access project documents. Those are different journeys, even though they begin on the same website.
Create a small destination list before drawing the header. For each proposed link, record the visitor question, the page that answers it and the next action available there. If a destination does not exist, a new menu label will not solve the missing content. If two pages answer the same question, resolve the overlap before adding both to the menu.
This exercise also exposes links that are present only because someone wanted their department represented. A page can remain useful without being a top-level navigation item. Place it where the reader will naturally need it, and keep a route from an appropriate overview page.
When navigation is part of a larger rebuild, include this destination list in your website redesign brief. It gives the designer something more actionable than a request for a cleaner menu.
Give the Header and Footer Different Jobs
The header should help a visitor orient themselves and take a useful next step. The footer can offer a wider directory once someone has reached the end of a page. Repeating important destinations is reasonable; repeating every link with equal emphasis is rarely necessary.
A sensible starting point for a small service business is a services route, proof of work, information about the company and a contact action. This is a starting point, not a required number of links. A specialist consultancy with two offers and a contractor with several service categories may need different structures.
Visitor need | Likely placement | What to check |
|---|---|---|
Understand the offer | Main navigation and relevant page links | The services overview explains the differences |
See relevant work | Main navigation or a prominent proof section | Projects include context, not only photographs |
Check service coverage | Service pages and a useful footer route | Locations reflect real coverage |
Make an enquiry | Clear header action and contextual page actions | The destination explains what happens next |
Access an existing project | Separate client-login link | It reaches the correct portal login |
Read privacy information | Footer and relevant forms | The link remains easy to find |
Group footer links by purpose, using headings such as Services, Company and Resources when those categories fit the site. Avoid a single long list in which a privacy policy, a service page and a client login appear indistinguishable.
The footer is also a good place to offer a direct contact route. Keep the wording consistent with the actual process. A button labelled Book a call should lead to a working booking experience, while Send an enquiry should not unexpectedly require someone to choose a meeting time.
Make Labels Predict the Destination
A label earns its place when a visitor can reasonably predict what appears after clicking it. Services, Projects and Contact may feel ordinary to the business owner, but they provide useful orientation. Personality can come through typography, composition, imagery and the surrounding copy.
Consider the difference between Explore and Kitchen projects. Explore could lead almost anywhere. Kitchen projects makes a promise that can be checked. A broad label may still work for a genuinely broad resource hub, but it needs a destination that helps people narrow their choice.
Keep the same meaning across the site. If the header says Projects, the footer says Our work and the page title says Portfolio, the wording may be understandable, but it creates unnecessary translation. Choose a consistent label unless the context benefits from a more specific phrase.
Do not use several near-identical contact actions for different processes without explaining the difference. Get started, Let's talk and Request a quote might all reach the same form. That is manageable. If one books a call, another opens email and a third begins a lengthy application, the labels should give visitors a better indication of the commitment.
Client login deserves particular care. It serves an existing relationship rather than a new purchase. Make it easy to find without presenting it as the main action for new visitors. Verify the destination after any portal migration, and avoid publishing a login button that merely opens a generic software homepage.
Add Submenus Only When They Improve the Choice
A submenu is useful when it makes a meaningful group easier to scan. It is less useful when it hides a short list that could have remained visible or creates several layers of decisions before a person reaches content.
For a hypothetical home-improvement business, Services might reveal Kitchens, Bathrooms and Whole-home renovations. Each destination should describe an actual offer. A list of internal capabilities such as Strategy, Solutions and Delivery may require more interpretation unless the audience already uses those terms.
Decide whether the parent label opens an overview page or expands a list. If it does both, the controls need to make the distinction clear. People should not have to discover through trial and error whether tapping Services navigates away or reveals more choices.
W3C's fly-out menu guidance describes ways to expose submenu state and support keyboard operation. It also recommends another route to submenu destinations, such as links on the parent page. Ask your developer to test the chosen pattern rather than assuming a hover effect makes it complete.
The practical alternative to an elaborate menu is often a better overview page. Give that page short descriptions and useful comparisons so visitors can choose a service with context. A menu does not need to carry the entire sales explanation.
Treat the Mobile Menu as a Complete Experience

A mobile menu needs more than a smaller version of the desktop layout. Opening, scrolling, choosing a destination and closing it must work together. Review the actual expanded state, not only the closed header in a design presentation.
Long menus are especially revealing. Try a small screen with a larger text setting. Check whether the final links and close control remain reachable, whether the panel can scroll when needed and whether content behind it behaves as intended. A beautiful panel that clips the contact action is unfinished.
Keep important destinations available on mobile. Removing a service or client-login route simply to fit the first screen changes the site's usefulness. Reorganize the layout instead. A compact group of primary links followed by secondary links can provide hierarchy without making everything compete for attention.
Test repeated use as well. Open the menu, follow a link, return with the browser's back control and open it again. Check an in-page anchor if the site uses one. The panel should not remain visibly stuck over the destination or leave the page unable to scroll.
Animation should support the interaction. A short entrance can clarify that a panel has opened, but a visitor should not have to wait through a long sequence before selecting a link. Include a reduced-motion treatment and verify that the menu still communicates its state when movement is removed.
Check Keyboard Use and Underlying Links
Ask for a keyboard review alongside the visual review. Starting at the page top, use Tab to move through navigation controls, activate a destination and inspect the focus indicator. Test closing the expanded menu and confirm the next focus position is sensible for the chosen pattern.
W3C's menu structure tutorial explains semantic navigation, list structure, navigation labels and indication of the current item. These are implementation concerns that a screenshot cannot prove. A menu can look like a list of links while exposing very little useful structure to assistive technology.
Search discovery has a separate implementation check. Google's link guidance recommends anchor elements with an href destination and descriptive link text. Ask the developer to inspect the rendered links, including cards and footer items, rather than testing only whether a mouse click appears to work.
Neither correct markup nor a new menu guarantees indexing or rankings. They establish useful foundations. A page still needs a clear purpose and worthwhile content. Adding every city or every keyword to the footer does not make those destinations helpful.
For location-specific content, decide first whether a page provides useful local information. Our guide to service-area pages for contractors covers that decision separately. Navigation should expose a sound content structure, not disguise a weak one.
Run a Short Acceptance Review Before Publishing
Use real destination URLs and actual labels for this review. Placeholder links can make a prototype appear finished while leaving the public experience incomplete. Assign someone to record failures and check the fixes on the published version.
Choose three visitor tasks. For example, find a specific service, inspect relevant work and make an enquiry. Record the intended destination for each.
Start from different pages. Test the homepage, a service detail page and an article. Visitors do not all enter through the homepage.
Check every navigation destination. Include the logo, footer, client login, privacy information and any booking action.
Review desktop and mobile states. Test open and closed menus, long labels, scrolling and a smaller viewport.
Complete the keyboard journey. Check visible focus, activation, submenu behavior and closing the panel.
Inspect link implementation. Confirm real destinations and distinguish navigation links from controls that expand content.
Follow the enquiry through. Submit an authorized test using clearly identified test details and verify the expected destination or confirmation.
Repeat the key paths after publication. The editor preview is not the final public site.
The last part extends beyond the menu. If a contact button reaches the right form but the enquiry never reaches the team, the journey still fails. Use the website enquiry form checklist when reviewing that handoff.
Keep the acceptance notes concise: task, device or input method, expected result, observed result and owner of the fix. This is more useful than a collection of screenshots labelled looks good.
Measure Successful Journeys After Launch
A menu redesign should be assessed against the tasks it was intended to support. More clicks can mean better engagement, but they can also mean people are struggling to find the right destination. Treat click counts as clues rather than a success verdict.
Where your analytics setup supports it appropriately, compare visits to important destinations and completion of relevant actions. Separate existing-client activity from new enquiries. Someone opening the portal is not necessarily a new sales lead, and an internal test booking should not inflate conversion reporting.
For smaller sites, direct observation can be useful before there is enough traffic for a meaningful comparison. Ask a person unfamiliar with the business to find a service and explain what they expect each label to contain. Record where their expectation differs from the destination, then improve that mismatch.
Avoid changing the entire menu every few days. Fix clear faults promptly, but give a coherent structure time to produce usable evidence. Record major changes and compare similar periods without assuming the menu caused every movement in traffic or enquiries.
Next steps
Write down three things a suitable visitor needs to do, then try each journey on the live website. Fix unclear labels, missing destinations and broken interactions before investing in a more elaborate menu animation.
If those journeys are difficult to evaluate, request a website audit. We can help identify the next practical improvements to the website, with navigation considered as part of the complete path from first visit to enquiry.



