Summary: Navigation is the part of a website people notice only when it fails. Most small business sites go wrong the same few ways: menus organised around the company’s internal structure rather than what customers want, clever labels nobody understands, too many top-level items, and a mobile menu that hides everything behind an icon. This guide covers how many items a menu should hold, how to name them, what to do about dropdowns on phones, and the two tests that reveal whether yours is working.
Navigation is a promise
Someone arrives on your site with a question — do you do this, do you cover my area, what does it cost, how do I reach you. Your navigation either answers quickly or gets in the way. There is no third outcome, and a visitor who cannot find the answer does not email to ask. They go back to the results and click a competitor.
Organise around the customer, not the org chart
The most common mistake is a menu that mirrors how the business thinks of itself: divisions, product names, internal terminology. Customers do not know your structure and will not learn it.
Write down the five things people most often ask you before they buy. Those are your menu items. If “how much does it cost” is one of the first three — and it usually is — then pricing belongs in the menu, not buried three levels down.
How many items
Five to seven at the top level. Enough to cover what you do, few enough to scan in a second.
Beyond that, two things go wrong. People stop reading the menu as a whole and start hunting, which is slower. And on a phone it becomes a long scrolling list that nobody reaches the bottom of.
If you genuinely have more, that is what a services landing page is for: one menu item, a page that lays out everything underneath it clearly.
Name things plainly
“Solutions” means nothing. Neither does “What We Do” on its own, or a made-up product name. The label should say what is behind it in the words a customer would use.
“Web Development” beats “Digital Engineering”. “Pricing” beats “Investment”. This is also how people search, so plain labels help you twice.
Dropdowns and phones
Dropdown menus work reasonably on a desktop and poorly on a touchscreen, where there is no hovering and a tap on the parent item is ambiguous — open the menu, or go to the page?
Two rules keep this manageable. Never go more than two levels deep, because a third level is unusable on a phone and hard to remember on a desktop. And make sure a parent item is either a real page or clearly just a heading — not something that looks tappable and does nothing.
The hamburger icon is fine and universally understood now. What is not fine is putting your only contact link inside it and nowhere else. On a mobile site, the phone number should be visible and tappable without opening any menu.
The footer is navigation too
People who reach the bottom of a page are looking for something. The footer should carry a full list of your pages, your address or service area, your phone number, and your hours if they matter.
It also helps search engines reach every page, which is worth having on a site with more than a few pages.
Two tests
The five-second test. Show your homepage to someone who does not know the business, for five seconds, then take it away. Ask what the company does and what they would click first. If they cannot answer, the problem is usually the menu.
The three-click check. Pick the five things a customer most wants — a price, a phone number, a specific service, your service area, an example of your work. Try to reach each from the homepage. Anything taking more than three clicks is too far.
Neither test needs a budget or a tool, and between them they find most of what is wrong.
What not to bother with
- Mega menus on a small site. They exist for retailers with hundreds of categories.
- Sticky menus that eat the screen. Fine if slim; on a phone a tall one leaves nothing to read.
- Animated menus. Every fraction of a second between tap and result is friction with no upside.
- A search box instead of structure. On a fifteen-page site, search is what people resort to when navigation has already failed.
Common questions
How many items should a website menu have?
Five to seven at the top level. Enough to cover what you do, few enough to scan in about a second. If you have more services than that, use one menu item pointing to a services page that lays them out clearly rather than stretching the menu.
Are dropdown menus bad for mobile?
They are awkward rather than bad. Touchscreens have no hover, so tapping a parent item is ambiguous. Keep to two levels at most, and make sure every parent is either a real page or obviously just a heading.
Should my phone number be in the menu?
It should be visible without opening the menu at all. On a phone, a tappable number in the header is one of the highest-value elements on a local service site. Hiding it behind a hamburger icon costs calls.
How do I know if my navigation is working?
Two tests. Show your homepage to someone unfamiliar for five seconds and ask what the business does and what they would click. Then check that a price, your phone number, a specific service and an example of your work are each reachable in three clicks or fewer.
Visitors arriving but not enquiring?
Navigation is one of the first things we look at. We will tell you what is getting in the way — and if the structure is fine, we will say that too.
Get in touch Call (647) 385-5532
BridgeWeb has been building websites in North York, Toronto since 2006 — 115 projects across 14 industries.
