> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/en/userguide/widget/apply-widget.md).
# Add widgets to your online store
You can use widgets made in Charlla on any online store platform that has an HTML editor.
### Add a Floating widget
1. Copy the code from the widget list or the widget editing screen.
2. Paste the code into the HTML editor of the page where you want the widget, then save your changes.
{% hint style="info" %}
**The Floating widget appears in the position you set in Charlla, no matter where you paste the code.**
{% endhint %}
### Add a Slide, Multi-Shop Player or Spotlight widget
1. Copy the code from the widget list or the widget editing screen.
2. Paste the code into the HTML editor of the page where you want the widget, then save your changes.
### Add a Hero Banner widget (main page top banner)
1. Copy the code from the widget list or the widget editing screen.
2. Paste the code into the HTML editor of the page where you want the widget, then save your changes.
{% hint style="warning" %}
**To add a widget to a product detail page, you must add the widget code in the editor for that individual product page.**
{% endhint %}
---
# 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://support.charlla.io/en/userguide/widget/apply-widget.md?ask=&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.
