Skip to main content

Add BotStacks to Squarespace

Before you start​

Have a BotStacks assistant ready to deploy and permission to edit your website. In BotStacks, open Add to website and use the generated instructions for your current account/environment. Keep the assistant and site selection consistent throughout setup.

The current widget uses a public Bot ID. Copy the generated snippet rather than entering an OpenAI or other model-provider API key. Keep the script URL and API origin from the same BotStacks environment. Do not add a separate charset meta tag.

Check plan eligibility​

Squarespace Code Injection is available on Core, Plus, Advanced and some legacy plans. Check the current Code Injection guidance for your account. Checkout pages do not support this code.

This setup uses Code Injection. It is not evidence of an approved native Squarespace Extensions listing.

Add your assistant​

  1. Copy the generated snippet in BotStacks Add to website → Squarespace.
  2. Open your site's Code Injection panel in Squarespace. Use the official guide above if navigation differs in your account.
  3. Paste the snippet once into Footer, preserving other existing code.
  4. Choose Save and open the public site outside the editor.
  5. Send a test message to confirm the correct assistant responds.

The footer field inserts code before the closing body tag across the site. Do not use a redirect to your own site as confirmation that installation occurred.

Update or remove​

Keep your Bot ID and snippet environment consistent. For removal, delete only the BotStacks snippet from Footer, save and reload the public site. Leave unrelated code intact. If using both page-level and site-wide code, remove duplicate BotStacks copies as well.

Check your published site​

Open the public domain outside the editor, including a private browser window. Check the launcher, send a test message, navigate to another page, and check the mobile layout. An editor install, callback or “detected” signal alone does not prove the assistant can answer visitors.

If it does not appear, confirm the assistant is published, the site is saved/published, the Bot ID and environment are correct, and the script is not blocked or installed twice. Keep other site scripts intact while troubleshooting. Contact BotStacks through the Help area in your account with the platform, public site URL and error; do not send credentials or handoff tokens.

Existing legacy installations​

If your working installation uses webassistant.js or initBotStackAssistant, it follows an older integration. Test the current generated snippet on a staging/test site before switching. Remove the older embed when the replacement is verified so visitors do not see duplicate assistants.