> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/footer.md).

# Footer

The site footer: menus, a newsletter signup, free-form text, plus a bottom row with your copyright, social icons, and payment icons. Content comes from blocks; the bottom row from two toggles.

👉 **Customize → Footer** (bottom of the sidebar on every page).

## Settings

* **Show social icons** (on) — icons for every social URL you've filled in under **Theme settings → Social media** (Instagram, TikTok, X, YouTube, Facebook). Empty links don't render.
* **Show payment icons** (on) — the payment methods enabled on your store (Visa, Apple Pay, etc.), pulled automatically from your payment settings.

## Blocks

### Menu (up to 2)

* **Menu** (default: the "Footer" menu) — renders that menu's links in a row. Edit links under **Online Store → Navigation**. Two Menu blocks let you split shop links from policy links.

### Newsletter (max 1)

* **Heading** (default "Sign up for early access") — above an email field + Sign up button. Subscribers are saved as customers tagged `newsletter`.

### Text

* **Text** (rich text) — a short brand paragraph, contact info, or drop-schedule note. Add as many Text blocks as you need.

## Pro tip

💡 The copyright line ("© 2026 Your Store") is automatic — year and store name included — so don't repeat it in a Text block. Use the Text block for something useful instead: your studio city, support hours, or "All sales final on drops."


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/footer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.