Update a shared footer across your website

Confirm which footer is active

A shared footer can supply contact details, navigation, and supporting links across the website. Editing its source affects multiple pages, so begin by identifying the active footer rather than adding the same section to each page body.

You need administrator access, approved replacement text, and a list of links that must remain. Confirm the website and content language. Record current legal links and any pre-footer content. If an optional shared custom shell replaces the footer region, editing the native footer page may not change public output; have the shell owner identify the active source first.

This guide covers the native shared footer page and footer settings. It does not activate or redesign a shared shell.

Edit content and settings separately

Open Settings > Design > Footer. Review Footer Settings and Footer Content. Note whether Use pre-footer is enabled and whether a footer page already exists. The pre-footer is a separate region above the footer, not another name for the same content.
If no footer page exists and you intend to add one, choose Create Footer Page. This creates the system page used by the shared footer. Do not create an ordinary navigation page called Footer as a substitute or add it to main navigation.
Edit the existing footer through the inline editor, or choose Open in new tab. Replace only the approved content. Keep contact details short and use meaningful link labels. For internal destinations, choose website pages through the link controls so references retain page identity.
Save the footer content explicitly. System chrome pages such as /_footer do not require the regular page-header structure. Do not add a large hero header merely because ordinary pages have one.
Review settings such as Show full navigation menu in footer, Show language nav, and Hide legal links. Preserve legal links unless their removal has been specifically approved. Saving content and saving these website-level settings are separate actions; review both before leaving the screen.
If the website already has other languages, select the appropriate content language and inspect the corresponding shared content. An English footer correction does not establish that every translation has been updated. Arrange language review without creating unapproved translations as part of this edit.

Check several public pages

Open Home, a regular content page, and a collection item outside the editor. Scroll to the footer and test every changed destination. Check a narrow screen, long labels, and language navigation where enabled. Confirm that a pre-footer has not been accidentally duplicated inside the footer itself.

If the old footer remains visible, check whether you edited the wrong website, a different language, or an inactive native region beneath a custom shell. Do not paste duplicate footer content into page bodies to work around that mismatch. Re-read the active configuration and allow only authorized cache or operational actions.

Read templates and reusable content, design and styling, and languages and translations for related behavior.