Websites with Many Services: Choosing What Belongs in the Footer Instead of the Main Menu

On a website with many services, keep the main menu focused on the routes visitors need to understand the offer and move towards a relevant decision. Use the footer for useful secondary routes, practical information and selected repeat links that help people continue at the end of a page.

The choice is about the role of each destination in the visitor’s task. It is not a ranking of which department matters most. A careers page can be essential to applicants and still need a different place from the services a prospective customer is comparing. A contact route may deserve a place in both areas.

Give the main menu a clear job

List the principal tasks for the site’s intended audience. A prospective customer may need to understand the service groups, check relevant experience, learn how an engagement works and make contact. The main navigation should make those routes recognizable.

A website can offer many services without displaying every service name in its top-level menu. A useful Services overview can introduce coherent groups and lead to the detail. Where a group represents a distinct, important starting point, a direct main-menu link may be justified.

Do not choose the number of items by applying an arbitrary limit. Review whether the choices are distinguishable, whether the labels fit at relevant screen sizes and whether visitors can predict the destinations.

If the menu feels crowded because several labels describe similar work, first resolve the overlapping service names. Moving one ambiguous label into the footer leaves the underlying confusion intact.

Decide the role of each link before its position

Create an inventory containing the destination, the visitor who needs it and the situation in which they are likely to look for it. Then assign its primary role: orientation, comparison, evidence, action, support or background information.

Use that role to discuss placement. A policy page helps someone check how the site operates. A service overview helps someone understand what they can commission. A project case study supports a decision within the relevant service journey. They do not all need identical visibility.

This table gives starting points to test:

Destination	Likely placement	Reason to reconsider
Main service groups	Main menu or a clear Services overview	A group is a major entry task and deserves a direct route
Individual specialist services	Relevant group pages and contextual links; selected footer links if useful	Visitors repeatedly struggle to reach a frequently needed service
Contact	An obvious route in the main journey, often repeated in the footer	Different audiences need clearly separated contact destinations
About and relevant credentials	Main menu or supporting routes according to their role in choosing the business	Understanding the people is a major part of the buying decision
Careers	Footer or a clearly named utility area on a customer-focused site	Recruitment is a primary purpose of the site
Policies and site information	A predictable footer group	Relevant information must also appear near a specific action
A temporary campaign page	Links from the campaign and related content	The offer becomes part of the enduring service structure

These are planning suggestions, not universal rules. A recruitment business, for example, may need applicant routes in its main menu. Placement should follow the site’s actual audience and purpose.

Keep essential service information near the decision

The footer should not become the only location for information someone needs before choosing a service. Eligibility, coverage, material limitations and the next step belong in the relevant service journey as well.

For instance, a business that serves only commercial premises should make that clear where a visitor evaluates the offer. Hiding the condition in a footer paragraph can leave the main page creating an inaccurate impression.

The same applies to contact details when contact is urgent or central to the task. Repeating a useful route in the footer can help a reader at the end of the page; it does not replace a visible route at the point where they are ready to act.

The homepage content checklist helps identify which questions the page must answer before a visitor moves on. Place those answers in context, then use the footer as additional support.

Build footer groups around recognizable purposes

Choose short group headings that make the links easy to scan. Depending on the site, useful groups might include Services, Company, Resources and Site Information. Use only groups that contain relevant destinations; a collection of nearly empty columns adds little clarity.

A footer can repeat selected principal links and add information that does not need top-level prominence. The GOV.UK Design System’s footer examples illustrate navigation groups alongside practical links such as help and terms. They are a reference for organizing information, not a reason for a commercial website to copy GOV.UK branding or components.

Give each link a name that makes sense in its group. “Support” could mean help with a purchased service, technical assistance or donations; clarify the meaning when the surrounding context does not.

Review the actual volume of content. If there are dozens of service links, a complete directory page may be more usable than repeating the entire list at the bottom of every page. The guide to category filters and simpler lists of links helps choose how that directory should work.

Allow purposeful repetition

A link can belong in both the main menu and the footer. Contact, the service overview and a useful work archive often support different moments in the same journey. Repetition is helpful when it gives someone a convenient next step without forcing them to retrace the page.

Keep repeated labels and destinations consistent. If “Services” means the full overview in the header, using the same label for one selected package in the footer creates an avoidable surprise.

Contextual links add a third layer. A paragraph about a specialist offer can link directly to its detail even when the top-level menu presents a broader group. That can be more helpful than asking the visitor to return to a menu and reconstruct the route.

Google’s link guidance supports descriptive links placed where related information is useful. A large footer full of loosely related keywords is not a substitute for a meaningful content structure.

Test the footer as part of the mobile experience

Check how the footer reads after its columns stack on a narrow screen. Group headings should remain meaningful, links should be comfortable to select and text should remain readable. A footer should not become visually inaccessible simply because it contains supporting information.

If groups can be collapsed on mobile, specify how they open and close, how their state is communicated and how a keyboard user reaches the links. Do not add disclosure controls automatically when a short, visible list is already easy to use.

Keep the identity of destinations consistent across screen sizes. W3C’s menu structure guidance recommends consistent wording, ordering and destinations for menu items that remain visible in responsive layouts. A mobile footer should still describe the same website.

Also check whether visitors can actually reach the footer. A collection that continuously loads more content can make a bottom-of-page destination awkward to access. Important support and contact routes may need another predictable location within that experience.

Test what happens when a visitor cannot find a route

Review the complete journey from more than the homepage. Someone may arrive directly on a service article or case study, read it and then need to identify the business, compare an offer or ask a question.

Give a suitable newcomer a task without telling them to use the footer: “Find out who you would contact about this service,” or “Check whether this business explains its process.” Observe where they look, which labels they interpret and whether the destination answers the question.

A failed task does not automatically mean the link must move into the main menu. The label may be unclear, the destination may lack the answer or the relevant page may need a contextual link. Record the cause before selecting the change.

The website navigation planning guide provides a wider review framework, including mobile and keyboard behaviour. Keep observations about findability separate from claims about sales or search rankings.

Keep a short record of navigation decisions

Document each main-menu and footer destination with its label, purpose, owner and reason for placement. Record intentional repetition and the routes into specialist service pages. This makes later additions easier to assess.

When a new service launches, ask where it fits in the agreed structure before adding another top-level item. When an offer ends, review its page and existing links together. A footer should not quietly collect every destination the team was unsure about.

Revisit placement when there is meaningful evidence: repeated enquiries for hidden information, a change in the business’s priorities or task reviews showing a route is hard to find. A low click count alone does not make a policy or support link unnecessary; consider the need it serves.

Common questions about footer navigation

Should every service appear in the footer?

No. Include the destinations that make the footer useful, and provide a clear route to a complete services overview when the list is extensive. Specialist pages can be introduced through relevant service groups and contextual links.

Is it a mistake to put Contact in both the menu and footer?

No. Contact can be useful at the start and end of a visit. Keep the destination and wording predictable, and distinguish separate contact routes only when they serve genuinely different needs.

Will moving links to the footer improve SEO?

There is no automatic improvement from that move. The question is whether useful pages remain clearly connected and understandable. Choose placement for the visitor’s task, then verify that the links lead directly to the correct destinations.

Give every service a clear route through the website

SavianoDesign’s Web Design service brings content structure, navigation and responsive layouts together for a complete homepage or website redesign. Explore the Web Design portfolio for examples of focused page hierarchy and connected content.

Contact SavianoDesign about your website with the current URL, your service groups and the information visitors struggle to find. Those details help define a navigation brief around real decisions.