Navigation Menus: What Should (and Shouldn't) Be in Yours

Most navigation menus I audit have too much in them. Not a little too much, either. Think "Services, Products, Solutions, About Us, Our Team, Our Story, Blog, News, Careers, FAQ, Contact" too much. Every one of those tabs felt necessary to whoever built the site. None of them are helping a customer with a leaking pipe or a dead furnace find the "call us now" button.

Here's the honest answer: your navigation menu should have 4 to 6 items, and every single one should answer a question a real visitor is actually asking. Not "what might someone want to know about us eventually." What are they asking in the first 5 seconds on your site. This article settles what belongs, what doesn't, and how to tell the difference for your specific business.

The short answer

Home, Services, About, Reviews, Contact. That's the entire menu for most local service businesses, and it's not because I'm being minimalist for style points. It's because a service business website has exactly one job: get a visitor to call, text, or fill out a form before they leave. Every nav item that doesn't move them toward that is a distraction with a label on it.

Add a phone number or "Call Now" button as its own element, not buried inside a dropdown. Add "Service Areas" if you cover more than one city or county. Drop "Blog" from the top-level menu unless content is genuinely core to how you get found (link it from the footer instead). Drop "Careers" from the customer-facing nav entirely; it belongs on its own page linked from the footer, not competing with Contact for attention.

The data backs this up. Menu size directly affects whether a visitor finds what they're looking for, and the drop-off isn't gradual. It's a cliff once you cross into the 9-plus range.

These are benchmark ranges pulled from published usability testing patterns, not a single study of your exact site, so your numbers will vary. But the direction never flips. More items, worse findability. Every time.

What actually matters here

Forget the "7 items" rule you've probably read somewhere. Nielsen Norman Group has directly called that a myth. The right number depends on your business, not a magic constant from 1950s memory research. What actually determines your menu is three things.

First, how many genuinely distinct things does a visitor need to do on your site? For a one-service business (say, a garage door repair company), that might just be "learn what you do, see proof you're legit, get in touch." Three buckets, three or four nav items. For a company running plumbing, HVAC, and electrical under one brand, that's naturally more, and a dropdown under "Services" earns its keep.

Second, how do people actually search for what you offer? NN/G's menu design research is blunt about this: use labels visitors already recognize, not internal jargon. "Services" beats "Solutions." "Reviews" beats "Testimonials" for most trades because that's the word people type into Google.

Third, what do your analytics already show people clicking? If you've never looked, this is worth doing before you redesign anything. Run a quick competitor site audit alongside your own to see which nav patterns are actually earning clicks in your category, not just which ones look nice.

Scenario A: the simple flat menu (most of you)

If you run one core service, or a handful of closely related ones, out of one or two locations, you don't need anything clever. Home, Services, About, Reviews, Contact, plus a visible phone number. That's five items and a phone number, and it covers every real question a visitor has: what do you do, are you legit, will you answer the phone.

Resist the urge to add more just because you have more pages. Your About page can hold your story, your license number, your years in business. That content doesn't need its own top-level tab plus a "Meet the Team" tab plus an "Our Mission" tab. One page, one nav item, everything relevant lives there.

This is where most visitors decide whether to trust you enough to call, and the data on that click pattern is fairly consistent across local service categories.

Services and Contact eat well over half of first clicks combined. Everything else in your menu is fighting over the leftovers. Design accordingly.

Scenario B: when a dropdown or mega menu earns its place

Now the other case. Say you're a multi-service contractor covering plumbing, HVAC, and electrical across four metro-area cities. That's not five pages anymore, it's closer to twenty, and a flat menu would either hide most of them or turn into an unreadable wall of tabs.

This is where a dropdown, or at real scale a mega menu, is the right call. NN/G's research on mega menus found that showing everything at once, organized into clear groups, beats forcing visitors to remember what's buried three clicks deep. People can scan a well-organized menu far faster than they can recall an invisible site structure.

But "we're a bigger business" isn't the same as "we need a mega menu." The threshold is roughly 15-plus service or location pages before the added build cost and design complexity pays for itself, which is worth factoring into your website budget if you're quoting a rebuild. Below that, a simple two-level dropdown under "Services" does the same job for a fraction of the development time.

And mega menus fail just as often as they succeed. NN/G's teardown of bad mega menu implementations found the common failure isn't having one. It's dumping items into it with no grouping logic, or arranging them in ways that don't match how people actually scan a page (horizontally instead of top to bottom, for instance). A mega menu with no structure is just a bigger, uglier version of the same clutter problem.

What most local service businesses get wrong

The single biggest mistake I see is hiding the navigation behind a hamburger icon on desktop. Not on mobile, where space is genuinely tight and a hamburger is the right trade-off. On desktop, where there's a full 1400 pixels of empty header space, and someone still decided to hide the menu behind three lines and an icon.

NN/G's testing on this is unambiguous: discoverability is cut almost in half when navigation is hidden, and task time goes up along with it. If visitors don't notice a menu exists, they don't use it. They just leave, or they scroll blindly hunting for a phone number that was one click away the whole time.

The second-biggest mistake is nav labels that sound like they were written for a boardroom, not a customer. "Solutions" instead of "Services." "Our Story" instead of "About." Google's own guidance on semantic site navigation emphasizes clear, consistent structure for a reason: it helps search engines and humans understand your site the same way, and vague labels confuse both. If it's not clear from the label what's behind it, rewrite it. This same clarity principle matters when you're structuring pages for search, which is worth checking against a proper on-page SEO checklist while you're at it.

The bottom line

Keep it to 4 to 6 top-level items built around what a real visitor is trying to do, not what your business is organized into internally. Home, Services, About, Reviews, Contact, plus a phone number that's visible without a click. Add a dropdown only once you've genuinely outgrown a flat list. Cut Blog, Careers, and anything with a vague label from the top nav and give it a home in the footer instead.

If you're not sure which category you're in, pull up your own site next to a couple of competitors and count. If you're one of a few similar local businesses fighting for the same searches, this is also a good moment to look at real case studies from other service businesses for how they structured their menus, then test a simplified version of your own against the current one. Something as basic as swapping the header for a week and watching your call volume is the same logic behind any proper homepage A/B test.

Frequently asked questions

How many items should be in a website navigation menu?

For most local service businesses, 4 to 6 top-level items is the sweet spot. There's no hard rule that caps it at 7 — that's a myth based on outdated memory research — but every item you add past 6 dilutes attention and makes the menu harder to scan on a phone.

Should I put my phone number in the navigation menu?

Yes. A phone number or a "Call Now" button in the nav, not buried in the footer, is one of the highest-value things you can put there for a service business. It should be visible on every page, including mobile, without needing a tap to reveal it.

Do I need a mega menu for my business website?

Only if you genuinely have enough content to need one, usually 15 or more services or location pages. A mega menu on a five-page site adds development cost and visual clutter with nothing to organize. A simple dropdown covers most local service businesses just fine.

Should Blog or Careers be in the main navigation?

Generally no. Blog content works better linked from the footer or a resources page unless content marketing is core to your strategy, and Careers almost never belongs in a customer-facing menu. Every item you add competes for attention with Services and Contact, which are the two that actually drive calls.

Is a hamburger menu bad for a business website on desktop?

On desktop, yes, in most cases. Hiding navigation behind a hamburger icon on a wide screen with plenty of room cuts discoverability nearly in half compared to a visible menu bar. Hamburger icons make sense on mobile where space is genuinely tight, not on desktop where it's a stylistic choice with a usability cost.