What Should Your Website Footer Link To? A Practical SEO and UX Guide

A practical guide to deciding which pages belong in your website footer, how to group and label them, and how to avoid turning sitewide navigation into a list of keyword targets.

Your website footer has become crowded. One team wants links to every regional office, another wants its latest campaign included, and someone has added a row of service pages because each one has a keyword target.

The result is usually a footer trying to do too many jobs at once. It may contain useful legal and support links alongside a second copy of the main navigation, a location directory, old campaigns and phrases written more for search engines than customers.

The practical question is not “How many footer links are too many?” There is no universal number supported by the available evidence. A better question is: what does this link help a user do, and is the footer the clearest place for that task?

This guide sets out a user-first way to decide. It covers the types of pages that commonly belong in a footer, how to group and label them, where SEO fits into the decision and how to govern changes to a sitewide template.

The footer is a fallback and support layer

A footer is a recognised page region. It commonly contains sitewide information such as copyright, privacy statements and disclaimers, as the W3C page-structure guidance explains.

That does not mean every footer should be a narrow strip containing only legal text. On a larger website, it can also provide a secondary route to important destinations that do not belong in the primary navigation. This is an information-architecture interpretation of the footer’s role, not a finding that expanded footers improve conversion, rankings or usability for every site.

Think of it as a fallback and support layer. The header should help most visitors begin their journey. The footer should help people who need a useful route that is secondary, operational, trust-related or too broad for the main menu.

This distinction matters. A footer can be useful without becoming a complete sitemap, and a complete sitemap may be better handled as a separate page or directory. Exploratory research on company footers and the Nielsen Norman Group’s work on site-map usability support treating these as related but different functions. They do not establish a universal boundary between footer navigation and a sitemap.

For a broader explanation of how navigation fits into the wider architecture, see our guide to customer-friendly, SEO-aware website structure.

Which types of links commonly belong in a footer?

There is no universal footer template. The right contents depend on your audience, business model, site hierarchy and the tasks people need to complete. The following categories are a useful starting point, not a prescription.

1. Essential utility

These are routes people may need from almost anywhere on the site, even if they are not part of the main commercial journey.

• Sign in or account access
• Accessibility information
• Language or market selection
• Contact details
• Site search, where it is useful as a distinct route

Whether each item belongs in the footer depends on the site. Account access may deserve a prominent header link for a customer portal, while accessibility information may be more discoverable in the footer. The point is to support a recognisable task, not to place every operational destination in the same area.

2. Trust and legal information

Privacy, cookies, terms, complaints procedures, modern slavery statements and regulatory information often need to be available sitewide. They may not be persuasive entry points for a new customer, but they can matter to existing customers, partners, staff and regulators.

These links also explain why repeated sitewide links are not automatically a problem. A privacy policy or accessibility statement has a clear purpose when it appears across the site. Its value does not depend on having a commercial keyword in the link text.

3. Customer support

Support routes can include help centres, delivery information, returns, service status, documentation, complaints and frequently asked questions. A visitor who has reached the bottom of a page may be looking for reassurance or a way to resolve a problem rather than another sales page.

Keep the label aligned with the destination. “Help centre” is useful if it leads to support content. “Customer solutions” is less helpful if it is simply a renamed contact page.

4. Secondary navigation

Some useful destinations are important but do not need to compete with the primary navigation. Examples include an about section, careers, press information, investor information, partner resources or a professional community.

These links are especially defensible when they represent a real audience need and have a stable place in the organisation’s structure. They should not appear merely because a team wants another page promoted across the site.

5. Important site destinations

A footer may provide a route to a resource hub, location directory, product finder or another destination that helps users choose where to go next.

For example, a national rail booking service might link to Find a station rather than listing 80 individual stations in the footer. The directory is a useful destination in its own right. It gives people a route into the selection process without turning the footer into a wall of place names.

That is an inference from information-architecture principles, not a universal rule. If a business has three locations and customers regularly need direct access to each one, three clearly labelled location links may be more useful than an extra directory step.

Use the footer to reflect hierarchy, not keyword targets

A page can have a keyword target without deserving a permanent sitewide link. Search demand can inform how you design navigation, but different search phrases do not automatically require separate destinations or footer links.

Suppose the fictional rail service in our example has pages for:

• Train tickets
• Season tickets
• Station information
• Accessible travel
• Weekend travel offers

Each page may be useful. That does not mean all five belong in the footer. “Train tickets” may be a primary navigation item. “Accessible travel” may belong under passenger information and in the accessibility route. “Weekend travel offers” may be temporary campaign content that should not become a permanent sitewide link.

The footer should express the site’s hierarchy rather than flatten it. If every page receives the same persistent treatment, users lose the distinction between core journeys, support information and occasional promotions.

Our guide to how search demand should influence site navigation explores this wider relationship between demand, user needs and information architecture.

Group links around real user tasks

People use labels and surrounding links to form an expectation about what a navigation group contains. A group labelled “Support” suggests that the links underneath will help with an existing service or problem. “Explore” is less useful if it contains a mixture of careers, privacy and regional offices. Information-scent research supports the broader principle that labels should accurately signal the likely content or task behind a link, although it does not establish a fixed vocabulary or footer layout. See, for example, this information-scent study.

W3C guidance for navigation regions recommends meaningful labels and distinguishable navigation areas, including for users of assistive technologies. You can read the relevant example in the ARIA Authoring Practices Guide.

Useful groups might include:

• Help and support: Help centre, Contact us, Service status
• About: About us, Careers, Press
• Resources: Guides, Reports, Events
• Legal and trust: Privacy, Cookies, Terms, Accessibility
• Find your way: Find a location, Select your market, Site map

These names are illustrative. A group should reflect the language your audience understands, not the internal departments that happen to own the pages.

On a smaller website, fewer groups may be clearer. A footer containing four well-chosen links can be more useful than one containing 40 links split into eight tiny columns. That is a design judgement, not an evidence-backed threshold. On a complex organisation’s website, a broader footer may be justified if the categories remain understandable and maintained.

Write labels that tell people where they will go

Link wording is part of the navigation experience. Descriptive, concise labels help users predict the destination, and Google’s guidance also recommends concise, relevant anchor text that gives context about the linked page. See Google’s guidance on crawlable links.

Accessibility guidance makes the same basic point from another direction: users should generally be able to identify a link’s purpose from its wording, particularly when links are encountered outside their surrounding visual context. The WCAG guidance on link purpose discusses this principle. It is a Level AAA success criterion, so treat it as strong practice rather than implying that every implementation is automatically a legal or conformance failure.

Compare these examples:

• Better: Find a station
• Weaker: Stations
• Better: Customer help centre
• Weaker: Solutions
• Better: Regional offices
• Weaker: Locations near you

The better labels are not better because they contain more keywords. They are better because they describe the likely task or destination.

Do not turn this into an excuse for keyword stuffing. A footer with links such as “cheap train tickets London”, “cheap train tickets Manchester” and “cheap train tickets Birmingham” may look optimised, but it gives users little sense of the site’s structure. Google’s spam policies warn against links created primarily to manipulate rankings, including unnatural or keyword-heavy patterns. That does not mean every repeated footer link is risky. Purpose and context matter. See Google’s spam policies for the distinction.

A practical test before adding a footer link

Before a team adds a link, ask these questions:

1. What user task does this support? Can you describe the task in ordinary language?
2. Who needs it? Is it relevant to most visitors, a distinct audience or a recurring support need?
3. Why does it need to be sitewide? Would a page-level link, main navigation item or directory be more appropriate?
4. Is the destination distinct? Does it provide a genuinely different route or simply repeat another page with slightly different wording?
5. Is the label clear? Would someone understand the destination without knowing your internal terminology?
6. Will it stay useful? Is this a stable destination, or a campaign that may be forgotten after the promotion ends?
7. Does the group make sense? Will the link sit beside other destinations with a similar purpose?

If the only convincing answer is “the page has a valuable keyword”, the link probably has not earned its place.

This test is a decision aid, not a scoring model. You do not need to force every page into a yes-or-no formula. The aim is to expose weak reasons before they become a template change.

Before and after: a footer that has lost its purpose

Imagine the rail service’s original footer contains these links under one heading:

Train tickets | Cheap train tickets London | Cheap train tickets Manchester | Weekend rail deals | Station information | Accessible train travel | Careers | Privacy | Contact | Investor relations | Train tickets for families

There are legitimate destinations here, but the group gives no indication of how they relate. It mixes commercial journeys, audience-specific information, corporate content and legal essentials. Several labels also appear to have been written around search phrases rather than user language.

A more useful version might separate the purposes:

• Travel information: Station information, Accessible travel
• Help and contact: Help centre, Contact us
• Explore: Weekend travel offers, Travel guides
• About the company: About us, Careers, Investor information
• Legal and accessibility: Privacy, Cookies, Terms, Accessibility

If a customer needs to find a station, the footer now offers a recognisable route. If a jobseeker arrives at the site, Careers is easier to identify. If the weekend offer expires, it can be removed from the relevant group without leaving a permanent keyword-shaped scar across every page.

Notice what has not happened: the footer has not become a replacement for the main navigation. It has become a clearer secondary layer.

Where SEO fits into the decision

SEO is a consequence of a good navigation decision here, not the organising principle.

Clear internal links can give search engines a route to important pages, and descriptive anchor text provides context about linked destinations. That supports discoverability and interpretation, as Google explains in its documentation on crawlable links.

It does not follow that adding more footer links creates a predictable ranking benefit. A footer link can provide a discovery path without guaranteeing that a page will be indexed, rank well or attract useful traffic. Crawl discoverability, indexation and ranking are separate outcomes.

The same separation applies to page purpose. A privacy policy, account page or support route may need to be easy for customers to find without being an organic search landing page. Conversely, an indexable service or resource page may not need a permanent sitewide footer link if users can reach it through a stronger, more contextual part of the architecture.

Repeated sitewide signals also need to be interpreted carefully. A legitimate repeated link to Terms or Accessibility is very different from a large set of unnatural, keyword-heavy links distributed mainly to influence rankings. Repetition alone does not decide the issue.

There is also no credible universal maximum for footer links. Google’s link guidance does not provide one, and usability evidence about crowded site maps should not be turned into a fixed footer threshold. A sensible footer for a ten-page site and a sensible footer for a global publisher will look different.

Govern the footer as a shared template

A footer change is rarely just a small content edit. On a template-driven site, one change can affect every URL. That makes ownership and release checks worthwhile.

Agree who can request and approve footer changes. Marketing may own campaign needs, customer service may own support routes, and legal or compliance teams may own policy links. Someone still needs responsibility for the whole structure.

Before release, check:

• the destination URLs work and use the intended market or language;
• temporary campaign links have an expiry or review date;
• labels match the destination and the group heading;
• the footer works on mobile at normal text sizes;
• keyboard users can reach and understand the navigation;
• navigation landmarks and group labels remain distinguishable;
• the change has not duplicated an existing primary or local navigation route;
• important pages remain reachable through a sensible wider hierarchy.

After release, validate a representative set of templates rather than checking only the page used by the developer. Confirm that links appear in the right markets, retired destinations are gone and analytics or support journeys have not been accidentally disrupted.

This is proportionate governance, not a formal standard or universal release checklist. A shared footer is a small piece of code with a very large distribution list.

So, what should your footer link to?

Start with the tasks people need to complete when the primary navigation is not the best route. That usually means a considered mix of utility, legal and trust information, customer support, secondary organisational destinations and selected routes such as a location directory or resource hub.

Give each link a clear label and a meaningful group. Use search demand as evidence when shaping the wider architecture, but do not let keyword targets decide which pages receive permanent sitewide promotion.

The most important distinction is simple: a page can be important without needing a footer link, and a footer link can be useful without pointing to a search landing page. Treat those as separate decisions.

For larger or more complex sites, Liquid Silver can help diagnose the wider architecture, prioritise footer changes by user and business need, and work through the implementation risks across shared templates.