How to Show a Footer on Specific Pages of a Client Site

A practical way to decide how many footers a site really needs, and how to exempt the pages that should not carry the standard one.

What it takes to show a footer on specific pages

A footer starts out global for a good reason. It carries the things every page owes a visitor regardless of why they arrived – who the business is, how to reach it, the legal links – and duplicating that across forty pages means forty places to edit when the phone number changes. Global is the correct default, and most of the trouble agencies have with footers comes from treating the default as a law rather than as a starting position.

Then a page arrives that needs something else. A checkout step where every outbound link is a way to abandon the purchase. A paid landing page where a full navigation footer undoes the point of having a single call to action. A thank-you page where the standard footer is simply noise. At that point the question stops being cosmetic and becomes structural: is the footer one object shown everywhere, or a small family of objects with rules about where each one appears?

Why builders make the footer global by default

Page builders generally treat a footer as a reusable block: stored once, referenced by many pages, edited in a single place. That reference is the entire value. Break it – by pasting a copy onto each page so you can change one – and you have not created a variant, you have created maintenance debt that only shows itself months later, when half the site quietly still carries the old address.

So the first rule of scoping is that you should be subtracting references, not multiplying copies. Every approach below is really a different answer to one question: how do you exempt a page from the shared block without abandoning sharing altogether?

Four ways to scope a footer, and what each one costs

Copy the section onto each page

The crude option, and the one people reach for first because it always works. Paste the footer as an ordinary section on the pages that should have it, and leave it off the pages that should not. It is instantly understandable and asks nothing of the builder.

It also scales badly. The cost is linear in pages and it is paid later, by someone else, usually under time pressure. On a five-page site it is defensible. On a client site that keeps growing, it is the reason a footer eventually disagrees with itself from page to page.

One global footer, switched off per page

The version most builders support in some form: the footer stays a single shared object, and individual pages carry a setting that says “not here”. Editing the footer still updates everywhere it appears, and the exception is recorded on the exception, which is where it belongs.

This is the right answer for the common case – a global footer everywhere except checkout and thank-you. Check what your builder calls the setting before you design around it, because the naming varies and the behaviour is not always identical between a funnel step and a standalone site page.

Two or more footers, assigned by page type

When a site genuinely serves two audiences – a marketing site and a client portal, say, or a blog alongside a set of paid landing pages – the honest structure is two footers, each global to its own group. A minimal footer holding a legal line and nothing else is a perfectly good second object.

The cost here is discipline rather than labour. Two footers become five if nobody owns the decision, and five is worse than forty copies, because at least the copies were obviously wrong. Write down which footer belongs to which page type, and keep the count as low as the site allows.

Hide it with a display rule

The section stays attached to every page and is hidden on the ones that should not show it, usually with a class or a visibility condition. It looks tidy in the editor and carries a real drawback: on many builders the markup is still delivered to the browser and merely hidden, so you have not removed the links, only made them invisible. That matters for page weight and for crawlers, which is a good reason to prefer a real exclusion over a visual one. The weight side of it is the same argument that turns up in any page speed score review.

Which pages usually want something different

Four categories account for most real exceptions, and it helps to name them rather than deciding page by page.

• Transactional steps. Order forms, checkouts, upsell steps. Every link in a footer is an exit, and the page exists to prevent exits. A short legal line is usually the correct footer here.
• Paid landing pages. The visitor arrived for one offer. A full sitemap footer invites them to go and read about something else instead.
• Confirmation and thank-you pages. The conversion already happened, so this is one of the few places where a larger footer can be right – next steps, support, the rest of the catalogue.
• Content pages. Posts and archives usually want the full footer, because that is where discovery happens. A browsing structure such as a blog category tree only earns its keep if something links into it.

Headers follow the same rule, with one difference

Everything above applies to putting a header on specific pages: same shared object, same exception mechanism, same trap around copies. The difference is that a header sits above the fold and a footer below it, so a header exception changes what a visitor sees immediately while a footer exception changes what they find after they have already decided. That makes header scoping the higher-risk change, and the one worth previewing on a real phone before it goes live.

What breaks when you scope a footer

Three failures come up often enough to check for deliberately.

The exception does not survive a copy. Duplicating a page, cloning a funnel or moving a design between sub-accounts can carry the layout and drop the per-page setting, so a checkout that had no footer suddenly has one. This is the same class of problem as anything else that travels between accounts – it is worth knowing what does and does not move during a funnel template import, and the same care applies to snapshot assets.

The legal links disappear entirely. Turning the footer off on a checkout is a reasonable instinct that can also remove the terms and privacy links from the one page where a buyer is most likely to want them. Strip the browsing navigation; keep the legal line.

Mobile spacing breaks. A page designed with a footer often relies on it to close the layout. Remove it and the last section can end flush against the bottom of the viewport. Check the exception pages at a narrow width, not only in the desktop editor.

How to decide, in order

1. Write down the page types on the site, not the pages. Most sites have three or four.
2. Decide what each type owes the visitor at the bottom of the page. If two types want the same thing, they share a footer.
3. Build the smallest number of footers that answers step two – usually one full and one minimal.
4. Record the exceptions on the pages, not in somebody’s memory.
5. Open one page of each type on a phone before calling it done.

A footer on specific pages is not a special feature to hunt for in a menu. It is a decision about how many footers the site actually has, followed by the much smaller question of how your particular builder attaches them.

See also: Reusable Header and Footer: One Source, Many Pages

Frequently Asked Questions

Can I put a footer on specific pages without copying it onto each one?

Yes, and that is the approach to prefer. Keep the footer as one shared object and record the exceptions on the pages that should not show it. Copying the section onto every page works immediately, but every future edit then has to be repeated in every copy, which is how a site ends up with two different phone numbers in its own footer.

Which pages usually should not carry the standard footer?

Transactional steps such as order forms and checkouts, and paid landing pages built around a single call to action. In both cases every footer link is an exit from the page’s one job. Replace the navigation with a short legal line rather than removing the footer completely.

Is hiding a footer with CSS the same as removing it?

No. On most builders a hidden section is still delivered to the browser, so the links are present in the markup and only invisible to the visitor. That still counts toward page weight and can still be read by crawlers. Use a real per-page exclusion for permanent structure, and treat visual hiding as a temporary measure.

How many different footers should a client site have?

As few as describe the site honestly, which is usually two: a full one for content and marketing pages, and a minimal legal one for transactional steps. A third is justified when a site genuinely has a separate section with a different audience, such as a client portal. Past that they stop being a system and become clutter.

Does a per-page footer setting survive when I duplicate a page or import a design?

Not reliably. Layouts travel more dependably than per-page settings, so a cloned funnel or an imported template can arrive with the footer switched back on. Re-check the exception pages after any copy, import or migration instead of assuming the setting came along with them.

Does the same approach work for putting a header on specific pages?

Yes. A header is scoped the same way, as one shared object with recorded exceptions. The practical difference is that a header is visible immediately, so a mistake there costs more than a footer mistake. Preview header exceptions at a narrow screen width before publishing.

What is the most common thing to get wrong?

Removing the whole footer from a checkout page, which also removes the terms and privacy links at the moment a buyer is most likely to look for them. Strip the browsing navigation, keep the legal line, and check the page at mobile width, because layouts often rely on the footer to close the bottom of the page.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.