How to Prioritise Links in Website Navigation

There is no magic number of navigation links. Learn how to decide which destinations belong in primary, utility, footer or contextual navigation.

Large websites often have more useful destinations than a navigation menu can present clearly. An ecommerce retailer may have hundreds of categories, services, support pages, store locations and account tasks. A service business may have dozens of specialisms, industries, resources and contact routes.

The usual response is to ask how many links are too many. That is the wrong starting point. Google does not specify an ideal number of links on a page, and a large menu is not automatically a search penalty. The more useful question is whether each link has a clear job, sits in the right part of the site and helps the people who need it find their next step.

This article sets out a practical way to make that decision. You will learn how to list candidate links, connect each one to a user task and page purpose, group related destinations, and decide whether a link belongs in primary navigation, utility navigation, the footer or the page content itself.

Start with the job of the link, not its URL

A navigation inventory usually begins as a list of URLs. That makes it easy for every stakeholder to argue that their page is important. It also produces menus that try to carry the whole website on their shoulders.

Instead, describe every candidate link as a route for a user task. Record:

• User task: what is the person trying to do?
• Page purpose: what does the destination help them understand or complete?
• Audience: who needs it, and how often?
• Business importance: does it support revenue, service delivery, trust, retention or compliance?
• Evidence: what do behaviour, research or search data tell you?
• Maintenance: can the team keep the label, destination and surrounding content accurate?
• Proposed layer: where should the link appear?

This changes the conversation from “Should our page be in the menu?” to “Which user task does this route support, and is global navigation the best way to support it?”

That distinction matters because an important page does not automatically belong in primary navigation. It may be better reached through a category hub, breadcrumb, internal search result, relevant service page or contextual link. Multiple ways of finding content can be useful, provided those routes are understandable and available to the people who need them.

Four navigation layers, four different jobs

Primary navigation, utility navigation, footer navigation and contextual links are not interchangeable containers. Moving a link between them changes its prominence, surrounding explanation and likely audience.

The four-layer model used here is a practical framework, rather than a formal Google or W3C taxonomy. W3C guidance does, however, emphasise meaningful grouping, hierarchy, labels and predictable interaction when navigation expresses a website’s structure. See its guidance on website menus.

Primary navigation: the main recurring journeys

Primary navigation should represent the major areas people repeatedly use to understand or buy from the organisation. It is the clearest expression of the website’s main hierarchy.

For a large outdoor retailer called Trailmark, suitable primary destinations might include:

• Hiking
• Camping
• Running
• Clothing
• Footwear
• Equipment

These are broad enough to represent durable product areas, but specific enough to give users a reasonable expectation of what they will find. They also provide useful starting points for people who are browsing rather than arriving with a particular product in mind.

Primary navigation is not a list of every commercially important page. A seasonal gift guide may generate strong sales without deserving a permanent top-level position. A specialist repair service may matter greatly to a smaller audience but still be easier to find through product-support pages, the footer and search.

This is a judgement about hierarchy, not a recommendation to hide important content. If a destination supports a core customer task, it needs a clear route. That route does not always need to be a global top-level link.

Utility navigation: important functions around the main journey

Utility navigation supports tasks that sit around the main content hierarchy. Common examples include account access, delivery information, store locations, customer support, returns and contact details.

For Trailmark, “Find a store”, “Help”, “Track an order” and “Account” may belong in a utility area. They are important, but they describe functions rather than the retailer’s main product structure.

Utility placement is not a demotion. Someone tracking an order may need that link more urgently than someone browsing footwear. The point is to give the task a predictable home without making every operational function compete with the main product categories.

Some businesses will find that a utility task deserves primary prominence. For a local service provider, “Emergency support” may be more important than a general “Services” menu. The layer should follow the user journey, not a rigid template.

Footer navigation: supporting routes and reassurance

Footer links are useful for supporting information, organisational details and secondary routes. They often include delivery and returns, accessibility information, careers, investor information, terms, privacy, sustainability and store information.

The footer is also a useful place for destinations that need to be available but do not belong in the main browsing hierarchy. It should not become a storage cupboard for unresolved decisions.

Moving a core customer task into the footer does not make the architecture clearer. If customers regularly need a service, product area or support route, ask whether the destination needs a more visible route elsewhere as well.

Contextual links: the next step on the current page

Contextual links appear where the page explains why the next destination is relevant. A product-care guide might link to repair services. A hiking boots category might link to a guide on choosing waterproof footwear. A delivery page might link to returns information.

These links can be more helpful than a generic global menu because the surrounding content gives them meaning. Research into hyperlink information scent describes the cues that help users predict whether a link will take them towards their goal. The cited research discusses how link wording and surrounding context affect link selection, although the effect will vary by audience, device and task.

Contextual links should still use descriptive wording. “Learn more” tells the user very little. “Compare waterproof hiking boots” gives a stronger indication of what happens next.

A worked prioritisation exercise

Imagine Trailmark is redesigning its global navigation. Stakeholders submit this list of candidate links:

• Hiking
• Camping
• Running
• Waterproof jackets
• Trail shoes
• Sale
• Gift cards
• Find a store
• Delivery and returns
• Order tracking
• Repairs
• Size guide
• Buying guides
• Gift guide
• Brand directory
• Sustainability

The first pass should not ask which six, eight or 12 links fit on desktop. It should ask what each destination is doing.

Hiking, camping and running are durable browsing areas. They can form primary navigation because they represent recurring user needs and organise more specific categories beneath them.

Waterproof jackets and trail shoes may be valuable product categories, but they are narrower destinations. They could sit beneath Clothing or Footwear, appear in a seasonal campaign, or receive contextual links from relevant buying guides. Promoting them to global navigation would make the menu reflect current commercial emphasis rather than the site’s durable structure.

Order tracking, delivery and returns, and Find a store support practical customer tasks. They are strong utility candidates. Their value may not show up as large browsing volume, but that does not make them unimportant.

Gift cards and the gift guide may be seasonal. A temporary campaign link or a prominent homepage module may be more appropriate than permanently expanding the main menu.

Repairs, size guide and buying guides need more context. A size guide may be most useful beside products and in the help area. Repairs could appear on product pages, in support navigation and in the footer. Buying guides might form a content hub, with links from category pages and related products.

Brand directory and sustainability may be valuable supporting destinations without being primary browsing routes. Their placement depends on audience need and business purpose, but neither should be added to the main menu simply because the pages exist.

The resulting structure might look like this:

• Primary: Hiking, Camping, Running, Clothing, Footwear, Equipment
• Utility: Account, Order tracking, Help, Find a store
• Footer: Delivery and returns, Repairs, Gift cards, Sustainability, Brand directory, legal and company information
• Contextual: Waterproof jackets, trail shoes, size guide, buying guides and gift guide where the current page makes them relevant

This is not a universal answer for outdoor retail. It is an example of the reasoning. The same destination could move layers if the evidence showed that it supports a different task for a different audience.

What evidence should inform the decision?

A sensible navigation review combines several types of evidence. None should be treated as a vending machine that produces the correct menu.

Analytics path exploration

Path data may show common routes, repeated backtracking, exits and associations with conversion events. It may reveal that users regularly move from a category to a buying guide before purchasing, or that people repeatedly return to a store locator.

It cannot, on its own, explain why a route occurs. High clicks may reflect strong usefulness, high prominence, confusion or a lack of alternatives. Low clicks may mean that the link is unnecessary, or that it works perfectly for a small but important audience.

Internal site search

Site-search data may reveal the words customers use, topics they struggle to locate, zero-result searches and demand for destinations that the navigation does not make obvious.

Search frequency is not a direct instruction to promote a page. People may search because it is faster than browsing. Search logs also contain duplicates, misspellings and one-off needs. Use this evidence to improve labels and identify gaps, then test whether the destination belongs in the global hierarchy.

Page importance and conversion paths

Review revenue, leads, retention, support volume, assisted conversions and high-consequence tasks. A low-volume compliance or support page may deserve a reliable route even if it will never compete with a major category for clicks.

Conversion paths show that pages are associated with important outcomes. They do not prove that a particular menu position caused those outcomes. Attribution settings, entry points and campaign activity all affect the result.

Search demand

Search demand can help identify familiar labels and commercially relevant destinations. It should be one input rather than the deciding rule.

A high-volume search term may describe a narrow product, a one-off information need or language that makes sense in search but not as a top-level category. Conversely, a strategically important service may have modest search demand because customers discover it through referrals, sales teams or existing relationships.

User research and findability testing

Card sorting can help people show how they group destinations and interpret labels. Card sorting is useful for investigating possible groupings, but its results depend on the participants, wording and format.

Treat the output as a hypothesis. Follow it with tree testing, task-based testing or live behavioural evidence. Ask people to find a destination and observe whether they choose the expected route, whether the label makes sense and whether they remain confident after selecting it.

Crawl and internal-link data

Technical data can confirm whether important destinations remain reachable, whether a template change has created broken links or redirects, and whether the released navigation matches the intended implementation. Google recommends crawlable links with useful anchor text and routes to important pages.

That evidence validates technical access. It does not prove that users understand the hierarchy or can find the right destination. A link can be perfectly crawlable and still be a poor navigation choice because it distracts users, has an unclear label or gives a core task no obvious role.

Why link count and PageRank are poor decision rules

There is no universal maximum number of menu links. A small, well-labelled menu can be confusing, while a broad menu can work when its categories are specific, meaningful and well grouped. Controlled ecommerce research found that broader menus were not automatically worse in every situation, and also highlighted differences between users who prefer browsing and those who prefer site search.

That does not mean breadth is free. More choices can make hierarchy, labels, responsive behaviour and maintenance harder. A menu with 40 links may be appropriate for a complex organisation, but only if users can understand the groups and the interaction works across devices and assistive technologies. The evidence supplied here does not establish a universal link count at which task performance fails.

It is also too simplistic to say that every extra internal link directly weakens rankings. The original PageRank paper describes a mathematical link-graph model, but it does not justify a modern rule that each added menu link reduces a page’s search value by a fixed amount. Internal links can help discovery and understanding, but the practical decision here is primarily about hierarchy, findability, user tasks and maintainability.

Use SEO data to check that important pages remain accessible and that the implementation reflects the intended structure. Do not use an arbitrary link limit as a substitute for deciding what the website is actually trying to help people do.

Implementation: make the decision safe to release

Once the proposed layers are agreed, record an owner for each navigation area. Someone should be responsible for labels, destinations, seasonal changes, redirects and review dates. Without ownership, temporary campaign links have a habit of becoming permanent residents.

Check the CMS and component constraints before promising a neat hierarchy. A shared header may affect every product, service and editorial template. One global change can alter thousands of pages, especially where menus are inherited through templates or rendered by a common component.

Design and test desktop and mobile states separately. An expandable desktop mega-menu may become a long accordion on mobile. Check keyboard operation, focus order, visible focus, expanded and collapsed states, accessible names and whether users can tell where a link will go. W3C guidance on menus covers meaningful grouping, hierarchy, labels and predictable interaction.

Before release, confirm:

• the visible label matches the page purpose;
• every link reaches the intended destination;
• removed links have an appropriate replacement, redirect or deliberate removal;
• important pages still have understandable routes;
• the menu works across affected templates and devices;
• the links are available in the rendered experience where required;
• analytics events and search tracking still work;
• owners know how seasonal and temporary links will be reviewed.

After release, compare task completion, search use, navigation paths, exits, conversion-assisted journeys, support contacts and internal-link coverage with the pre-change baseline. Segment the results by device, audience and entry point where possible. Technical crawls can check links, redirects, errors and affected templates, while user testing and behavioural evidence are needed to assess whether the new hierarchy makes sense.

How to make the decision on a small or large site

A small site may be able to complete this exercise in a workshop. List the candidate destinations, write down the user task for each, group them, test the labels with a few people and review the result on desktop and mobile.

A large site needs more control. Use template-level analysis to understand which navigation components affect which URL groups. Combine analytics, internal search, conversion data, search demand, content ownership and crawl data. Document exceptions for seasonal campaigns, specialist audiences and high-consequence support tasks. Plan a staged release if the navigation is shared across thousands of pages.

In both cases, the principle is the same: do not optimise for a target number of links. Optimise for a hierarchy that helps people understand their options, reach important destinations and take the next sensible step.

Conclusion: navigation is a set of routes, not a URL cupboard

The strongest navigation decisions begin with user tasks and page purpose. Primary navigation should express the main recurring journeys. Utility navigation should support practical functions. Footer navigation should provide reliable secondary routes. Contextual links should explain the next relevant step within the current page.

There is no universal menu limit, and a technically crawlable link is not automatically a good navigation choice. Review evidence from behaviour, search, business outcomes, research and technical implementation, then test the decisions that remain uncertain.

If your site has grown through product launches, service expansion or repeated redesigns, start by documenting the destinations that are competing for the same space. Assign each one a task, purpose, audience and evidence trail before deciding where it belongs.