Install on Any Website
The widget is two script tags. It works on any site where you can edit the HTML: Webflow, Squarespace, Shopify, a hand-written page, or a framework app.
1. Copy Your Snippet#
In the Chatleadr dashboard, open your bot and go to Channels, then open the Website Snippet card. The snippet shown there is already filled in with your bot key.
<!-- Chatleadr Widget Installation -->
<script>
window.CHATLEADR_BOT_KEY = "your-bot-key";
window.CHATLEADR_API_URL = "https://chat.chatleadr.com";
</script>
<script src="https://chat.chatleadr.com/widget/app.js"></script>2. Paste It Before the Closing Body Tag#
Put the snippet at the end of the page, just before </body>, on every page the widget should appear on. Most sites have one template that produces this for the whole site.
| Platform | Where | Full guide |
|---|---|---|
| Wix | Settings → Custom Code → Add Code → Body end | Chatbot on Wix |
| Shopify | Online Store → Themes → Edit code → theme.liquid, before </body> | Chatbot on Shopify |
| Squarespace | Settings → Advanced → Code Injection → Footer | Chatbot on Squarespace |
| Webflow | Project Settings → Custom Code → Footer Code | Chatbot on Webflow |
| WordPress | Install the plugin instead | Install on WordPress |
| Plain HTML | Before </body> in each page, or in a shared footer include |
Each platform guide adds that platform's own detail: which plan allows custom code, whether the site must be published first, and which areas of the site the widget reaches.
3. Check It#
- Load your site in a private window.
- Within a second or two, the launcher appears in the corner.
- Send it a message and confirm a reply comes back.
- Check your bot's Analytics page. The figures are rebuilt every five minutes, so allow that long for the conversation to appear.
A visible launcher confirms the bot key reached the page. If no reply arrives, check the bot is switched on, then work through my workflow is not triggering.
Common Problems#
The launcher never appears. Open the browser console and the network tab. A 404 on app.js means the script URL is wrong. A failed /chat/<botKey>/config request means the key is wrong or the bot is archived. No request at all means the snippet is not on the page: view source and search for CHATLEADR_BOT_KEY.
It appears on some pages only. The snippet is in a page template instead of the site-wide one. Most site builders have both.
It appears twice. The snippet is in two places, commonly a theme setting and a manual paste. Remove one.
Nothing happens in a single-page app. The widget mounts once, when the script runs, so put the snippet in the shell that survives navigation rather than inside a route.
Common Questions#
Does the Widget Slow My Site Down?#
No. The script loads at the end of the page and does not block rendering. It fetches its configuration after the page is interactive, so the launcher appears a moment after the rest of the page.
Can I Put the Widget on More Than One Domain?#
Yes, as long as you add every address. A bot answers on the Domain on its Setup tab and on the addresses in Additional domains on the same tab, one per line, up to 20. Connecting a site with the Chatleadr WordPress plugin adds that site for you. Set the Domain before you paste the snippet anywhere: once the widget has loaded on a site, that field is locked.
www.example.com and example.com are the same website here. Any other subdomain is not: shop.example.com answers only when you add that address too. A marketing site and a separate store can share one bot, but they get the same knowledge and the same workflows, so two brands that need different answers are better served by two bots. Bots are a plan limit, so check plans and limits before splitting a site in two.
How Do I Remove the Widget From One Page?#
Move the snippet out of the site-wide template and add it only to the pages that should have it. On WordPress the plugin has visibility settings that do this without editing anything.
Where Do I Find My Bot Key?#
On the bot's Channels tab, already filled into the snippet shown there. The bot key is visible in your page source and needs no protection. The WordPress secret key is a different value and must stay private.