SuperBot for Squarespace

01

What SuperBot does on Squarespace

Add a real customer-support AI agent to your Squarespace site. SuperBot answers visitor questions from your live pages and policies, captures qualified leads, and routes the rest to your inbox — no rebuilding your site.

• Squarespace sites are content-heavy — SuperBot reads them and grounds answers in your actual prose.
• For a site that exists to generate enquiries, a short conversation qualifies a lead better than a static contact form.
• Multilingual replies open up international visitors who currently bounce off English-only sites.
• Booking and inquiry routing happens inside the chat — no detour to a 6-field form.

02

Before you install

The quality of the first answers depends on what a visitor can already read on your site, so publish your current shipping, returns, and contact information before training the agent. Have your site URL and one test page ready.

• Use the site that should be connected to this SuperBot workspace, not a staging copy.
• Check that your policy and product pages are written for customers rather than internal staff.
• Decide where escalations should land: the SuperBot inbox, Slack, or your existing support process.
• Copy the exact snippet from your SuperBot dashboard so the site ID routes conversations to the right workspace.

03

Install SuperBot on Squarespace

Settings → Advanced → Code Injection, in the Footer field. Save the Code Injection panel; changes are live on the published site immediately.

• Sign up for SuperBot free.
• Connect your Squarespace site URL — SuperBot crawls your pages and FAQs.
• Add SuperBot to your Squarespace site via Code Injection (one snippet in Settings → Advanced → Code Injection → Footer).
• Customize colors and tone to match your Squarespace theme.
• Publish your site. SuperBot is live.

04

Check that it is live

Open your site in a private window rather than the editor or preview, because most platforms only serve custom code on the published site. The launcher should appear in the lower corner within a second or two.

• Load a real published URL, not an editor preview or a password-protected page.
• Open the launcher and send a question you know the answer to, then confirm the reply cites your own content.
• Check one product or interior page as well as the home page, since templates can differ.
• If you run several languages or store views, check one page in each.

05

If the widget does not appear

Almost every failed install is one of four things: the change was never published, a cache is still serving the old page, the snippet carries the wrong site ID, or another script is stripping it.

• Code Injection is only available on paid Squarespace plans — a trial or personal-tier site may not have the panel.
• Squarespace's built-in visitor tools can sit in the same screen corner; move one of them if they overlap.
• Password-protected or unpublished pages will not load the widget.
• Open your browser console and look for a blocked request to superbotapp.ai, which points at a Content-Security-Policy or an ad blocker.
• Confirm the site ID in the snippet matches the workspace you are looking at in the dashboard.

06

Train and test before you send traffic

Approve a small, representative set of answers before the widget meets real customers. Test the questions that normally create tickets or stop a purchase, and correct the wording once so every later answer inherits it.

• Start with the ten questions your team answers most often.
• Check that policy answers link to the live page that supports them.
• Add a trained answer for anything the agent gets wrong rather than editing the source page twice.
• Decide what should escalate immediately — refunds, complaints, anything account-specific.

Common questions