Install on your platform

The Nexvio widget is a <script> tag plus a <nexvio-widget> marker containing your agent public key. No server-side code or npm package is required for this floating launcher. Your site builder must allow both the HTML marker and executable JavaScript in the published page.

The embed snippet

Every install starts with the same snippet, copied from the agent's Widget tab in the dashboard:

<script src="https://app.nexvio.ai/api/agent.js" async></script>
<nexvio-widget id="pk_..."></nexvio-widget>

• The <script> tag loads the widget runtime, which reads the <nexvio-widget> marker and creates a floating chat launcher.
• id is the agent's public key (starts with pk_). It is safe to expose in browser HTML. Keep this value as the public key; replacing it with a custom HTML/CSS ID makes the widget use that ID as its key.
• Optionally set window.nexvioConfig before the <script> tag loads to control appearance, identity, or behavior. See Widget SDK Reference.

The only thing that differs between site builders is where you paste this snippet, because each platform exposes custom code in a different place. Pick your platform below for the exact steps.

Platform guides

• WordPress — theme footer, a header/footer plugin, or a Custom HTML block.
• Wix — Custom Code panel in Wix Settings.
• Webflow — site-wide custom code or a page Code Embed element.
• Framer — Project Settings → Custom Code.
• Bubble — SEO/metatags body code or an HTML element.
• Weebly — Embed Code element in the classic Weebly editor.
• Squarespace — site-wide Code Injection or a JavaScript-enabled Code Block.

General tips

• Paste the snippet once per page, preferably in a site-wide body/footer code area. Avoid installing it in both a site-wide area and a page block.
• If a platform only lets you add code to a single page, the widget will only appear on that page.
• After publishing, always reload the live (published) site, not the editor preview — some builders don't execute custom <script> tags inside the editor canvas.
• Use the browser Network tab to check the agent.js request, then confirm the launcher appears and responds. A marker in the DOM or a successful script download alone does not prove the widget initialized.
• Place the marker in the initial page HTML. If your builder inserts it later without reloading the page, the script may already have scanned the page; use the Widget SDK Reference for explicit initialization.
• Platform menus and eligibility change. The guides link to official guidance; confirm custom JavaScript access in your current editor before choosing a placement.