# Add an AI chatbot to your Wix website.

Add WebotX to Wix through dashboard Custom Code, apply the widget script to all pages, and place it at Body – end. Publish your website, confirm the final domain is allowed in WebotX, and test both the first page and later page navigation.

Canonical: https://webotx.com/platforms/wix
Updated: 2026-11-05

## Use dashboard Custom Code for a floating widget

A floating chat launcher belongs to the website as a whole. Use Wix's dashboard Custom Code controls rather than placing the assistant inside an embedded HTML frame. Check Wix's current domain and publishing requirements for your site before starting.

Decide which services and policies the assistant should explain. If a visitor asks about a private booking or personal account, plan a handoff to your team. Adding a script does not connect WebotX to private Wix business records.

## Match the assistant to your Wix site's published information

Add the public Wix website to WebotX, then inspect the captured service pages and business overview. Edit inaccurate summaries before approving the overview and at least one included page. Try a service-area question in Live simulator and verify that the answer is supported by the right source.

In Install widget, publish the assistant and allow the final Wix website origin. Copy the script for that workspace before opening Custom Code. If visitors are redirected to your connected domain, configure that destination rather than assuming an editor or preview address is the correct origin.

![Install widget screen with publishing requirements and the Allowed widget origins field](https://webotx.com/docs/screenshots/example-install-widget.jpg)

Install widget brings together publishing checks and allowed origins. In this example, publishing is still unavailable because the overview needs approval.

- [Review the knowledge approval workflow](https://webotx.com/docs/knowledge)

## Install through Wix Custom Code

Use the published site's dashboard. The Wix documentation linked below explains its Custom Code options and current requirements.

1. Publish your Wix site and confirm that the domain is connected.
2. Open Settings → Custom Code, add a snippet, and paste your complete WebotX script.
3. Name the snippet WebotX, apply it to all pages, and select the option to load once per visit.
4. Choose Body – end, apply the change, and check the published website.

## The Wix widget script

Paste the generated workspace script as one Custom Code snippet. The placeholder below explains the format; use the real key supplied by your WebotX workspace. Keep this as the single widget installation rather than also adding it through an HTML frame.

Wix controls the snippet's page placement and loading option. WebotX supplies the greeting, approved answers, and follow-up workflow. Confirm both sides of that setup when checking a new domain or a redesigned site.

```html
<script
  src="https://webotx.com/widget.js"
  data-webotx="YOUR_WIDGET_KEY"
  async>
</script>
```

## Test navigation on the published site

Open the public homepage, navigate to a service page, and refresh that page directly. The launcher should remain usable without creating duplicate widgets. Check a narrow mobile viewport too, especially near fixed booking buttons or mobile navigation.

Test a question with an approved source and a request for a person. If you connect a different domain later, review the Wix snippet and WebotX allowed origins again. The final address in the visitor's browser is the origin that matters.

- Use the published website, not only the Wix editor.
- Check that Custom Code is enabled for the intended pages.
- Ask an unsupported question and review the result in WebotX.

## Troubleshoot Wix setup

Use a published visit to separate Wix placement and domain problems from answer quality. If the assistant opens normally, inspect the approved facts for the missing answer instead of changing Custom Code settings repeatedly.

| What you see | What to check |
| --- | --- |
| Missing in the editor or preview | Verify the published site before treating an editor-only difference as a failure. |
| Missing after a domain change | Review the Wix snippet and update WebotX's allowed origin. |
| Duplicate launchers after navigation | Remove other installations and review the once-per-visit setting. |

- [Open the complete troubleshooting guide](https://webotx.com/docs/troubleshooting)

## Wix: common questions

### Should I use a Wix HTML embed for the chatbot?

Use dashboard Custom Code for this floating website widget. An HTML embed creates a separate frame and is not the site-wide installation described in this guide.

### Why should I test the published Wix website?

The public site is where visitors run the script. Editor and preview behavior can differ, so verify the launcher, allowed origin, and questions on the actual published domain.

### Does this connect WebotX to Wix bookings?

The script displays the assistant and does not provide access to private booking records. It can explain approved public service information; booking-specific requests need an appropriate team follow-up.

## Official platform documentation

Check the platform's current controls and plan requirements alongside this guide.

- [Wix: embedding custom code on your site](https://support.wix.com/en/article/wix-editor-embedding-custom-code-on-your-site)

## Continue with the next step

- [Website chatbot for lead generation](https://webotx.com/use-cases/lead-generation)
- [Prepare your first assistant](https://webotx.com/docs/getting-started)

## Support

Email: [support@webotx.com](mailto:support@webotx.com)