Jump to a section +
The menu is a promise about how the business is organized. When its labels match internal departments rather than customer questions, visitors must translate company language before they can move. When every page is promoted, the header stops prioritizing anything. Good navigation is less about choosing a fashionable layout and more about deciding which routes deserve persistent attention.
Navigation also extends beyond the header. A service-page link can carry a buyer to a relevant case study. A location page can connect to the correct service and contact route. An article can lead into a comparison or project guide. Search can help a content-heavy site. The footer can expose policies and secondary paths. Plan those layers together so the main menu is not asked to do every job.
Build the menu from customer tasks
Turn business knowledge into navigation priorities
List the audiences
Name the people who actually use the site: new customers, returning customers, applicants, partners, members, patients, tenants, distributors, or press. Do not create a top-level menu item for every audience automatically.
List their important tasks
Use plain verbs and objects: compare services, check coverage, see work, understand a process, book a time, pay a bill, find support, or apply for a role. Include calls and customer conversations, not only analytics.
Rank frequency, value, and urgency
A frequent task may deserve persistent access. An infrequent but urgent task may need a utility link or alert. A valuable sales task may become the primary action. Rank with evidence and operational reality rather than executive preference.
Group by the visitor’s mental model
Customers may think in services, problems, industries, product families, or life events. Use the model they recognize, then decide whether a landing page or direct child link best supports each group.
Assign a navigation layer
Choose whether each path belongs in the header, utility row, dropdown, in-page context, search, account area, or footer. A page can be essential without appearing at the top level.
A simple scoring conversation prevents the loudest stakeholder from becoming the information architecture.
| Task | Possible evidence | Likely placement |
|---|---|---|
| Understand the primary service | Sales questions, search demand, service-page entrances, user interviews | Top-level Services or a specific primary service when the business is focused |
| Confirm geographic coverage | Out-of-area inquiries, location searches, multiple branches | Service-area detail in context; Locations in header when customers truly choose among places |
| Evaluate credibility | Repeated questions about experience, process, team, licenses, or examples | About, Work, Results, or a descriptive proof route; relevant proof also belongs on service pages |
| Request the main next step | Qualified calls, form submissions, purchases, bookings | Distinct primary action with wording that matches what happens next |
| Reach an existing-customer portal | High repeat use by current customers | Utility link or account control, visually separate from the new-customer journey |
| Read policies or accessibility information | Transaction, support, or compliance need | Footer plus context at the decision where the policy matters |
| Apply for a job | Active and meaningful recruiting program | Careers in utility or footer; header only when recruiting is a major site purpose |
Choose labels a first-time visitor can predict
Distinctive brand language can live inside the page without replacing the words people use to navigate. A menu label should help someone predict the destination before activating it. Google’s search documentation also recommends crawlable links and concise, relevant anchor text; clear labels can therefore support both human movement and the site’s internal linking structure without stuffing keywords into every item.
Avoid using the primary action as a vague decoration. “Get Started” may lead to a quote form, an account signup, a product configurator, or a consultation calendar. Name the next commitment when it matters: Request a Website Review, Check Availability, Shop Products, or Contact Support. The call-to-action guide helps align wording with the next screen and the team’s real process.
Use dropdowns only when the grouping helps
A dropdown is useful when it previews a meaningful group without forcing an extra landing-page decision. It is not a place to paste thirty unranked links. A compact service list, a small set of product families, or clearly separated audience routes may work. If a service group needs education, keep the parent landing page available rather than making the label only a toggle.
- Give the parent label one clear role: a destination, a disclosure control, or an intentionally supported combination.
- Keep related links together and use short, specific names instead of repeating promotional descriptions.
- Show which section and page are current so visitors can maintain orientation.
- Support keyboard focus, logical order, Escape or another documented close behavior, and focus return to the trigger.
- Avoid hover-only disclosure because touch, keyboard, speech, and screen-reader users need predictable operation too.
- Do not place critical transactional terms only inside a menu; repeat them where the customer makes the decision.
W3C’s navigation-menu tutorial distinguishes navigation menus from application-style menus and demonstrates patterns for site navigation. Copying desktop application semantics into an ordinary link list can make a site harder to operate. Use native links and buttons for their intended roles, and test the implementation with keyboard and assistive technologies rather than relying on appearance.
A sitemap inventories indexable and useful pages. A header repeatedly exposes the highest-priority routes. Making them identical can bury important customer tasks under policies, campaign pages, old resources, narrow locations, and internal labels.
Treat the mobile menu as its own interaction
A desktop header does not become a usable mobile menu merely because its links move into a drawer. The trigger needs an accessible name and visible state. The drawer needs a sensible reading and focus order, a dependable way to close, and enough room for zoomed text and long labels. Expanded groups should not hide where the visitor is or require precision tapping.
Test the mobile header under ordinary and adverse conditions.
| Test | What to do | Failure it can reveal |
|---|---|---|
| Touch | Open groups, follow links, return, and close on a small physical phone | Targets are crowded, states are ambiguous, or the page position is lost |
| Keyboard | Move through the trigger, links, nested groups, close action, and content after the menu | Focus disappears, order is illogical, or the drawer traps or leaks focus |
| Large text and zoom | Increase text size or browser zoom and test portrait and landscape | Labels clip, controls overlap, scrolling is blocked, or the action becomes unreachable |
| Screen reader | Confirm names, roles, expanded state, current-page state, and reading order | An unlabeled icon or incorrect widget semantics hides the structure |
| Slow connection | Load from a cold cache and activate the menu before every asset finishes | JavaScript dependency delays navigation or causes a layout shift |
| Layer collision | Open menu with consent, chat, alert, and sticky action states | Controls cover one another or background content remains unintentionally interactive |
Give the footer, search, and in-page links separate jobs
A layered system keeps the header focused without hiding useful content.
| Layer | Best job | Examples |
|---|---|---|
| Primary header | Frequent, high-value routes for the site’s main audiences | Services, Products, About, Locations when material, Contact, Book, Shop |
| Utility navigation | High-frequency secondary or existing-customer tasks | Login, Pay Bill, Support, language choice, phone, emergency information |
| Contextual links | The next decision from the page someone is reading | Service to relevant project, guide to pricing, location to coverage, comparison to consultation |
| Search | Known-item retrieval across a substantial content or product collection | Help articles, products, documentation, large editorial library |
| Footer | Secondary discovery, business details, policies, and complete-but-curated groups | Accessibility, privacy, terms, careers, social profiles, resource categories, contact details |
| Breadcrumbs | Orientation within a real hierarchy and a route back upward | Home / Services / Website Design, or Blog / Conversion & UX / Current guide |
Search is not a cure for unclear categories, and small sites may not need it. Add it when people look for many named resources, products, support topics, or records and when the business can maintain useful indexing and no-result behavior. Keep navigation available for people who do not know the term the site uses. Search and browse solve different retrieval problems.
Contextual internal links deserve the same editorial care as the menu. The SEO-friendly site architecture guide covers hierarchy, crawl paths, canonical destinations, and topic relationships. Page count should follow distinct customer needs rather than menu capacity; use the small-business page-count guide when a growing header is really signaling an unresolved content model.
Choose a structure that fits the business model
An online store, membership organization, school, clinic, or software product will need a different system. Product categories, account tasks, program finders, patient portals, or documentation can dominate. The method remains stable: identify audiences and tasks, group them in language people recognize, expose the highest-priority routes, and test the complete interaction. Do not copy a five-link agency header onto a fundamentally different service model.
Validate the menu before and after launch
Use evidence without letting analytics make every decision
Run a first-click check
Give representative people a specific task and ask where they would begin. Record their reasoning, not just whether the chosen link eventually worked.
Test labels without visual context
Ask what content someone expects behind each label. Conflicting interpretations signal a wording or grouping problem before development begins.
Review paths, not raw clicks
A highly clicked item may be important, confusing, or simply first. Pair click data with destinations, successful tasks, search terms, exits, support questions, and qualitative feedback.
Check every state
Review desktop, mobile, keyboard, zoom, screen reader, slow loading, current-page indication, logged-in states where relevant, and interactions with banners or overlays.
Maintain an owner
Assign responsibility for retiring services, adding locations, updating policies, repairing broken links, and keeping header priorities aligned with the business.
When navigation problems reflect a deeper mismatch between the site and the business, the work may require new page architecture, content, and components rather than a menu edit. Web Respawn’s website design service can plan those pieces as one customer journey. The conversion and user-experience hub contains related guidance for forms, mobile paths, trust, and calls to action.
How many items should a small-business website menu have?
There is no universal count. Keep the top level limited to clearly distinguishable, high-priority routes that fit comfortably and remain understandable on mobile. Move secondary pages into meaningful dropdowns, contextual links, search, utility navigation, or the footer instead of meeting an arbitrary number.
Should every service appear in the main menu?
Not necessarily. A focused business may expose each core service, while a larger catalog usually needs a Services landing page and customer-recognizable groups. Every important service still needs a crawlable route and relevant contextual links, even when it is not a top-level item.
Should the logo link to the homepage?
That is a familiar and useful convention, so the logo should normally link home and have an accessible name that identifies the organization and destination. A visible Home link can still help some audiences or complex sites; test the complete context rather than assuming the logo is understood by everyone.
Do small-business websites need a search box?
Many small sites do not. Search becomes valuable when the site has a substantial product, support, document, location, or editorial collection and people know what they want to find. If added, maintain indexing, useful result labels, filters where justified, and helpful no-result behavior.
Evidence behind the guide
Sources and further reading
- Menus TutorialW3C Web Accessibility Initiative
- Header component guidanceU.S. Web Design System
- Links crawlable by GoogleGoogle Search Central
- Understanding Success Criterion 2.4.4: Link Purpose (In Context)W3C Web Accessibility Initiative
Continue on Web Respawn
Pages that actually connect to this decision.
These links are selected for the subject of this guide. They are not a generic service dump.
Explore the strategy, content, design, build and launch foundation.
Open page ↗RELEVANT PAGEFind My Website PlanAnswer five questions to identify a practical website starting point.
Open page ↗RELEVANT PAGEWebsite PricingSee current build pricing, required care and what changes the scope.
Open page ↗
