Add AI chat to Duda

Installation steps

1. 1

   Prepare

   Open Duda Site settings and locate the supported custom HTML field for the head or end of body.

2. 2

   Configure

   Paste the full loader into one site-wide location; if Duda's current labels differ, check its site settings documentation.

   <script src="https://mivochat.app/widget.js" data-site="YOUR_SITE_KEY" async></script>

   Copy
3. 3

   Publish

   Publish the site and allow each public hostname visitors use in MivoChat.

4. 4

   Verify

   Inspect a live page for widget.js and test questions from pricing, help, and docs before inviting customers.

Use a site-wide HTML control

A head field or body-end field is preferable to a visual content widget because it runs as page code across the intended site. Duda labels and role permissions may change, so confirm the current Site settings controls before selecting a location.

Keep one copy of the loader. If your template already injects scripts, check that it is not also adding MivoChat before pasting another tag.

<script src="https://mivochat.app/widget.js" data-site="YOUR_SITE_KEY" async></script>

Publish and confirm

Save and publish, then check the actual public domain rather than the builder preview. Add both a Duda preview hostname and custom domain to Allowed websites only if you test both.

The live HTML should contain one widget.js loader. If the launcher is absent, inspect the request and console before moving the snippet to another field; consent tooling and CSP can block an otherwise correct install. For a multi-language or multi-location site, verify a page from each relevant template and confirm the same site key is intended for those domains. If the site uses a cookie banner, decide how support chat should behave before changing consent categories, then test with the same consent choice a visitor will make. Also make sure the help and pricing pages use the expected layout, not a one-off campaign template.

Before you change the setup

Who this is for

a Duda site owner adding site-wide chat through custom HTML settings

What you need

Duda site settings access, the widget site key, and the public hostname

Where it goes

Site settings → Head HTML or body-end HTML, whichever current control accepts the loader

Watch out for

Builder previews and published sites can have different code behavior and origins

Test the support boundary

• Does one loader appear in the live page source?
• Does an approved production hostname show the widget?
• Can a teammate complete the handoff?

Related guidance

Use /guides/html for the basic tag and /guides/content-security-policy if the browser reports a policy violation.

Frequently asked questions