> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/sequoia-theme-documentation/blocks-and-sidebar/footer-setup.md).

# Footer Setup

A footer is an area located at the bottom of a webpage. Like a header, it typically appears consistently throughout the website and on all pages and posts.

## Creating Footer

The setup of the footer occurs in the very same way as the header setup.

Go to **Appearance > Header & Footer Builder** and click on **“Add New”.** Type the name of the template – Footer.

![](https://2425882545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCl8bwZ72WkAolEEjK0qm%2Fuploads%2FiPJrOAu7s9hOkE6myM1o%2FAdd%20Footer.gif?alt=media\&token=63a7cf30-8c84-4f74-a62d-4e3f7638af12)

Select a header in the drop-down menu to display it on the entire website.

Additionally, you can add displaying rule or exclusion from that rule, appoint user roles, pick post attributes, and enable layout for Elementor Canvas Template.

Now, hit **Publish** to get your footer template published.

The footer can also be configured via Elementor, just hit the **Edit with Elementor** button.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stylemixthemes.com/sequoia-theme-documentation/blocks-and-sidebar/footer-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.