A website navigation checklist for Malta businesses should begin with customer tasks, not with a debate about how many menu items fit in the header. Good navigation helps visitors understand what the business offers, where they are and how to reach the next useful page on a phone, desktop or assistive device.
This guide is for businesses planning a new site or redesign. It covers information architecture, menu labels, hierarchy, mobile behaviour, accessibility, breadcrumbs, search and approval testing without duplicating the separate work of contextual internal linking.
1. List the tasks visitors need to complete
Start with the reasons people visit the website. A navigation structure based only on the company organisation chart can make sense internally while remaining confusing to customers. Define the main audience groups and the task each group should be able to complete.
- Understand the main services or product categories.
- Check whether the business serves their location or sector.
- Compare options, specifications or packages.
- Find evidence, case studies or relevant experience.
- Understand the process, requirements or next steps.
- Request a quotation, book a call, buy or contact support.
- Find policies, company details or existing-customer resources.
Prioritise tasks rather than trying to give every page equal prominence. The primary navigation should support the most important and frequent journeys. Secondary, footer and in-page navigation can serve less common tasks.
A sitemap is the complete page hierarchy. The main menu is only one interface into that hierarchy. Build the sitemap first so decisions about missing, overlapping and misplaced pages are not constrained by a header design.
- Give every planned page a working title and purpose.
- Group pages by customer need or topic.
- Identify parent pages that introduce each section.
- Mark pages required for navigation, search, campaigns or compliance.
- Flag pages that may be consolidated, redirected or removed.
- Define the expected URL and breadcrumb path.
- Record the content owner and approval status.
The website discovery workshop guide helps align audiences, goals, scope and decision-makers before the sitemap is approved. The website content checklist can then identify the material needed for every page in the structure.
3. Choose labels customers can predict
Menu labels should tell visitors what they will find after selecting them. Internal department names, slogans and invented categories create unnecessary interpretation. Use the words customers use when asking about the service or product.
- “Web Design” rather than “Create”.
- “Services” rather than “What We Do” when space is limited and the destination is a service overview.
- “Industries” when the pages are genuinely organised by sector.
- “Resources” only when the section contains several useful resource types.
- “Contact” or “Book a Consultation” when the destination and action differ.
- A specific account or support label for existing customers.
Avoid several links with the same vague text when they lead to different destinations. W3C guidance on link purpose recommends descriptive wording or clear context so users can determine what a link will do before following it.
4. Keep the hierarchy shallow enough to understand
There is no universal number of levels or menu items that fits every site. The correct structure is the smallest hierarchy that represents the catalogue or service range without creating an overloaded top level. A visitor should not need to open multiple vague categories to discover where a page belongs.
- Use top-level categories that are distinct from one another.
- Avoid a category that contains only one child page unless it has a useful overview role.
- Do not repeat the same destination under several labels without a clear reason.
- Keep related services together and separate unrelated audiences.
- Use landing pages to orient visitors within larger sections.
- Review whether each nested level adds meaning or only hides content.
Google recommends organising a site logically so users and search engines can understand how pages relate. It also notes that descriptive URLs and topical directories can communicate structure. Navigation planning should therefore align menu hierarchy, page hierarchy, URLs and breadcrumbs rather than treating them as separate systems.
5. Define desktop and mobile behaviour together
Mobile navigation is not the desktop menu squeezed into a smaller space. Decide how the same structure will be revealed, how nested sections open and how users return to a parent level. Keep wording, order and destination consistent across screen sizes wherever possible.
- Provide a clearly labelled menu control.
- Show whether the menu is open or closed programmatically.
- Keep tap targets large enough and separated from adjacent controls.
- Avoid hover-only access to essential destinations.
- Make submenu parent items understandable and operable.
- Preserve a logical order when the layout changes.
- Do not hide critical contact or purchase actions only on one device.
- Test the menu with zoom and narrow viewport widths.
W3C advises that responsive menu structure should remain consistent across screen sizes, even where some items are collapsed into subnavigation. Items that remain visible should keep the same order, wording and destination.
6. Make dropdowns and fly-outs operable
Dropdowns can reduce visual clutter, but they add interaction risk. Users must be able to open, navigate and close them using a mouse, touch and keyboard. Submenus should not vanish unexpectedly when a pointer moves slightly outside a narrow area.
- Use a button for a control that opens a submenu when the label itself is not a destination.
- Communicate expanded and collapsed state to assistive technology.
- Keep keyboard focus visible.
- Use Escape or another documented method to close expanded navigation where appropriate.
- Avoid forcing diagonal pointer movement through fragile hover areas.
- Return focus logically after a menu or modal navigation closes.
- Confirm that links remain ordinary crawlable links where they are destinations.
The W3C Menus Tutorial highlights semantic structure, appropriate labels, recognisable states and mouse and keyboard operation. Adding ARIA attributes does not create the required behaviour by itself; the implemented interaction must also work.
7. Show visitors where they are
Orientation becomes more important as the site grows. The current menu item, page heading, URL and breadcrumb should tell a consistent story about the visitor’s location.
- Visually distinguish the current section or page without relying on colour alone.
- Use an accurate page heading that matches the selected destination.
- Provide breadcrumbs on sites with meaningful hierarchy.
- Keep the current page as the final breadcrumb item.
- Link parent breadcrumb levels to usable overview pages.
- Label breadcrumb navigation so assistive technology can distinguish it from the main menu.
W3C documents breadcrumbs as one way to help users understand their position and move up through a hierarchy. Google also supports Breadcrumb structured data, which can help it understand the page’s position in the site hierarchy.
8. Provide more than one useful route on larger sites
A single main menu may not suit every visitor. People arrive on deep pages, search with different words and use different strategies. Depending on the site, combine navigation with search, breadcrumbs, contextual links, category pages, filters or a sitemap.
- Site search for content or catalogues that are too large to browse efficiently.
- Breadcrumbs for hierarchical orientation.
- Contextual links to related services, products or guidance.
- Category and hub pages that explain available options.
- Filters for product or resource collections.
- A footer containing important support, company and policy destinations.
- An HTML sitemap when it serves a real user need.
WCAG guidance on multiple ways explains that users benefit from more than one method of locating pages. The right combination depends on the site size and task. A small brochure site may need little more than clear global links, while an ecommerce catalogue may require search, categories and filters.
The main menu explains where content lives. A call to action asks the visitor to take a business step. They can appear together, but should not compete or create several visually identical “primary” actions.
- Select one primary action for the header.
- Use wording that reflects the destination, such as “Request a Quote” or “Book a Call”.
- Do not replace essential service navigation with campaign slogans.
- Keep the primary action available without obstructing content on mobile.
- Make telephone, email and form routes appropriate to the visitor’s stage.
- Ensure the action lands on a page that continues the promise made by the label.
A multilingual Malta website needs more than translated menu labels. Each language version should have an intentional structure, clear language switching and appropriate destination mapping. Do not send every language switch to the homepage if an equivalent page exists.
- Use the language name in a form users recognise.
- Keep language choices available in a consistent location.
- Map equivalent pages where content exists.
- Explain unavailable translations rather than creating broken or misleading links.
- Review label length in every supported language.
- Test right-to-left behaviour if relevant.
- Keep the selected language through the user journey.
Use the multilingual website checklist for language URLs, translation workflow, metadata and search considerations beyond the navigation itself.
A stakeholder approving a sitemap is not evidence that customers can use it. Test representative tasks with people who were not involved in designing the hierarchy. Ask them where they would go, then observe rather than guiding them.
- Find the service that solves a named customer problem.
- Find pricing or learn how a quotation is obtained.
- Reach a sector-specific or location-specific page.
- Find returns, privacy, support or contact information.
- Move from a deep page back to its parent section.
- Complete the task using only a keyboard.
- Repeat the task on a narrow mobile screen.
- Use search or an alternative route when the menu is not the preferred method.
Record hesitation, wrong turns, labels participants interpret differently and destinations they expect but cannot find. Update the hierarchy before visual refinement. After implementation, use the website testing checklist for browser, device, form and link verification.
12. Protect existing URLs during a redesign
Changing navigation does not always require changing URLs. If the redesign removes or renames pages, map every affected old URL to an appropriate destination and preserve valuable content and internal links where justified. Do not redirect unrelated removed pages to the homepage.
The website redesign SEO checklist covers URL mapping, redirects, indexability and post-launch monitoring. The internal linking checklist complements this guide by auditing contextual links, orphan pages and anchor text outside the global menu.
- List the main audiences and tasks.
- Create the complete sitemap before styling the header.
- Give every page a unique purpose and owner.
- Group pages by customer need, not only internal departments.
- Use specific and predictable menu labels.
- Keep the hierarchy meaningful and avoid unnecessary levels.
- Define consistent desktop and mobile behaviour.
- Make menus usable by touch, mouse and keyboard.
- Show current location through headings, state and breadcrumbs.
- Provide alternative routes where site size requires them.
- Separate structural navigation from the primary call to action.
- Map multilingual equivalents intentionally.
- Test representative tasks with uninvolved users.
- Map redirects and preserve valuable URLs during redesign.
A practical brief should contain the audience groups, top tasks, sitemap, menu labels, primary action, mobile behaviour, dropdown rules, breadcrumb requirements, site-search requirements, language handling, existing URL mapping and acceptance tests. This gives designers and developers evidence-based requirements instead of asking them to “make the menu easy”.
Digital Consulting Pros provides web design and development services in Malta. A navigation workshop can turn an existing page inventory, analytics evidence and customer tasks into a testable sitemap before design and development begin.
Official sources
- W3C Web Accessibility Initiative: Menus Tutorial
- W3C Web Accessibility Initiative: Menu Structure
- W3C: Understanding Focus Order
- W3C: Understanding Multiple Ways
- W3C: Understanding Link Purpose
- Google Search Central: SEO Starter Guide
- Google Search Central: Breadcrumb structured data
Featured image: Photo by UX Indonesia on Unsplash.
