How to Add an AI Chatbot to Squarespace

Before you start

This guide uses PrimeWebKit's standard website widget: one external script that loads the chatbot configured in your account. It does not install a native Squarespaceplugin or automatically connect your site's private data. The platform-specific steps below explain where the snippet belongs and what to verify before making a live change.

• A published PrimeWebKit bot with its own widget script copied from the Widget tab.
• Squarespace site-owner or administrator access to the site's code-injection settings.
• A Squarespace plan and site configuration that currently allow custom code injection; verify this in your account.
• The public site domain allowed in the bot's domain settings, if the bot restricts where its widget can appear.

Installation steps

1. 1. Find site-wide code injection

   Editor or file path: {{VERIFY: Squarespace dashboard → current site settings → Code Injection; verify the exact menu labels and plan support in Squarespace help}}

   Squarespace settings and plan limits can change. Use the platform's current official instructions to locate site-wide footer injection and check whether your subscription allows it. The precise menu path is not present in this project's existing documentation and is intentionally marked for verification.

2. 2. Paste the bot snippet in the footer field

   Editor or file path: {{VERIFY: Code Injection → Footer or equivalent site-wide body-end field}}

   Paste the full script copied from PrimeWebKit into the site's footer injection field, preserving the bot ID and script URL. Avoid adding the same snippet in both global code injection and an individual page block. A site-wide placement lets the floating widget remain available as visitors move between site pages.

3. 3. Save, publish, and check a public page

   Editor or file path: Squarespace site settings → Save; then publish the site if prompted (verify current control labels)

   Save your changes and test a public page in a fresh browser tab. Confirm that the widget appears and opens rather than relying only on the editor preview. If Squarespace changes or removes the code-injection option, do not switch to an unrelated setting; verify support in its current help material.

The menu paths marked {{VERIFY}}are not confirmed by the existing project documentation. Check the platform's current first-party help and your account's available features before applying them.

Widget snippet

Copy the snippet from the selected bot's Widget tab whenever possible. The example below shows the format for your reference; replace the example identifier only with the bot ID from your own copied snippet.

<script src="https://api.primewebkit.com/widget.js" data-bot-id="YOUR_BOT_ID" async></script>

Example format only. Copy the bot-specific snippet from the Widget tab and use it only in a Squarespace location confirmed to allow external scripts.

Platform-specific notes

The widget is an external script, so a code field that escapes or sanitizes script tags will not work. Confirm how Squarespace handles footer injection for your site and whether custom code runs on every page before treating installation as complete.

When using page-level code blocks, the widget may appear only on that page or may execute in a restricted context. Prefer the verified site-wide footer mechanism if available and permitted for your account.

Before publishing, review any site-wide consent banner, security policy, and domain restrictions already in place. Add the widget only to the pages and hostnames where it is intended to run, and avoid copying account secrets or private customer data into the page source.

Verify the chatbot is working

Test a published page, not just an editor preview. Confirm the launcher is visible, opens when activated, and accepts a question. Ask something answered by the bot's current knowledge sources, then check that an unrelated or unsupported question is handled within the limits of the bot's instructions.

Repeat the check on another page that shares the layout and on each hostname visitors use, such as a staging host and the production domain. If the bot is restricted to allowed domains, include the exact hostname for each environment before testing. Inspect the browser console and Network panel if the script or API request fails; record the specific error rather than changing unrelated settings.

Common problems

Frequently asked questions