Add AI chat to a Notion site

Installation steps

1. 1

   Prepare

   Identify whether the public page is hosted directly on notion.site or through Super.so or Feather.

2. 2

   Configure

   For Super or Feather, locate its current custom code or footer injection option and confirm the plan supports scripts before adding the loader.

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

   Copy
3. 3

   Publish

   Publish through that service and allow the final public origin in MivoChat; a Notion editor preview is not the visitor origin.

4. 4

   Verify

   Test from the published URL. If using plain notion.site without an approved script feature, link to a separate chat-enabled support page instead.

Know which layer publishes the page

Notion content and a Notion publishing service are different execution environments. A plain notion.site page does not provide an arbitrary script slot, so a code block containing the tag is only displayed content and cannot install chat.

Super and Feather provide their own publishing controls, and their menus and plan capabilities may change. Use only a currently documented custom-code feature in the service that publishes your page; do not assume a setting in Notion itself applies to the public rendered site.

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

A link is the fallback

If your publisher does not allow custom JavaScript, add a visible support link to a page on your own website where the MivoChat widget is installed. This keeps the route usable without presenting a non-running script as an integration.

After an injected install, inspect the actual published HTML for widget.js and test on the final hostname. Each custom domain is a distinct origin that may need to be allowed in MivoChat.

Before you change the setup

Who this is for

a Notion site publisher using a service that can execute custom JavaScript

What you need

a Super or Feather published site, a supported script setting, and the final public origin

Where it goes

the current custom code or footer injection setting in Super.so or Feather

Watch out for

plain notion.site does not run arbitrary custom scripts; a code block is not a loader

Test the support boundary

• Does the chosen publisher preserve the script in the public HTML?
• Does the final custom domain show the launcher?
• Can a visitor reach a person if the source does not answer?

Related guidance

For other supported custom-code sites, see /guides/webflow and /guides/static-site-generators; the HTML guide explains the shared loader.

Frequently asked questions