Overview
Add Voiceflow’s widget to your Squarespace site so visitors can ask your AI agent about your products, policies or services. This guide installs the floating widget through site-wide Footer Code Injection on Squarespace 7.1 or 7.0.
Building your own interface? Custom chat and voice walkthroughs are coming soon. Start with Chat agents or Voice agents for the APIs.
New to Voiceflow? Build a support agent, add your help content to Knowledge and publish it before connecting the site. This installation provides public support; it does not connect customer accounts or orders.
Before you begin
Check your plan and permissions before copying the widget code.
Before copying the snippet, open Widget → Modality & interface in Voiceflow. Set Modality to Chat and Chat interface to Widget, then publish.
Check Squarespace’s current Code Injection availability, legacy plans and contributor permissions. If an administrator handles setup, send them the full snippet and test question, then ask for the test URL.
Install the widget
Save the generated snippet in the site-wide footer field.
Copy the installation snippet
In Agent studio, open your project’s Widget → Installation panel. Copy the complete snippet, including its script tags. Keep its generated authorization, runtime and environment settings unchanged. Do not use a personal or service API key in browser code.
Open Code Injection
In Squarespace, open Website → Pages. At the bottom of the Pages panel, choose Custom Code → Code Injection. On version 7.0, find Code Injection under Website Tools instead.
The Pages panel guide covers these navigation differences.
Save the footer snippet
Paste the full snippet into Footer, keeping any unrelated code, then choose Save. Squarespace inserts this field before the closing body tag across the site. Do not also add the widget through a Code Block or individual page injection.
Open the site URL in a private browser window. The launcher should appear; continue with the visitor test.
This footer installation does not add the widget to checkout. Keep the floating widget at the site level rather than inside an iframe, which confines it to the embedded element.
Configure appearance and sessions
Use Voiceflow settings for the widget and Squarespace for installation.
In Voiceflow’s Widget settings, choose the launcher, colors and icon, then publish the changes. If you change the installed project or release routing, replace the Footer snippet with the corresponding generated code. See widget environment selection for explicit routing.
For page-specific visibility, have the site developer implement that behavior and test included and excluded URLs after navigation. Keep protected account actions behind backend authorization; a customer ID supplied by browser code does not prove account ownership.
Test a visitor conversation
Verify the installed widget on the site URL, outside the editor.
Open the site as a visitor
Open the site URL in a private browser window, supplying the site password if required. Confirm that a normal page shows one launcher and that it opens. Squarespace may disable custom scripts in its editing preview, so use the site URL for this test.
Ask a question and follow-up
Ask a prepared question, such as “What are your delivery options?” Then ask “How long does standard delivery take?” Both replies should match the content in your agent’s Knowledge.
Check the project and page coverage
Find the exchange in Transcripts to confirm the intended project. Navigate to another page, send a message and reload. Check conversation retention and any page-visibility rules. If the site uses consent controls, repeat with the relevant consent choices.
Code Injection is unavailable
Ask the site owner to confirm an eligible plan and Owner or Administrator access. A Website Editor can add some page content without being allowed to edit Code Injection. Recheck eligibility after a plan change.
The widget is absent in preview
Use the site URL to check custom scripts.
If Squarespace reports that scripts are disabled in preview, open the site in a private window. This editor setting does not establish whether the script works for visitors. Confirm the Footer field was saved and inspect Console and Network on the visitor page for blocked requests or initialization errors.
The widget is missing or duplicated
Check placement, other snippets and browser errors.
Keep one Voiceflow installation in the site-wide Footer field. Remove copies from Code Blocks, header injection or page-specific fields. If the script is present but the launcher is missing, review consent and security rules with the site owner and check requests to cdn.voiceflow.com. Checkout is outside this installation.
The answer is wrong or missing
Verify the installed project and published agent.
Compare the Footer code with the Voiceflow project’s generated snippet. Check that the intended release is published and retry with a fresh conversation. Correct missing delivery or policy information in Knowledge and instructions.
Maintain the live installation
Treat Footer saves and agent publication as separate changes.
Saving Code Injection updates the site; it is not waiting for a separate widget publish action. Use a separate test site if you need to review the installation without changing the production site.
- Publish the reviewed agent and widget settings in Voiceflow.
- Save the correct snippet in the production site’s Footer field.
- Repeat the visitor test on the production domain.
Update or remove the widget
Maintain the footer code after release.
Publish agent and appearance changes in Voiceflow. Replace the Footer snippet when its generated installation details change. Recheck the visitor route after a plan change, site redesign or changes to consent scripts.
To remove the widget, delete only its snippet from Footer, choose Save, then open a fresh visitor window and confirm that the launcher is gone. Keep unrelated footer code intact.
Custom interface guides
Planned Squarespace walkthroughs for your own conversation UI.
Custom chat and voice walkthroughs are coming soon, separately from this widget guide.