> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Embed the Voiceflow widget in GoDaddy

> Add a Voiceflow AI agent to GoDaddy Websites + Marketing with an embedded chat widget. Configure an HTML section, test a conversation and publish the page.

## Overview

Embed Voiceflow’s chat widget in a **GoDaddy Websites + Marketing** page so visitors can ask your AI agent about your products, policies or services. GoDaddy places custom HTML inside an iframe, so this guide displays chat **within a page section** rather than as a site-wide floating launcher.

Using GoDaddy to host WordPress? Follow the [WordPress widget guide](/docs/guides/channels/web/wordpress) instead. Registering a domain with GoDaddy does not determine how a website installs the widget.

**Note:** 

**Building your own interface?** Custom chat and voice walkthroughs are [coming soon](#custom-interface). Start with [Chat agents](/docs/api-reference/agent-runtime/chat) or [Voice agents](/docs/api-reference/agent-runtime/voice) for the APIs.

New to Voiceflow? [Build a support agent](/docs/guides/usecases/customer-service/build-faq-agent), add your help content to Knowledge and publish it first. This widget guide provides public support, without customer-account access.

<a id="before-you-begin"></a>

## Before you begin

Prepare an embedded widget and access to the website’s HTML section.

| Requirement | What to prepare |
| --- | --- |
| Voiceflow agent | A published agent, its generated installation snippet and a known-answer question. |
| GoDaddy product | A **Websites + Marketing** site with an **HTML** section available in the builder. |
| Site administrator | Someone who can edit the section, adjust its height and publish the site. |
| Test page | The page where visitors will open chat, such as Support or Contact. |

In Voiceflow, open **Widget → Modality & interface**. Set **Modality** to **Chat** and **Chat interface** to **Embed**, then publish. Copy the full snippet from **Widget → Installation**. You will supply its target element below.

If another teammate owns the site, send them the snippet and test question, along with the container and configuration instructions in this guide. Keep personal and service API keys out of browser code.

GoDaddy’s [HTML-section guide](https://www.godaddy.com/help/add-html-or-custom-code-to-my-site-27252) and [iframe limitations](https://www.godaddy.com/help/troubleshoot-html-or-custom-code-not-displaying-properly-28025) describe this installation surface.

<a id="install-widget"></a>

## Embed the widget

Create the chat container inside one GoDaddy HTML section.

### 1. Add an HTML section

From your GoDaddy product page, open **Websites + Marketing → Manage → Edit Website**. Go to the intended page and add a section. Search for **HTML**, then choose **Add**.

Use one section for this widget. A second section creates another embedded interface.

### 2. Create the chat container

Paste this into the section’s **Custom Code** field:

```html
<style>
  html, body { margin: 0; }
  #voiceflow-chat { width: 100%; height: 600px; }
</style>
<div id="voiceflow-chat"></div>
```

Paste your **complete generated Voiceflow snippet immediately after this container**, including its script tags. Keep its loader and generated authorization, runtime and environment settings.

### 3. Point the widget at the container

Inside the generated `window.voiceflow.chat.load({ ... })` configuration, replace its `render` property with the following, and set `autostart` to `true`:

```javascript
render: {
  mode: 'embedded',
  target: document.getElementById('voiceflow-chat')
},
autostart: true
```

These properties belong inside the existing configuration object; they are not a second script or a second `chat.load()` call. Keep its `verify`, `url`, `voice` and any environment properties intact. Use a comma between properties, and keep only one `render` and one `autostart` property.

The target ID must match the container above. The generated `document.getElementById(...)` placeholder needs this real element; leaving it unchanged does not create a working embed.

### 4. Set the section height

Set **Forced Height** to **600** pixels to match the container. GoDaddy saves section edits automatically. Use **Preview** to inspect the section, then publish to your test site when ready for the [visitor test](#test-conversation).

A chat window should occupy the section. This embedded mode has no floating launcher.

<a id="configure-widget"></a>

## Configure appearance and placement

Keep the conversation inside its page section.

Choose colors and other interface settings in Voiceflow’s **Widget** panel, then [publish the changes](/docs/documentation/deploy/environments/publishing). GoDaddy owns the section’s title, position and dimensions.

| Change | What to update |
| --- | --- |
| Move chat to another page | Move or recreate the HTML section there, then remove the old section. |
| Change chat height | Change both the container’s CSS height and GoDaddy’s **Forced Height** to the same value. |
| Change the project or release | Replace the generated snippet, then reapply the container target and `autostart` properties. |

Conversation retention follows the [widget persistence configuration](/docs/documentation/deploy/widget/web-chat-api#configuring-chat-persistence) and the storage available inside the iframe. Do not assume it shares the parent site’s login, storage or conversation across pages. Test navigation and reload in the browsers your visitors use.

GoDaddy customer accounts and browser-supplied IDs do not authorize protected agent actions. Account-aware support requires a separate backend authorization flow.

<a id="test-conversation"></a>

## Test a visitor conversation

Verify the embedded interface on the published GoDaddy page.

### 1. Open the published page

Open the test page in a private browser window. Confirm that the chat window, message field and send control fit inside the section. Expect embedded chat rather than a corner launcher.

### 2. Ask a question and follow-up

Ask a prepared question, such as “What are your opening hours?” Then ask “How do I make an appointment?” Both replies should match the help content in your agent’s Knowledge. Check that longer replies scroll inside chat and that the message field remains reachable.

### 3. Check the project and return visit

Find the exchange in [Transcripts](/docs/documentation/measure/transcripts) to confirm the intended project. Navigate away, return and reload; check the conversation’s retention behavior. A page without the HTML section should have no chat. If consent controls are present, test their relevant choices too.

<a id="troubleshooting" />

### Chat is blank or shows a launcher

Check the target element and embedded mode.

Confirm the container appears before the generated snippet in the same HTML section. Its ID must match `render.target`, and `render.mode` must be `embedded`. Check for an unreplaced target placeholder or a JavaScript syntax error. A missing target can cause an initialization error or an overlay fallback; correct the target rather than resizing a clipped launcher.

### The message field is cut off

Match the section height to the container.

Set a positive **Forced Height** and use the same height in the container CSS. Increase both if the conversation needs more space. The widget stays within GoDaddy’s iframe; increasing its CSS alone does not enlarge the outer section.

### The widget does not load

Inspect requests from the HTML section’s frame.

Check Console and Network for a blocked `cdn.voiceflow.com` request, initialization error or rejected widget setup. Have the site developer inspect the HTML section’s iframe as well as the parent page. Review domain and consent restrictions with the project owner; do not assume the frame makes requests from the parent page’s origin.

### The answer is wrong or missing

Check the snippet and published agent.

Compare the saved generated options with the Voiceflow project’s snippet, keeping the documented embed properties. Check the intended release is published and retry with a fresh conversation. Correct missing hours or booking information in Knowledge or instructions.

<a id="go-live"></a>

## Publish the chat section

Release the website edit separately from the Voiceflow agent.

1. Have the Voiceflow owner publish the reviewed agent and widget settings.
2. In the GoDaddy builder, review the pending website changes and choose **Publish**. If you used a separate test site, apply the reviewed section to production first.
3. Repeat the [visitor test](#test-conversation) on the production page.

Saving a section does not publish it. GoDaddy’s [publishing instructions](https://www.godaddy.com/help/publish-my-websites-marketing-site-20115) cover that final website action.

### Update or remove the widget

Maintain the section and its configuration.

Publish agent and appearance changes in Voiceflow. When installation settings change, replace the generated snippet, retain the real container target and republish the site.

To remove chat, delete its HTML section and publish. Open the public page in a fresh window and confirm the embedded interface is gone. Keep unrelated HTML sections intact.

<a id="custom-interface"></a>

## Custom interface guides

Planned GoDaddy walkthroughs for your own conversation UI.

Custom chat and voice walkthroughs are **coming soon**, separately from this embedded-widget guide.

| Planned guide | API reference |
| --- | --- |
| Add custom chat | [Chat agents](/docs/api-reference/agent-runtime/chat) |
| Add custom voice | [Voice agents](/docs/api-reference/agent-runtime/voice) |
