Skip to main content
Footer renders the bottom section of a page — named groups of links plus a copyright string. This page explains the props, the shape of each group, and the patterns Footer supports. Each group is a column with a heading and a list of links: typically sitemap navigation, legal links, and social profiles. Footer is almost always the last block inside NavShell’s children array and appears on every page in the workspace, so keep the content consistent.

​
Example

footer.json
{
  "block": "Footer",
  "props": {
    "groups": [
      {
        "title": "Product",
        "links": [
          { "label": "Features", "href": "/features" },
          { "label": "Pricing", "href": "/pricing" }
        ]
      },
      {
        "title": "Company",
        "links": [
          { "label": "About", "href": "/about" },
          { "label": "Blog", "href": "/blog" }
        ]
      }
    ],
    "copyright": "© 2026 Acme Co."
  }
}

​
Props

The links shape inside each group is implied by convention. Confirm the authoritative shape — including whether external or rel attributes are supported — via the Builder MCP get_block_schema tool.

​
Patterns

Standard SaaS footer. Three groups: product (features, pricing, changelog), company (about, blog, careers), legal (privacy, terms). Mirrors the structure most users expect. Footer with social row. Pull social profile links into a fourth group, or use class_overrides on the Footer instance to render them as a dedicated row beneath the link columns. Auto-updating copyright. If your runtime version supports template interpolation in copyright, a string referencing the current year and brand name keeps the line up to date without per-year patches. Verify interpolation support against your runtime before relying on it.

​
Common props

In addition to the Footer-specific props, every block accepts id, class_overrides, visible_if, and analytics_event. See common props on the PageBlocks overview.

​
Where to go next