Squarespace AI Chatbot: Add a Shopping Agent
Squarespace has no built-in live chat for shoppers. Add an AI assistant through Code Injection and confirm it answers from your products and policies.
Yes, you can add a Squarespace chatbot through Code Injection on a plan that supports custom scripts. Connect your product catalogue and store policies separately so the assistant can answer shoppers’ questions.
shoppa is an AI shopping agent you add with two lines of code. It helps customers find, compare and buy products in one chat, using your catalogue and documents. For a Squarespace storefront, the embed displays the agent while your product feed supplies what it knows.
Squarespace AI and Chat Options
Squarespace AI helps you build and edit your site, including drafting product descriptions and page copy. Blueprint AI creates a starting site, while Clarkson AI chat helps the site owner make changes. These editing tools serve a different purpose from a shopper-facing assistant.
Squarespace has no built-in live chat for shoppers. Add a separate chat service to answer questions on your storefront. Human live chat connects customers with your staff. An AI assistant answers automatically from the information you supply.
Choose an AI shopping agent when customers need help finding a product as well as asking about delivery. If you need staff to handle conversations, the live chat software guide explains that choice.
Plans That Allow Code Injection
Code Injection is available on Squarespace’s Core, Plus and Advanced plans. Legacy Business, Commerce Basic and Commerce Advanced plans also support it. The current Basic plan and legacy Personal plan don’t include this feature.
When you downgrade to a plan without premium code features, access continues until your current billing period ends. After the lower plan takes effect, the injected script can no longer provide the same storefront function. Keep a copy of the embed before changing plans, then choose a plan with Code Injection to run it again.
Squarespace’s Code Injection guide lists the supported plans and where injected code runs. Your website subscription and shopping-agent subscription are separate costs.
Adding the Script With Code Injection
Paste your store’s two-line shoppa embed into the site-wide Footer field in Code Injection. This puts the script before the closing body tag on your storefront pages.
- Copy the embed supplied for your store, including its retailer identifier.
- Open your Squarespace site’s Settings. Find Code Injection under Developer Tools or Advanced, depending on your site’s menu.
- Open Code Injection and paste both script tags into Footer. Preserve any unrelated code already in that field.
- Click Save, then open the storefront in a private browser window.
- Open the agent and send a product question. Follow a product link to another page and confirm the agent is available there too.
Use the site-wide field once. Adding the same script to individual pages as well can load it twice. Keep the two script tags in their supplied order because the second initialises the agent loaded by the first.
If Squarespace disables scripts in the editor preview, inspect your public site in a private window. The preview and the visitor’s storefront can behave differently. The shoppa setup process explains the feed and embed steps that apply across storefronts. For stores on another platform, use the platform integration guides.
Giving the Agent Your Catalogue
Your Squarespace product data reaches shoppa through a JSON or CSV product feed. The embed displays the agent. It doesn’t turn every page on your site into product knowledge.
Start with Squarespace’s product export. Open Products & Services, choose Products and select Export all, or select particular products to export. Prepare that data for shoppa’s feed import, then inspect the import preview before publishing it.
Include product identifiers and descriptions, prices and availability, images and product-page links. Supply variant details such as size and colour when they affect a recommendation. Product links must lead to the matching Squarespace product page, including the correct variant where applicable.
A CSV export is a snapshot. Changes in Squarespace don’t automatically update the exported file or the agent’s catalogue. Set a refresh process that imports changed products and stock before customers receive stale answers.
Add your shipping and returns information as knowledge documents in shoppa’s workspace. Use the text from your store’s policy pages, including delivery regions, dispatch times and return exclusions. Update those documents when the public policies change. shoppa answers from this material and your catalogue, so omitted conditions won’t become reliable answers by installing the script.
Limits and Checks
Code Injection adds the agent to storefront pages, but Squarespace’s checkout pages don’t support custom code. Installing a chat script alone doesn’t establish a connection to the Squarespace Commerce basket or payment flow.
shoppa supports buying in the chat. Keep that capability distinct from controlling Squarespace’s own cart. Product cards can link shoppers to your Squarespace product pages, where they can use the store’s existing purchase flow.
Run these checks on the saved storefront before directing customers to the agent:
- Open a product page on a phone. Open and close the agent, then type a message with the keyboard visible. Confirm it doesn’t cover the store’s purchase controls.
- Ask for a product with a specific size or colour. Compare the answer and linked product with the catalogue record.
- Ask about delivery to a region you serve, then about a region you exclude. Compare both answers with your shipping policy.
- Ask about a return exclusion. Confirm the answer includes the condition from your returns document.
- Follow a product card through the Squarespace purchase flow. Confirm its link reaches the intended product and your existing basket still works.
- Change a product’s availability, refresh the feed and repeat the product question. Confirm the answer reflects the update.
Save the questions you use so you can repeat them after a catalogue refresh or policy change. A working chat button confirms installation. Correct product and policy answers confirm the data connection.