Insights · Nov 11, 2026 · 5 min read · FAQ

Is your website menu helping buyers find the right service?

A good menu uses the buyer's words, keeps the top level short, works by tap, keyboard and screen reader, and gives Google plain links.

NAV MENUSLabels, mobile, keyboard SELLWRIGHT

A buyer lands on your home page asking one thing: do you do what I need? On many service sites the menu answers in the company's own language: Solutions, Capabilities, Platform. They open three dropdowns and guess. A menu that works uses the buyer's words, stays short, opens with a tap or a key press and gives Google plain links.

What should the menu items be called?

Call them what buyers call them: the service or the problem, not internal product names. Google's SEO starter guide notes that people who know a topic well may search with different words from newcomers, such as charcuterie versus cheese board. Menus have the same gap: your team says Growth Suite, a buyer looks for Bookkeeping.

Take the words from enquiry emails, sales call notes and the Queries view of Search Console's Performance report, which groups search data by the terms people typed. Then group items one way per menu: by service, by problem or by type of business.

How much belongs in the top level?

Only the few sections a buyer needs to decide and get in touch. The GOV.UK Design System puts it plainly: navigation links should go to the most important top-level sections, and navigation is not a site map. On a typical service site that means:

  • Services, opening to each service plus a link to the services hub.
  • Proof, such as Work or Case studies.
  • About, if who does the work matters to your buyers.
  • Contact, or a clear enquiry label such as Book a call, as the last item.

Keep the contact link visible at every screen size, worded like the main button on your pages. Policies, careers and older resources belong in the footer or on hub pages, with links in the content doing the rest.

Dropdown or mega menu?

A simple dropdown suits most service sites; a mega menu earns its place only when many services fall into groups buyers recognise. Six services fit a plain dropdown; thirty across four practice areas suit a mega menu with one plain heading per group.

Either way, the menu should not be the only route. W3C's fly-out menu tutorial notes that people with reduced dexterity, such as tremors, often have trouble operating fly-out menus, and suggests repeating submenu items on the parent page. So list every service on the Services page too, and link to it from the dropdown.

How should the menu work on a phone?

With the same structure as on desktop, opened by tapping a button. W3C's menu tutorial says menu structure should be consistent across screen sizes: items may collapse, but the ones that show keep the same order, wording and destination.

Hover is not an option there: MDN notes that many mobile devices can only emulate hovering with an inconvenient long tap. In Webflow, the Navbar's menu button appears at the tablet breakpoint and below by default and opens the same nav menu used on desktop, as a vertical list. We keep the contact link outside the collapsed menu, one tap away.

How do you build it for keyboards, screen readers and Google?

With plain HTML: a labelled nav element, buttons that open dropdowns and ordinary links that go to pages. The W3C ARIA Authoring Practices Guide calls this a disclosure navigation menu:

  • Label the nav, for example aria-label="Main", so screen reader users can find it and tell it from other menus.
  • Open each dropdown with a button whose aria-expanded is true when open and false when closed. Enter or Space toggles it; in the W3C example, Escape closes it and returns focus to the button.
  • Don't open submenus as Tab passes through. W3C notes keyboard users would then have to step through every submenu item.
  • Leave out the ARIA menu role: typical site navigation doesn't need the keyboard behaviour it promises.
  • Mark the current page with aria-current="page".
<nav aria-label="Main">
  <ul>
    <li>
      <button aria-expanded="false" aria-controls="services-menu">
        Services
      </button>
      <ul id="services-menu">
        <li><a href="/services/bookkeeping/">Bookkeeping</a></li>
        <li><a href="/services/payroll/">Payroll</a></li>
        <li><a href="/services/">All services</a></li>
      </ul>
    </li>
    <li><a href="/work/">Case studies</a></li>
    <li><a href="/contact/">Book a call</a></li>
  </ul>
</nav>

The links matter to Google too. Google says it can generally crawl a link only when it is an <a> element with an href; a span with an href or an <a> that navigates through onclick is not recommended. In Webflow, the Navbar and Dropdown elements support keyboards and screen readers without custom code, but Webflow says they need a visible focus style to be fully keyboard accessible.

How do you test a menu with real people?

Give people tasks, not a tour, and watch where they go first:

  1. Write three to five tasks in a buyer's words, such as: your bookkeeper is retiring, find out whether this firm can take over your monthly accounts.
  2. Ask a few people who match your buyers and haven't seen the site to try each task on their own phone. Note the first tap and any back-tracking.
  3. Repeat the tasks with a keyboard only, then once with a screen reader, checking that each dropdown button says whether it is expanded or collapsed.
  4. Check the home page in Search Console's URL Inspection tool to confirm the menu links appear in the rendered HTML.

Change one label or grouping at a time, then run the same tasks with new people.

Where to start

Write your menu down as a plain list and read it as a buyer who has never heard of you. Rename anything only your team would say, cut the top level to what helps someone decide, and run the keyboard check today. We build service site menus in our Webflow development work, or ask for a website review.

FAQ

Frequently asked questions

Should the Services item be a link or a button?

If it only opens a list, make it a button and put an All services link inside the list. If the top-level item must also go to a page, W3C's fly-out menu tutorial suggests a separate button beside the link to open the submenu. Webflow's Dropdown can work the same way, with the text as a link and the arrow opening the list.

Is it fine for dropdowns to open on hover on desktop?

Yes, as long as hover is not the only way in. W3C's fly-out example opens on hover for mouse users and waits a second before closing, so an imprecise mouse doesn't lose the list, while keyboard users open it by activating the parent item or a button. Webflow's Dropdown opens on click by default, with an optional hover setting and an adjustable close delay.

Does Google follow links inside a closed dropdown?

It can when they are already in the page as <a href> links: Google's rules for crawlable links are about the markup, and links that JavaScript inserts count too. Problems start when links load only after a click, because Google says Search does not interact with your page. Check the live page in Search Console's URL Inspection tool.

Should the logo link to the home page?

Yes. Webflow's Navbar guide calls a logo that links to the home page standard practice. Give the link a text alternative that says where it goes, such as your company name or Back to homepage. Google also uses an image's alt text as the anchor text when the image is a link, so keep that alt text descriptive rather than empty.

Can different pages show different menus?

Keep the main menu the same everywhere. WCAG 2.2's Consistent Navigation criterion asks that navigation repeated across pages appears in the same relative order each time, unless the user changes it. A section menu inside one area, such as a services sidebar, is fine as an addition, as long as it has its own label so screen reader users can tell the two apart.

Next step

Ready for a website that sells?

Book a short call. We will look at your current site, agree what matters most and send a written scope with a fixed quote.

Book a callOr write to hello@sellwrightstudio.com