Home › Web Design › Website Navigation
WEBSITE NAVIGATION
Effective website navigation helps people understand where they are, find what’s relevant and move through a site without confusion.
This guide covers navigation end to end: the types of menus, information architecture, hierarchy and labels, dropdowns and mega menus, mobile and responsive patterns, breadcrumbs, internal linking, accessibility, SEO, testing methods and how it all maps onto Elementor.
THE BASICS
Website navigation is the system of menus, links, labels and pathways that helps people move through a site and find information or complete tasks. It’s far more than the header menu: primary and secondary navigation, utility links, the footer, breadcrumbs, sidebars, contextual links inside content, search, pagination and the mobile menu are all part of it.
Good navigation quietly answers five questions at every point: Where am I? Where can I go? How do I get there? How do I get back? What else is related? When any of those goes unanswered, people start guessing — and guessing is where sites lose visitors.
level 1level 2level 3level 4WHY IT MATTERS
Navigation is infrastructure: nobody praises it when it works, and everybody notices when it doesn’t. It shapes both how people experience a site and how easily its content is discovered — though navigation alone never determines search rankings.
Helps people locate relevant content instead of hunting for it.
Makes interactions predictable, so attention goes on content.
Surfaces related pages people wouldn't have searched for.
Supports movement between the steps of a real task.
Provides predictable pathways for keyboard and screen-reader users.
Internal links and structure help search engines understand how pages relate.
TWO DISCIPLINES
Information architecture is the broader discipline: it organises content, decides categories and relationships, and settles the vocabulary. Navigation is how a useful selection of that structure becomes visible and usable.
The distinction matters in practice. Restyling a menu won’t fix content that was never organised coherently — that’s an architecture problem wearing a navigation costume.
NAVIGATION TYPES
Most sites use several of these together. Few need all of them — adding navigation types a site doesn’t need creates clutter rather than clarity.
Main links to the major sections of the site, usually in the header.
Supports a section or category, often shown within it.
Account, login, language, help or settings — tasks rather than content.
Supporting links, policies and details people look for at the end.
Shows where the current page sits within a hierarchy.
Useful for section-based or content-heavy sites.
Links placed inside content where they're relevant.
Moves people between pages of a longer set.
Lets people find content directly, bypassing the hierarchy.
PRIMARY NAVIGATION
Primary navigation carries the site’s main categories and highest-priority destinations. Its value comes from restraint: every item added makes the others slightly harder to see.
A typical bar combines a logo linking home, the primary links, dropdown indicators where submenus exist, sometimes search, a utility link such as login, and occasionally a CTA styled differently from the rest. Not every bar needs all of these.
Keep placement consistent across the site and make the current section visible. There’s no universally correct number of items — it depends on how much content sits behind each one.
SUPPORTING NAVIGATION
Supports a section once someone is inside it — category pages, documentation, resource libraries, account areas or product ranges. It should stay related to the current context rather than duplicating the whole site menu.
Small links supporting tasks rather than content: login, account, search, language, help, contact and settings. They’re usually visually quieter and set apart from the main menu, because they serve a different purpose.
A useful second chance to reach important pages, policies, contact details, resources and secondary categories. Footers work best when they’re organised into a few labelled groups — not when they become an unstructured dump of every URL on the site.
BREADCRUMBS
Breadcrumbs are secondary navigation showing where a page sits in a hierarchy. Most are hierarchical — reflecting structure rather than the visitor’s actual click history — which makes them a reliable way to step back up a level.
They’re most valuable on deep sites where people often arrive mid-hierarchy from search. On a five-page site they add little. On mobile, long trails may need truncating, and the current page shouldn’t be a link. Mark up the trail appropriately and identify it for assistive technology.
Breadcrumb structured data can affect how a result is displayed in search, but it isn’t a ranking mechanism, and not every site needs breadcrumbs at all.
DROPDOWNS
A dropdown reveals child items under a parent. Problems usually come from the same few causes: nesting too deep, opening on hover only, small targets that are easy to overshoot, vague labels, and behaviour that breaks on touch. A dropdown should open predictably by click or keyboard as well as hover, and the parent should make clear whether it’s a destination or just a toggle.
Mega menus expand this into a panel of grouped links, which suits large sites, ecommerce and resource libraries where showing structure beats hiding it. The trade-offs are real: complexity, choice overload, harder keyboard and screen-reader handling, awkward mobile adaptation and more to maintain. Neither pattern is better in general — the amount and shape of your content decides.
MOBILE
The hamburger menu — three stacked lines toggling a panel — is common because space is scarce, and widely recognised for that reason. It’s a pattern, not a requirement: sites with few sections often do better showing links directly, since hidden navigation is navigation people may not look for.
Whichever you choose, the control needs an accessible name, a clear open and closed state, a visible way to close, and focus that moves sensibly into the menu and back again. Inside, keep hierarchy shallow with obvious expand and collapse behaviour, comfortable touch targets, a visible current page and search if the site is large. Sticky navigation can help on long pages, but it eats screen space that’s already limited.
RESPONSIVE
Navigation changes more than any other component across breakpoints, so plan it as part of the overall responsive system rather than bolting on a mobile menu at the end. Typography, spacing, touch targets, dropdown behaviour and where search lives all shift. What shouldn’t shift is access — if something is reachable on desktop, it should be reachable on mobile too. More in responsive design.
HIERARCHY
Hierarchy is the parent-and-child structure behind the menus: major categories, their children, and the relationships between them. Two decisions shape it — how content is grouped, and what each group is called.
Keep grouping logic consistent. If one category is organised by topic and another by audience, people can’t predict where anything lives. And don’t force a site into a fixed depth: a small business site rarely needs three levels, while documentation often needs more.
LABELS
Labels are the smallest part of navigation and among the most consequential. They should be clear, familiar, specific, consistent, concise and aligned with what people expect to find. A label is a promise about a destination — when it’s vague or clever, people either click and feel misled, or don’t click at all.
Use the words your audience uses, not internal terminology. Card sorting, covered later, is a practical way to find out what those words are.
Many choices at each level, fewer levels deep. Everything is visible sooner, but a long menu is harder to scan.
Fewer choices per level, more levels. Each decision is simpler, but content sits further from the entry point.
DEPTH & BREADTH
Breadth is how many choices sit at one level; depth is how many levels there are. They trade against each other: reduce one and the other usually grows.
A typical path runs home → category → subcategory → content. Whether that’s right depends on content volume, how naturally it groups, what people expect and the type of site. There’s no universal maximum depth, and rules like “everything within three clicks” matter less than whether each step feels obvious. Contextual links and search both relieve pressure on the hierarchy without flattening it artificially.
USER JOURNEYS
Navigation exists to support tasks, so test it against real ones rather than admiring the menu in isolation. Someone looking for a service follows a different path from someone comparing articles.
A common flow runs from a landing point, through a category, to relevant content, to an action and a confirmation. Where people get stuck usually reveals a structural problem: a missing category, an unexpected label or a step that assumes knowledge they don’t have.
ARCHITECTURE
Navigation should be designed after the content is understood, not before. A workable sequence: take a content inventory, group items into categories, settle the hierarchy and labels, then design the navigation that exposes it, and finally check it against real user journeys.
A visual sitemap is the planning artefact: a diagram of pages, categories and relationships used to agree structure before anyone builds a menu. It is a different thing from an XML sitemap, which is a file listing URLs to help search engines discover pages. Confusing the two leads to the mistaken belief that submitting an XML sitemap fixes a messy structure — it doesn’t; it just lists the mess.
LINKS & SEO
Internal links come from navigation menus, breadcrumbs, footers, related-content blocks and contextual links inside copy. For visitors they surface relevant pages at the moment of interest; for search engines they signal which pages exist and how they relate. Descriptive anchor text helps both — “responsive design guide” says more than “read more”.
For pages to be discoverable, links need to be crawlable: real anchor elements with href attributes. Menus that only work through scripted interactions may not expose their destinations reliably, so important routes shouldn’t depend on them alone.
An orphan page has no meaningful internal links pointing to it from the navigable structure. It may still exist and even rank, but people can’t reach it by browsing and it’s easy to forget when updating the site.
The fix depends on purpose: link it properly from a relevant section, merge it, or accept that a standalone campaign page is deliberately separate.
Navigation contributes to crawlability, internal linking, page relationships, discoverability, anchor text and overall site architecture. It doesn’t determine rankings on its own — content relevance, quality, technical health and competition all matter more.
Faceted navigation deserves particular care: filter combinations can generate large numbers of near-duplicate URLs, which needs deliberate crawl and canonical management. See our website SEO guides.
ACCESSIBILITY
Navigation is where accessibility problems bite hardest, because a menu that can’t be operated locks people out of the whole site. Cover semantic HTML and navigation landmarks, real links for destinations and buttons for toggles, keyboard operation throughout, visible focus indicators, a logical tab order, announced expanded and collapsed states, accessible names for icon-only controls, a skip link past repeated navigation, adequate contrast and comfortable touch targets.
In keyboard terms that means Tab and Shift+Tab to move, Enter to activate, Escape to close an open menu, and arrow keys within complex menus where appropriate. Focus must not get trapped or jump somewhere unexpected when a menu closes. Nothing important should depend on hover alone. See website accessibility for the wider subject.
FINDING CONTENT
Complements navigation on large sites, documentation, stores and resource libraries. Keep the field visible and clearly labelled, make results scannable, handle empty states helpfully and offer filters where the result set is large. Search should support good architecture, not excuse a poor one.
Filters such as category, brand, price, size and colour let people narrow large sets themselves. The UX benefit is clear; the technical cost is that filter combinations can create many near-duplicate URLs, so crawl and indexing behaviour needs deliberate handling.
Numbered pages give a sense of scale and let people return to a position. “Load more” keeps flow while staying controllable. Infinite scrolling suits browsing but can make footers hard to reach and positions hard to recover. None is universally best.
STICKY NAVIGATION
Sticky navigation keeps the header visible as people scroll, which helps on long pages and deep sites where someone may want to switch sections at any point.
The costs are worth weighing: it permanently occupies viewport space, which matters most on the small screens where space is scarcest; it can obscure content when anchor links jump to a heading; and it needs care so it doesn’t overlap focused elements or interfere with zoom. A slim sticky bar, or one that reappears only when scrolling up, usually balances these better than a tall fixed header.
BY SITE TYPE
The same principles apply everywhere; the structures differ because the content and goals do.
Prioritise services, company information and contact routes. Usually a shallow hierarchy with clear labels.
Organise categories and subcategories, plus search, filters, sorting, cart, account and breadcrumbs. Related products help discovery without deepening menus.
Categories, topics and measured use of tags, with search, archives, related posts and breadcrumbs. Overlapping taxonomies confuse more than they help.
Projects, services, about and contact. Work should be browsable without excessive clicking.
Balance product pages, pricing, resources, login and support across distinct audiences.
Deep hierarchies handled with sidebar navigation, section structure, search, previous and next links, breadcrumbs and an on-page table of contents.
PRINCIPLES
People should understand where a link leads before clicking.
Patterns stay predictable across the whole site.
Related destinations are grouped logically.
Navigation reflects where the visitor currently is.
Important destinations are reasonably easy to find.
Every input method and assistive technology is supported.
Navigation adapts to the space available.
Active and expanded states are visible.
The structure survives content growth.
PITFALLS
Clever or internal wording leaves people guessing at destinations.
A long menu of equal-weight items makes nothing stand out.
Multi-level flyouts are hard to operate, especially on touch.
Menus that move or rename between pages break trust.
Excludes touch and keyboard users entirely.
Cramped menus and tiny targets on the most common device.
Key pages buried where nobody thinks to look.
People lose track of where they are in the structure.
Focus traps and invisible focus make menus unusable.
Dozens of links with no grouping become noise.
Dead ends in navigation erode confidence quickly.
Unpredictable paths make structure harder to understand.
A footer listing every page helps nobody.
Weak results push people back to a menu they'd already given up on.
Content reachable only by direct link or search.
Trails that don't match the real hierarchy mislead.
Menus describing how the business is organised, not the content.
One inaccessible menu can block the entire site.
AUDIT
An audit works best as a walk-through of real tasks rather than a look at the menu. The gap between the structure you intended and the one people experience is where the findings are.
Check labels, order and priorities.
Check categories and relationships.
Walk through the most common tasks.
Test smaller screens and touch.
Test keyboard and focus behaviour.
Find missing or weak connections.
Verify important paths still work.
Review usefulness where it exists.
Look for navigation-related behaviour.
Gather feedback where possible.
RESEARCH METHODS
Three complementary methods answer different questions. Card sorting asks participants to group and sometimes name content, which reveals how your audience expects things to be organised. Open sorting lets them create their own categories, closed sorting asks them to file items into yours, and hybrid approaches sit between. Tree testing then checks whether people can find things in a proposed hierarchy, stripped of visual design — useful because a handsome menu can disguise a confusing structure.
Task-based testing completes the picture on the built site: find the contact page, find the pricing information, find the responsive design guide, find the WordPress resources. Watching where people hesitate exposes confusing labels, unexpected paths, missing categories, excessive depth and over-reliance on search. Card sorting informs architecture rather than dictating it — participants don’t see the business constraints, and results need interpreting.
TESTING
Run through these with a real task in mind rather than as an abstract review. Most navigation problems reveal themselves within the first two or three attempts.
WORKFLOW
Navigation should be planned before a menu is styled. Each step narrows the gap between how the business thinks about its content and how visitors do — and the loop repeats as content grows.
Identify users and their common tasks.
List major pages and content types.
Find the natural categories and relationships.
Create a logical content hierarchy.
Use clear, familiar terminology.
Map the page relationships.
Choose patterns that fit the structure.
Check whether people can find things.
Improve based on evidence and feedback.
COMPONENTS
Wireframing navigation first keeps the discussion on labels, order and grouping before anyone argues about styling. The layout above is illustrative, not a real project.
The component list below covers what navigation systems are usually built from. No site needs all of them — a skip link and breadcrumbs matter on a large documentation site and barely register on a five-page brochure.
Returns to the homepage from anywhere.
The main sections of the site.
Reveals child items under a parent.
Shows many grouped links in one panel.
Shows position within the hierarchy.
Direct access to content.
Compact navigation for small screens.
Section navigation for deep content.
Moves through a set of pages.
Supporting and legal links.
Lets keyboard users bypass repeated navigation.
Returns to the previous level or page.
CONNECTIONS
Campaign pages may keep full navigation, simplify it, use campaign-specific links or drop it. The right choice depends on page purpose, traffic source, journey stage and trust needs — removing navigation doesn't automatically improve outcomes. See landing page design.
Navigation is where visual hierarchy, interaction, labelling, feedback, consistency and user expectations meet. Predictability matters more than novelty. See UI/UX design.
Layout, typography, colour, spacing and content hierarchy all shape whether navigation reads clearly. See website design basics.
Minimal menus, mega menus, sticky headers, mobile-first and search-driven patterns come and go. Judge each against usability and accessibility rather than fashion. See website design trends.
Large menu DOM structures, mega-menu imagery, scripted interactions, third-party widgets and animation all add weight to every page, since navigation appears everywhere. See website speed.
Search, recommendations, personalised paths and conversational interfaces can supplement navigation, but predictable access to key sections still matters. See AI for websites.
WEB VS APP
App navigation borrows from the web and vice versa, but the contexts differ enough that patterns don’t transfer directly — a bottom tab bar suits an app with a few persistent sections more than a content site with dozens. Mobile app patterns are covered in our mobile apps section.
TOOLING
Tool categories rather than rankings. A pen-and-paper card sort with six people often teaches more than an expensive platform used once.
Plan and visualise page structure and relationships.
Sketch menu layouts before styling.
Test menu interactions and flows.
See which paths people actually take.
Observe clicks and scroll behaviour in context.
Check focus order, contrast and landmarks.
Inspect markup, focus behaviour and responsive states.
Run card sorts, tree tests and task studies.
ELEMENTOR
Navigation in Elementor usually lives in a header template applied site-wide, built from containers and flex settings, with a menu widget handling links, dropdowns and the mobile toggle.
Work with global colours and fonts so navigation matches the rest of the site, set typography and spacing per device, and style hover and active states so the current section is visible. Responsive settings control when the menu collapses and how the mobile panel behaves. Custom CSS remains available for gaps, but heavy reliance on it usually signals a structural problem. Interface labels vary between versions, so these are concepts rather than click paths.
ELEMENTOR PRACTICE
Build navigation layouts with real containers rather than nested workarounds.
Keep menu items visually balanced and comfortably spaced.
Make destinations understandable at a glance.
Test desktop, tablet and mobile separately.
Confirm predictable behaviour by click, touch and keyboard.
Review keyboard access and focus visibility.
Keep the structure manageable for visitors and editors.
Real labels wrap differently from placeholder text.
CHECKLIST
A review list rather than an automated audit tool — copy it into your own tracker and work through it with real tasks.
[ ] Main navigation is clear [ ] Navigation labels are understandable [ ] Important pages are discoverable [ ] Categories are logically grouped [ ] Navigation hierarchy is consistent [ ] Dropdowns are usable [ ] Mobile navigation works [ ] Navigation works with keyboard input [ ] Focus states are visible [ ] Current page or state is understandable [ ] Breadcrumbs are useful where appropriate [ ] Search works where needed [ ] Footer links are organised [ ] Internal links are relevant [ ] No important pages are orphaned [ ] Links work correctly [ ] Navigation does not overflow on mobile [ ] Menu interactions are predictable [ ] Accessibility is considered [ ] Navigation has been tested with real tasks
NEXT TOPICS
Learn the foundations of structure, typography, spacing, hierarchy and visual organisation.
Learn how interface and experience principles influence navigation usability.
Learn how navigation adapts across desktop, tablet and mobile.
Learn how navigation choices support focused landing page journeys.
Learn how to make navigation more accessible and usable.
Explore modern navigation patterns and evaluate them against real user needs.
FAQ
Short answers to the questions people ask most about website navigation.
Learn how to organize website content, menus, user journeys and responsive navigation so visitors can find information and move through your website more confidently.