Design the footer like someone reads it — because someone does

A while back we published our footer taxonomy — the four jobs a footer does, in order, from wayfinding to charm. That piece is about what a footer is for. This one is about the craft: the twenty small decisions that separate a footer that quietly signals "these people sweat everything" from one that signals "Tuesday afternoon, deadline, good enough". Because visitors notice. Not consciously — nobody has ever complimented a footer — but in the aggregate judgement that happens at the bottom of the page, where a new client decides whether to start a conversation or close the tab.

The footer is also where design teams' quality dips, reliably, because it's the last surface designed and the first surface descoped. Our countermeasure is unglamorous: the footer gets its own design review, with its own checklist, at a moment in the project when it can still change. Here's what that review looks at.

Contact confidence: the last trust exam

For a services or B2B site, the footer's most valuable real estate is the contact affordance, and the review starts there. The questions:

• Can a human be reached from here? A real email address, spelled out, beats a link to a form for a certain kind of prospect — the one who's been burned by black-hole forms before. We often ship both: the address as a link, the form one click away. Footer email addresses collect some spam; they collect more trust.
• Does the response promise hold? "We reply within one business day" under an email link is a contract. Only ship it if ops can keep it — an unkept micro-promise in the footer out-damages no promise at all. This is the same trust-proximity logic we apply at checkout: reassurance belongs exactly where doubt occurs.
• Is the location honest? "Sydney · Melbourne · London" means those are staffed places. A footer that performs cosmopolitan reach for a four-person company is discovered within one procurement check, and the discovery is silently fatal.

The newsletter field: design the moment, not the input

Footer newsletter signups have the worst conversion-to-clutter ratio of any common component, so the review treats them as guilty until proven innocent. If the list is real and active, design the moment properly: one sentence of what and when ("Field notes on design and growth, monthly"), a single email field with a label that survives autofill, and honest microcopy about frequency and unsubscribe. No checkbox wall, no double-dropdown, no "join 10,000 subscribers" unless the number is both true and flattering.

If the list isn't actively maintained, the review's answer is delete the field. A signup that hands subscribers to an abandoned newsletter is a trust withdrawal with a loading spinner. This is the footer's version of the judgement call we make on social proof: the absence of a weak element is a design decision, and usually the right one.

The legal row: compliance without ugliness

Privacy, terms, cookies, accessibility statement, company registration. The legal row is where craft goes to die — dumped in 11px grey, disabled-contrast, as if shame made it smaller. The review rule: the legal row is set at the same size as other secondary metadata, on a contrast that passes, with at least touch-target spacing. Two arguments, one principled and one cynical. Principled: the accessibility statement that fails contrast while linking to your accessibility statement is a specific kind of embarrassment, and we've seen it in the wild. Cynical: procurement and legal reviewers read footers; a legal row handled with care reads as a company whose documents will also be handled with care.

And for studios and agencies: the colophon lives here. A line about what the site is made of — ours names our typefaces and the fact the whole thing is static-prerendered — is a small honest signal aimed at exactly the people who'll appreciate it. Colophons are handshakes between practitioners.

The details that only a dedicated review catches

These are the checklist items that never survive a general review, because nobody's job is the footer:

• Focus styles and keyboard order. Tab through the footer. Focus rings must be visible against the footer's background — a common failure, since footers are often the site's lone dark section. Keyboard users discover the footer by tabbing; the experience should not be a gauntlet of forty links before ever reaching it (hence: the ~25-link ceiling, and a real skip-link above it all). Our focus-visible piece covers the ring craft; the footer is where it most often regresses.
• Responsive collapse. At 375px, columns stack, tap targets hold at 44px, and the phone number is a tel: link with enough padding to be thumbed. Check the actual footer on a real phone; stacked-column order is a design decision (contact first for local businesses, nav first for content sites).
• Dark-section safety. When the footer is dark and the page above is light, the boundary needs design: a hairline, a deliberate step in value, something that says "you have arrived at the end". An unintentional gradient seam or a section that reads as more page keeps people scrolling past conversion content into the hedge.
• The copyright line. It says the year, the legal entity, nothing else. Auto-update the year, because a footer saying © 2023 in 2026 is a systemic roar that nobody is home. One small line that quietly invalidates every claim to craft above it.
• Social links: chosen, not defaulted. Every social icon in the footer is a promise that the destination is alive. A profile last posted in 2024 is a link to an empty shopfront. Fewer, live, ordered by where the practice actually shows up.
• Back-to-top? Only if it's honest about what it is (a utility, not an ad for scrolling) and non-sticky. We mostly leave it out and let the footer be the bottom.

The review ritual itself

Logistics, because rituals die without them. The footer review happens when the type scale, colour tokens and nav are settled — footers designed earlier get redesigned twice — and takes thirty minutes with a checklist and a live build, not a mock. Output is a punch list, owner per item, done in the same sprint. Then it recurs once before launch as part of the final QA pass, because footers accumulate drift in the last two weeks of any project (a legal clause lands, a social link gets added "temporarily").

And one post-launch check, a month in: pull the click data. Footer click maps are a diagnostic for the whole site's information architecture — heavy footer use of a link that's absent from the primary nav is the audience voting with their thumbs. We've promoted careers and pricing links into primary navs off the back of footer analytics more than once.

Why it matters more than its pixels suggest

The footer is the site's handshake goodbye, and also — this is the part we care about most — the place where an organisation reveals whether its craft claims are structural. Any team can make a hero beautiful; heroes get the meetings. The footer gets the leftover hour, which makes it an unusually honest signal about the people who built the site. Design it like someone reads it. Someone does. They're deciding whether to hire you while they do.

Key takeaways

• The footer deserves its own thirty-minute design review against a checklist — general reviews never catch footer failures because nobody owns the surface.
• Contact affordances are the last trust exam: reachable humans, promises ops can keep, honest locations.
• Newsletter fields are guilty until proven innocent; an abandoned list is worse than no field.
• Legal rows at readable size and passing contrast — procurement reads footers.
• The details: keyboard focus on dark backgrounds, 375px stacking order, auto-updating © year, dead social links.
• Footer click data a month post-launch is a free IA diagnostic.

FAQ

Should the footer be identical on every page? Structurally yes — it's a contract; visitors build one model of it. Minor contextual variation is legitimate (a checkout footer strips everything down to support and security links, which is a conversion decision, not inconsistency).

Do footers matter for SEO? Indirectly and structurally: the footer is crawlable internal linking on every page, which is why we insist money pages are reachable from it — the plumbing side is covered in internal linking architecture. Don't stuff it; do let it carry honest, permanent navigation.

Mega-footers with five columns and 60 links — ever? For very large properties (universities, platforms with hundreds of destinations), yes, designed as an index. For marketing sites, no — link slurry hides the five links people actually want beneath fifty they don't.

Where does the footer sit in a Brassfern website engagement? It's a named checklist in our website engagements — designed when tokens settle, reviewed in its own session, QA'd again pre-launch. It sounds like a small thing. It is exactly a small thing, done deliberately, which is most of what craft is.