List the questions a new visitor must answer: Do you do this work? Do you cover my area? Can I see examples? How do I enquire? Our recommendation is to map those questions to a small set of straightforward destinations such as Services, Areas, Our work, About and Contact. The exact number matters less than whether the choices make sense.
Avoid internal department names, clever labels and several links that appear to mean the same thing. “What we do”, “Solutions” and “Services” should not compete without a clear distinction. Put detailed service choices inside a useful Services page or an understandable submenu. Keep urgent contact information available without requiring someone to explore several levels.
Make the small-screen version predictable
W3C’s menu-structure guidance recommends consistent wording, ordering and destinations across screen sizes. If a desktop link says “Service areas”, do not quietly rename it “Coverage” on mobile. The visual arrangement can change while the meaning stays stable. A menu icon should have a clear accessible name; adding the visible word “Menu” can also reduce guesswork.
For menus with nested items, ask the developer how opening the submenu differs from following its parent link. W3C’s fly-out guidance covers mouse and keyboard operation. Our preference for small service sites is a simple disclosure control or a separate service overview, rather than a hover-dependent menu that has no clear equivalent on a touchscreen.
The clickable area matters, not just the size of its text or icon. WCAG 2.2’s target-size criterion generally uses 24 by 24 CSS pixels, with defined exceptions including spacing. Our practical recommendation is to make important menu and contact controls comfortably larger where the design allows, then check them on an actual phone instead of treating the minimum as a design target.
Watch for a narrow close icon, tightly stacked links and a sticky call bar that covers the last menu item. Open the menu in portrait and landscape orientations. Increase text size. If the menu is taller than the screen, users still need to reach every link and close it. A beautiful overlay that traps the contact link below the screen fails its purpose.
Give someone three tasks without coaching: find a particular service, confirm whether a nearby town is covered and start an enquiry. Note the labels they try first and any place they backtrack. Illustrative finding: people choose “Our approach” when looking for services because the service link is hidden under “Discover”. The fix may be a better label, not a new design.
Repeat with keyboard navigation on a desktop at a narrow width. Check that opening and closing the menu leaves the user in a sensible place. After editing navigation, test existing service-page links and the browser Back button. Record the confusing task and the revised destination so future edits do not recreate the same problem.
Your practical checklist
Use labels customers recognise.
Keep mobile and desktop destinations consistent.
Make submenus work without hovering.
Check menu controls and close buttons on a real phone.
Ensure overlays do not hide contact options.
Test service, service-area and enquiry tasks.
One useful next step
Ask one unfamiliar person to find your main service and start an enquiry from their phone while you observe silently.
Written with AI-assisted research and drafting, with source checks and editorial review for this guidebook. Platform facts link to official documentation. Examples and recommendations are our own; no client results are implied. Sources reviewed October 8, 2026. About Getting Found Local