Skip to main content
Wix Editor supports visible HTML and site embeds. Use this guide to prepare a test location; it does not supply a released Threetone widget snippet or prove Wix compatibility.

​
Choose an embed type

In Wix Editor, open Add Elements > Embed Code > Popular Embeds. Embed HTML accepts a snippet, while Embed a site accepts an external URL. Both use an iframe. Wix requires HTTPS and cannot override a destination’s policy that forbids embedding. See Wix’s embed guide. A future widget release must explicitly support the selected embed context. Do not substitute a dashboard or API URL for a public widget URL.

​
Prepare and test

1

Reserve a usable container

Place the test embed where it has room for controls, transcript, and errors. Check the desktop and mobile layouts separately. Container dimensions can crop an interface even if its content uses relative sizing.
2

Review the released asset

Confirm whether the widget supplies supported HTML or a hosted URL. Inspect the required origin, frame policy, permission policy, and session access. Public embed fields must not contain workspace API keys.
3

Inspect the published result

After a supported release, test the actual site URL. Give the embed a useful accessible description. Confirm keyboard access, readable error states, session end, navigation cleanup, and microphone permission behavior for a voice interface.
Keep a contact link outside the iframe. If the frame is blank, inspect loading and frame-policy errors before changing the page layout. If content is clipped, test the expanded interface at each target size. Remove the test embed if it interferes with navigation or essential site controls. See widget preparation and current availability before planning a public launch.

​
Frequently asked questions

Do not assume it will. Wix’s embed container has its own dimensions. Test the supported widget at desktop and mobile sizes, including expanded and error states.
A destination’s security policy still applies. Use an installation method that the widget release supports rather than trying to bypass that policy.