> For the complete documentation index, see [llms.txt](https://guide.tiledesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.tiledesk.com/manage-your-workspace/install-widget-on-your-website.md).
# Install widget on your website
### Installation
To chat with your visitors embed the widget on your site following steps:
1. **Locate the javascript code**\
You can find your unique Tiledesk javascript code on your Tiledesk Dashboard by heading over to the **Settings > Widget > Add chat to your website**
1. **Copy the Javascript code**
```
```
Copy the above javascript under the *With javascript code* section.\
Example is provided below:
**3. Open your website's HTML page**\
Access the page on which your website is hosted with the tool allowing you to modify the files or log in to your respective platform Dashboard.\
**4. Paste the javascript code**\
Paste the javascript code in the HTML source page between the \`\<\head>\` tags.\
**5. Save changes**\
Save the changes, and that's it! Now, check your website and enjoy Tiledesk widget 🚀\
**6. Check your website**\
Go to your website and check if you can see the Tiledesk widget
---
# 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://guide.tiledesk.com/manage-your-workspace/install-widget-on-your-website.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.
.gif?alt=media&token=0ac93742-4323-43a0-b2dd-bc2b426f8b2a)