Website Footer Examples

Quick answer: Website footer examples are reference points for how service businesses, ecommerce stores, SaaS products, local operators, and professional services structure their footers so visitors can find deeper pages, check business credibility, contact the business, see locations or service areas, and keep moving when they reach the end of a page. The strongest website footer patterns share a brand block with a one-line description and a primary CTA, link columns for services/products, studio/company pages, resources, and legal, a real contact block (address, phone with click-to-call, hours, Google Business Profile link), social links the business actually maintains, real trust signals where they earn their place, and a copyright line naming the legal entity. Onyxarro can use concept-style examples to show the thinking clearly, but they should be labelled honestly as design examples, not presented as real client results. Footer performance depends on the offer, the proof, the niche, the audience, the device mix, the speed and accessibility floor, the rest of the site, the tracking, and the follow-up. For a free 48-hour read of your footer in context, see our free 48-hour website audit.

A footer is not the bottom of a page. It is a trust block, a navigation block, and a recovery block. By the time a visitor scrolls down to it, they have either decided to act, decided to look for something specific, or decided to leave. The footer's job is to catch all three. Operators who treat the footer as decoration leak the visitors most likely to buy on the next click.

Across every niche we audit (service businesses, ecommerce stores, SaaS products, local operators, professional services), the structure stays the same. What changes is which link columns matter most, which trust signals earn their place, and which CTA pattern the footer carries. A service-business footer leads with services, work, about, contact, and a phone with click-to-call. An ecommerce footer leads with customer service, shipping, returns, payment-method icons, and product columns. A SaaS footer leads with product columns, resources, status, and security. Same skeleton, different muscle.

This article walks the elements a footer needs, then runs niche pattern blocks (service business, ecommerce, SaaS, local, professional, contact, navigation, trust, CTA, legal, mobile) so the umbrella stays useful for whichever niche you're briefing.

Footer real estate sits below the fold by design, but it carries an outsized share of trust and discovery work. A visitor who has scrolled to the footer of any page is, by definition, engaged. The footer's job is to convert that engagement into a click, a call, or a decision to come back.

A clean footer does five things. It confirms what the business is. It carries the deeper pages the header could not. It surfaces real contact information for visitors who prefer phone or email. It carries trust signals that did not earn their place in the header. It gives the visitor a clear last CTA when nothing else on the page caught them. Done well, the footer is a working part of the conversion path. Done badly, it's a wall of bland link grids that the visitor scrolls past on the way to closing the tab.

None of this is legal, financial, medical, tax, compliance, staffing, operational, or industry-specific advice. The article is strictly about website design patterns. Your local advertising and consumer-protection rules sit above any of this. For the upstream navigation pattern that frames the footer, see our website navigation examples pillar, and for the broader homepage context see our website homepage examples pillar.

The simplest useful footer has four blocks: a brand block with a one-line description, two or three link columns, a contact block, and a copyright line. Add only the support content that genuinely earns its place.

Sections that earn their place. The brand mark and a one-line description. Two to four link columns matching the site's real page types. A contact block with the channels the audience actually uses. A small social row for the platforms the business actually maintains. A copyright line naming the legal entity. A small legal row (terms, privacy, refund or complaints).

For the broader navigation pattern that the footer extends, see our website navigation examples pillar.

Service business footers are read by visitors who want to confirm what the business does, where it works, and how to talk to a real person. Phone, service area, and a quote or audit CTA carry the bulk of the weight.

Sections that earn their place. A brand block with a one-line "what we do, who we help" sentence. A Services column listing the four to seven real services. A Work or Studio column linking to portfolio, blog, about, and contact. A Service Areas block naming real suburbs or regions, ideally linking to location pages where they exist. A Contact block with phone, click-to-call, email at the brand domain, and a one-line address or service-area note. A small trust strip with real Google rating, real industry-body membership, and real licensing where the niche needs it. A clear secondary CTA back to the audit, quote, or contact page.

What to avoid. "Industries we serve" link grids that exist only to keyword-stuff the footer. Phone numbers that contradict the Google Business Profile. Fake "Member of..." badges with no current year. Awards with no issuer.

For the broader service-business umbrella, see our service business website examples pillar, with niche reads for tradies, builders, and roofers.

Ecommerce footers are read by visitors who want shipping detail, returns policy, customer service, and trust signals before they check out. The footer is the last reassurance block on the way to the cart.

Sections that earn their place. A Shop column listing real categories or collections. A Customer Service column with shipping, returns, contact, order tracking, and FAQ. A Company column with about, careers, sustainability where real, and press. A small payment-method strip showing the real payment options accepted. A real shipping-partner badge where the brand has confirmed coverage. A small "Trusted by" or rating block where the rating is genuine and consent-cleared. A legal row with terms, privacy, refund, and accessibility statement where relevant.

What to avoid. Logos lifted from public-logo libraries without consent. "As seen in..." strips with no verifiable source. Newsletter sign-ups that promise discounts the brand never delivers. Returns policies hidden behind a "contact us" link.

For the broader ecommerce umbrella, see our ecommerce website design examples.

SaaS footers are read by buyers comparing tools and by existing customers looking for documentation, status, or support. The footer should serve both audiences clearly.

Sections that earn their place. A Product column with the real modules, use cases, or features. A Pricing link. A Resources column with docs, changelog, blog, customer stories, and webinars where they exist. A Company column with about, careers, contact, and press. A Trust column with security, status page, privacy, terms, and DPA where the audience expects it. A small "Trusted by" or named-customer strip where consent is in writing. A small social row.

What to avoid. Customer logos used without consent. "SOC 2 compliant" or similar claims without a real attestation link. Status pages that haven't been updated in months. Press strips that look impressive but link to nothing.

For the broader SaaS umbrella, see our SaaS website design examples.

Local business footers are the most underrated trust block on the site. A footer that names the real address, real hours, real phone, real Google Business Profile, and real social links makes the business feel verifiable. A footer that hides any of those raises questions the homepage cannot answer.

Sections that earn their place. A brand block with a one-line description and a small location tag. An address block with the real street address and a small embedded or linked map. A real phone with click-to-call. Real opening hours, including statutory holiday notes where they matter. A Google Business Profile link. A short service or menu column. A small social row pointing at the platforms the business actively uses. A real "Local since..." line where the year is defensible.

What to avoid. Addresses that contradict the Google Business Profile. "Open 24/7" claims for a business that closes at 5pm. Multi-location pages with no map. Newsletter sign-ups for a single-location cafe.

For local hospitality and retail patterns, see our restaurant examples and beauty salon examples.

Professional service footers (legal, accounting, financial, advisory, medical-adjacent) are read with more scrutiny than most other niches. The footer is also where compliance, regulator, and registration detail tends to live by convention.

Sections that earn their place. A Practice Areas or Services column. A People or Team column linking to the real bios. A Resources or Insights column with current articles and guides. A Trust column with real industry-body membership (current year), real registration or licence number where the regulator publishes one, real address, and real phone. A Legal row with terms, privacy, complaints, and disclaimers in plain English. A copyright line naming the legal entity.

What to avoid. "Award-winning" with no named issuer. Membership badges past their current year. Registration numbers that cannot be verified. "Guaranteed outcomes" copy of any kind on a professional services footer. Disclaimers buried in small grey type that the audit floor flags for contrast.

For niche-specific professional patterns, see our law firm examples, accountant examples, and clinic examples. None of this article is legal, financial, accounting, tax, or medical advice.

The contact block is the most-read part of most footers. Visitors who want to call, email, or visit usually scroll straight to it. The block should be short, scannable, and accurate to the rest of the site.

What works. A real phone number with click-to-call. A real email at the brand domain (not a generic free-mail address). A real street address or honest service-area description. Real opening hours where they matter. A small map block or Google Business Profile link for local businesses. A "what happens next" line for any contact form that lives elsewhere, so the footer block reinforces honest response expectations.

What to avoid. Phone numbers that go to a personal mobile while the site advertises a landline. Email addresses on a free-mail domain. Address blocks that contradict the Google Business Profile. Hours that contradict the Google Business Profile. "Available 24/7" claims the business cannot meet.

For the deeper contact-page pattern library, see our contact page examples pillar.

Footer navigation is not the same as header navigation. The header is short, conversion-led, and primary-CTA heavy. The footer is wider, discovery-led, and link-density tolerant. Visitors who scroll to the footer have chosen to look there, so the bar for "is this link useful" is lower than in the header.

What works. Three to five clear columns with descriptive headings. Real page types only, not placeholder labels. Links opening real pages, not 404s. A short "More" or "Resources" column where the site genuinely has more pages than the primary nav can carry. A small sitemap or "All pages" link for accessibility and SEO. A separate "Locations" column for businesses with more than one branch. A consistent column order so a returning visitor finds the same link in the same place.

What to avoid. Twelve identical columns padded with single-link pages. "Quick links" columns that exist because the operator could not decide what else to add. Footer link grids designed for crawlers rather than humans. Hidden categories of "SEO landing pages" linked only from the footer.

For the upstream nav pattern that the footer extends, see our website navigation examples pillar.

Footer trust signals are where most operators over-reach. The header is no place for a wall of badges; the footer is not the place to relocate the same wall. One to three real trust signals beats a strip of 12 logos every time.

What works. A real Google rating block where the rating and count are genuine. A real industry-body badge with a current membership year. A real "Trusted by" or named-customer strip with consent in writing. A real registration number for regulated professions. A small NZBN or company-registration link for businesses that operate under transparent business-registration rules. A real payment-method strip for ecommerce. A real shipping-partner badge for ecommerce where confirmed.

What to avoid. Logos lifted from public-logo libraries without consent. "As seen in" strips with no verifiable source. Fake awards. Memberships past their renewal date. Star-rating strips that aggregate reviews from unrelated businesses. "Featured by" lines that reference media the brand has never actually appeared in.

Footer claims are also where consumer-protection regulators look. In New Zealand, the Commerce Commission's misleading-claims guidance applies to footer copy as much as it does to hero copy. Similar rules sit under the ACCC in Australia, the ASA + CAP codes in the UK, and the FTC's truth-in-advertising rules in the US. Fake awards, fake review counts, fake "as seen in" strips, fake regulatory claims, and misleading guarantee links all sit inside the territory regulators care about. None of this is legal advice, just a flag that footer-level claims should be defensible, not aspirational.

The footer CTA is the recovery CTA. It exists for visitors who reached the bottom of the page without converting from the hero, the services block, the proof block, or the in-page CTA. Soft, specific, and confidence-led tends to beat hard sell at this point.

What works. A short "Want a quick read on your site?" or "Have a project in mind?" block above the link columns. A clear primary CTA pointing at the audit, quote, contact, or booking page. A secondary line confirming response time or "no call required" where true. A small "Or just say hi" mailto link as a softer alternative. Mobile-thumb-sized buttons.

What to avoid. Three competing CTAs in the footer fighting for the same click. "Limited consultations" claims the business cannot defend. Pop-ups firing when the visitor hovers over the footer. CTAs leading to pages that 404. Newsletter sign-ups dressed up as a "Get a free audit" CTA.

For the deeper CTA pattern library, see our website call-to-action examples, and for the booking-page depth see our booking page examples.

The legal row in a footer is short, plain, and consistent across the site. It is also one of the easiest blocks to get wrong by importing a generic template that does not match how the business actually operates. Treat this as a design pattern, not a legal exercise.

What works as a layout pattern. A small row at the bottom of the footer carrying Terms, Privacy, Refund or Complaints, and Accessibility where it exists. A copyright line naming the registered legal entity (for example "Onyxarro · The Victory Co. Limited"). A short cookie note where the audience expects one, linking to a real cookie policy. A real sitemap link for accessibility and SEO. A small accessibility statement link for sites that publish one.

What to avoid as a layout pattern. Legal pages that are 5,000-word boilerplate with no specific business detail. Copyright lines without the legal entity name. Cookie banners that block the footer behind a tap-to-dismiss layer that never dismisses. Sitemap links pointing at a 404. Terms or privacy links pointing at the same generic template across unrelated client sites.

None of the above is legal advice. The actual content of those pages should be drafted with a lawyer who understands the business and its jurisdiction; this article is strictly about how the layout, link placement, and labelling should look.

Mobile footers are where most footer design fails. A footer that looks balanced on a 27-inch monitor and unreadable on a 5.4-inch phone is a footer that loses. Mobile-first is not a slogan here; it's the only realistic default.

What works. Single-column or two-column collapse at the right breakpoint. A click-to-call link at the top of the contact block. A real "Open in Maps" link for the address. Tap-targets at least 44x44px. Visible spacing between links. A clear visual break between the legal row and the rest of the footer. A footer-height that does not stretch the page two extra screens on mobile.

What to avoid. Mobile footers that hide the contact block under a "More" toggle. Multi-line link rows that overlap on small screens. Light-grey text on near-black background that fails AA contrast. Sticky CTAs that overlap the footer copyright line at the bottom of the viewport.

Accessibility matters here. The footer should be keyboard reachable, have visible focus on every link, and announce its landmark role to screen readers (a real `<footer>` element with semantic markup is usually enough). None of these need to be visible to most visitors; they all matter to some, and they all sit inside the WCAG basics the audit floor expects.

Footer failures repeat across niches. Different industries, same patterns. The shortcut is to write every footer label, claim, and link as if the visitor will hover for two seconds, scan, and decide.

Each of these is fixable in a single sprint. The shortcut is to write the footer as if the visitor will hover over every label, click every link, and screenshot every claim. A footer built for that visitor never has to be rewritten when the audit floor or the regulator tightens.

Onyxarro briefs every footer off the same checklist regardless of niche. Brand block, two to four real link columns, real contact block, real trust signals where they earn their place, real legal entity in the copyright line, and a single recovery CTA. Where a claim sits in the footer, it has to be defensible in writing. Where a logo or badge appears, it has to be there with consent and a current year.

Onyxarro can use concept-style examples to show the thinking clearly, but they should be labelled honestly as design examples, not presented as real client results. We will happily ship a concept service-business footer, a concept ecommerce footer, a concept SaaS footer, a concept local footer with NAP and map, a concept professional services footer with compliance-safe wording, or a concept mobile footer for any niche on this list. Concepts are useful for showing how a footer should feel; they are not a stand-in for the real business's real services, real proof, or real entity layer.

The 48-hour delivery is a workflow choice, not a quality compromise. The structural piece (brand block, link columns, contact block, trust strip, legal row, copyright line, mobile collapse) is fast once the brief is honest. Most of the time in a footer rebuild goes into the conversation needed to decide which link columns earn their place.

If you want a redesigned footer preview against your real site, the free 48-hour website audit ships a written read plus a public preview link. You can also read the website navigation examples pillar for the upstream header pattern, the website homepage examples pillar for the homepage frame, and the website trust signals examples pillar for the proof layer that backs the footer trust strip.

A practical operator checklist for anyone briefing or sweeping a footer. Tick what's working; everything still unticked is a candidate for the next sprint.

If more than four lines stay unticked, the footer is a rebuild candidate, not a polish job. The free 48-hour audit runs this checklist on your live site and ships a written read alongside a redesigned footer preview.

The footer pillar closes the header / navigation / footer triad. Pick the closest pattern or niche for the deeper read:

• Website navigation examples: cross-niche header, footer, mobile menu, and nav CTA pattern library.
• Website service page examples: cross-niche service-page hero, offer, proof, pricing, FAQ, and CTA pattern library.
• Website portfolio page examples: cross-niche gallery, project card, case study, before-and-after, and proof pattern library.
• Website homepage examples: cross-niche front-door pattern library.
• Website trust signals examples: cross-niche proof and credibility layer that backs the footer trust strip.
• Website call-to-action examples: cross-niche CTA pattern library.
• Contact page examples: cross-niche enquiry-flow pattern library.
• Pricing page examples: cross-niche pricing and packaging patterns.
• About us page examples: cross-niche story, team, values, and proof pattern library.
• Booking page examples: cross-niche appointment, consultation, quote, demo, and reservation pattern library.
• Service business website examples: cross-niche service-business umbrella.
• What makes a website convert: the upstream design-decision layer.
• Ecommerce website design examples: ecommerce shop / shipping / returns footer patterns.
• SaaS website design examples: SaaS product / status / security footer patterns.
• Tradie website design examples: trades footer and service-area patterns.
• Builder website design examples: builder footer and licence patterns.
• Roofer website design examples: roofer footer and emergency-call patterns.
• Law firm website design examples: law firm footer and credential patterns.
• Accountant website design examples: accountant footer and service patterns.
• Clinic website design examples: clinic footer and team patterns.
• Restaurant website design examples: hospitality footer and reservation patterns.
• Photographer website design examples: portfolio footer patterns.
• Beauty salon website design examples: salon footer and booking patterns.