SpunkArt
Long reads and site policies

How to write a good website footer

The footer is the strip at the bottom of every page. Visitors scroll there when they are looking for something specific: contact details, a policy, or a way back to the main sections. A good footer answers those needs quickly and stays out of the way.

What visitors look for in a footer

People rarely read a footer from left to right. They scan it for one thing. Plan the content around the most common reasons someone scrolls to the bottom:

  • Policies: privacy page and terms, if the site has them.
  • Contact or about: how to reach the people behind the site, or who they are.
  • Main sections: a short repeat of the top navigation, useful after a long page.
  • Copyright line: the owner’s name and the year range.
  • Accessibility statement, if you publish one.

Everything else is optional. If an item does not serve one of those needs, consider leaving it out.

Sample footer HTML

<footer class="site-footer">
  <nav aria-label="Footer">
    <ul>
      <li><a href="/">Home</a></li>
      <li><a href="/ebook.html">Build a site</a></li>
      <li><a href="/privacy.html">Privacy</a></li>
      <li><a href="/terms-of-service.html">Terms</a></li>
    </ul>
  </nav>
  <p>&copy; Example Garden Club</p>
</footer>

The <footer> element tells assistive technology this is the page footer. Wrapping the links in a <nav> with an aria-label lets screen reader users jump to it and tells them which navigation it is when the page has more than one.

Accessibility checklist

  1. Contrast. Footers often use small grey text on a dark background. Check that the text still meets contrast guidelines.
  2. Size. Keep the text readable, not shrunk to fit. Touch targets on phones need enough space between them.
  3. Link text. Each link should make sense on its own: “Privacy”, not “Click here”.
  4. Keyboard. Tab through the footer and confirm each link shows a visible focus outline.
  5. Structure. Use lists for groups of links, and headings only when there are several labelled groups.
  6. No essential content only in the footer. Important information belongs in the main page too.

Why sitewide link blocks to unrelated sites look spammy

Some sites put a long block of links to other websites in the footer of every page, often with keyword-heavy anchor text: “cheap widgets”, “best loans”, a list of sister sites. This causes several problems.

ProblemWhy it matters
It does not help the readerSomeone reading about recipes has no use for links to unrelated tools or services.
It multipliesA footer appears on every page, so ten links become thousands across a large site.
It matches a known patternSearch engine spam policies describe link schemes and excessive cross-linking between sites. A sitewide block is easy to spot.
It harms trustReaders see the block as advertising and trust the rest of the page less.
It adds weightLong footers make every page heavier and noisier for screen reader users.

If another site is genuinely useful to your readers, link to it from the specific page where it helps, with a plain description. If links are paid or sponsored, mark them with rel="sponsored", and use rel="nofollow" for links you do not want to vouch for.

Common mistakes

  • Repeating the whole site map, so the footer is longer than the content.
  • Broken policy links, or links to policies that describe a different site.
  • Badges, counters and award logos that make claims nobody can check.
  • A copyright year that stops updating; either set it when you publish or update it as part of your routine.

Questions

Should a footer be the same on every page?

Usually yes. Consistency helps people find things. Small differences, such as a section-specific link, are fine.

Does a footer help search rankings?

Internal links in a footer help crawlers find key pages. Beyond that, a footer is for usability, not ranking.