> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/settings/how-to-update-the-default-favicon-across-all-pages.md).

# Default Favicon

This article provides a step-by-step guide to updating the default favicon for your shop globally across all pages in Limio Shop.

> **Note**: If your shop operates on multiple domains (multi-shop), refer to our [How to Set Up Shops on Multiple Domains (Multi-Shop)](https://docs.limio.com/product/settings/how-to-set-up-shops-on-multiple-domains-multi-shop) article for instructions on managing favicons within multi-shop implementations.

## Steps to Update the Favicon

1. **Navigate to the Settings Page**
   * In the Limio Shop interface, click the **profile icon** in the top-right corner.
   * From the dropdown menu, select **Settings**.
2. **Access Shop Settings**
   * Once on the Settings page, navigate to **General Settings > Shop**.
3. **Enter the Favicon URL**
   * In the **Favicon URL** field, enter the full URL for your desired favicon.
     * *Example: `https://example.com/favicon.ico`*
   * **Important**: A complete URL is required; file paths (e.g., `/images/favicon.ico`) will not work.<br>

     <figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-4f081c824c80d482b332531a3bee0e554bbfa6a3%2Fimage%20(186).png?alt=media" alt=""><figcaption></figcaption></figure>
4. **Rebuild and Publish All Pages**
   * After updating the favicon URL, rebuild and publish all pages from your shop to apply the changes.
   * This step ensures the updated favicon appears across your entire site.

### Additional Notes

* The favicon update may take a few minutes to reflect across all pages due to caching.


---

# 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.limio.com/product/settings/how-to-update-the-default-favicon-across-all-pages.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.
