To add an AI chatbot to Squarespace, build the bot in a tool such as Tidio or Chatbase, copy its embed script and paste it into the Code Injection footer field. Your plan must include code injection (Squarespace lists Core, Plus and Advanced), so check that first. Then save, open the live site in a private window and test on a phone.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowSquarespace has no native AI chatbot for this job, so the widget runs from the vendor's servers and your site only loads a small script. That keeps the setup short, but it also means the fiddly parts are elsewhere: training the bot, choosing what it asks, and making sure the lead details reach you. Those take most of this tutorial.
Which Squarespace plans allow code injection?
Code injection is available on Squarespace's Core, Plus and Advanced plans and some legacy billing plans, according to Squarespace's help article on the feature. Squarespace's plans and prices vary by currency and change, so this tutorial leaves prices out; check the current plans page for your region. If you are on the entry plan, a chatbot will mean upgrading, and that cost belongs in your sums before the chatbot's own fee.
Four details from that article shape what you can do:
- Code placed in the Footer field is added before the closing body tag on every page. Code in the Header field is added to the head of every page.
- Checkout pages do not support custom code, so a widget will not appear once someone starts paying.
- The widget may not show in the editor. You see it only on the published site, ideally in a private or incognito window.
- Squarespace support cannot help add custom code or fix problems it causes. You are on your own with the vendor's help centre if something breaks.
Where to find the field: open the Code Injection panel from your site's settings (Squarespace describes it under Advanced), add valid HTML or script into the field for the area you want, then save. If you only want the bot on one page, such as a pricing or enquiry page, the page's own advanced settings have a header injection field. I would still start sitewide, because a bot that appears on only one page is easy to overlook when you test.
Tidio or Chatbase: which suits a Squarespace site?
Tidio and Chatbase both work through the same Squarespace footer field, so choose the one whose lead capture and pricing you can finish and test in an afternoon. Build one fully before you compare. These are the figures the vendors' own pages listed when checked on 20 November 2026.
| Point | Tidio | Chatbase |
|---|---|---|
| Entry cost | Free plan at $0 with 50 human conversations a month, plus 50 Lyro AI conversations listed as a one-time lifetime allowance. Lyro now comes inside the paid plans: Starter lists $39 a month billed monthly, or $390 a year billed annually, for 50 conversations that Lyro and your team share; Starter without AI is $29 a month billed monthly for 100 human conversations | No free plan listed. Basic lists $120 a month billed yearly (shown against a $150 list price) with 4,000 message credits and a seven-day trial |
| Squarespace install | Tidio has its own help article: copy the snippet, paste it into the Squarespace footer code injection field, save | Copy the widget script and paste it before the closing body tag. No Squarespace-specific guide found, so use the footer field |
| Lead capture | Data collection sits in Flows. Every plan, the free one included, reaches the first 100 visitors a month with Flows; more is an add-on from $29 a month billed monthly for 2,000 visitors ($24 a month billed annually) | A Collect Leads action: form mode with up to three fields, or conversational mode with up to 20 custom fields |
| Branding | Removing Tidio branding is a flat $20 a month add-on on either billing cycle, which Tidio's comparison table offers on Growth | Removing the Chatbase badge is a $99 a month add-on |
The point that decides it for most small sites is cost of failure. A free plan lets you install, find out the snippet does not suit your template, and walk away for nothing. Chatbase's seven-day trial gives you the same safety for a week. Neither suits a site that gets a handful of visitors, where a plain contact form does the job. If you are still deciding whether a bot pays for itself, the tutorial on adding an AI chatbot that captures leads covers the economics before you touch any code.
One more caution: Tidio's pricing page opens on annual billing, so the $33 a month it shows for Starter is $390 a year paid up front; month to month it is $39. Confirm the billing cycle at checkout. The pages above can change, so look at them again on the day you buy.
Why build the chatbot before pasting the snippet?
Build and test the chatbot in the vendor's dashboard before you paste anything into Squarespace, because once the snippet is on the site, every half-finished answer is public. That means finishing the training and the settings first.
Give it the pages that answer real questions
Point the tool at your own pages: services, prices, opening hours, cancellation terms, the FAQ. For an event venue that is capacity, hire rates, catering rules, parking, accessibility and the deposit terms. If you want a systematic way to decide what goes in, the tutorials on training Tidio's Lyro with questions, pages and files and which sources to add to Chatbase and which to leave out work through it, and building the FAQ your chatbot needs does the question list.
Write the rules the bot must follow
Short and specific beats clever. Here is an illustrative instruction block for the venue; adapt the facts, never copy the numbers.
You are the assistant for [venue name]. Answer only from the pages and
documents provided. If you do not know, say so and offer to take the
visitor's name and email so a person can reply.
Never quote a price unless it appears in the provided pages.
Never confirm a date is free: say a person will check and reply.
Keep answers under 80 words. Ask at most one question at a time.
If the visitor is upset or mentions an accident or complaint, offer to
pass the message to a person straight away.
Test this before you embed it, using the vendor's preview. Ask ten real questions from your inbox. Note which answers are right, which are vague and which are invented, and fix the training pages rather than arguing with the bot.
How do you paste a chatbot snippet into Squarespace?
Copy the embed snippet from the chatbot's dashboard, paste the snippet unedited into the Code Injection footer field under Settings, then Advanced, and save. The steps for Tidio come from its own help article; the Chatbase steps follow its widget guide and the same Squarespace footer field.
- Copy the snippet. In Tidio, go to Settings, Live Chat, Installation and copy the JavaScript snippet. In Chatbase, open the chat bubble channel, choose Deploy, pick the website widget, and copy the embed script. Chatbase recommends the widget over the inline frame because it supports all the advanced features.
- Open Code Injection. In the Squarespace editor, go to the site's Settings, then Advanced, then Code Injection.
- Paste into the Footer field. Paste the snippet exactly as given, including the script tags. Do not edit the key or address inside it.
- Save. Then open your live site in a private window, wait a few seconds and look for the chat bubble.
- Keep a copy. Paste the snippet and the date into a note so you can restore it if a later edit overwrites the field.
If the field already contains code, such as an analytics or consent script, add the chatbot snippet below it on a new line and do not delete what was there. If the editor preview shows an error saying the preview failed to load and that this is usually caused by injected code, Squarespace says the Disable Scripts in Preview option fixes the editor view and does not affect what visitors see.
How do you capture leads without putting visitors off?
Capture leads by setting up the lead action in the chatbot vendor's dashboard and asking only for what a quote needs, such as name, email and the event date. A chatbot that also gets a name and email when someone is ready to enquire is worth running, and both vendors handle it differently.
In Chatbase
Chatbase's documentation describes a Collect Leads action under Build, then Actions. Each agent can have one. You write a "when to use" instruction, then choose a mode:
- Form mode shows up to three fields (name, email, phone) on the chat bubble. Custom fields are not available, and either email or phone must be on and required.
- Conversational mode has the agent ask one question at a time and allows up to 20 custom fields (text, number, email, date or yes/no). Dropdowns are not supported, so list the allowed options in the field's description.
Leads then appear under Activity, then Leads, attached to their conversation, and can go to a webhook or an email notification. The documentation says there is no built-in qualification filter, so any screening belongs in your instructions. Here is a "when to use" text for the venue, as an illustration:
Use this when the visitor asks about hiring the venue for a specific
date, asks for a quote, or asks to be called back. Do not use it for
general questions about opening hours or parking. Ask for name, email
and the event date. Do not ask for anything else.
In Tidio
Tidio lists "Collect data" as a feature of Flows, which is separate from the Lyro AI agent. Every plan, the free one included, reaches the first 100 visitors a month with Flows, and the Flows add-on buys more; open the Flows editor on your account and see what is available before you plan around it. A typical flow asks one question ("What are you planning?"), then name and email, then a thank-you with a time to expect a reply. If your leads should flow on into a sheet or CRM, the tutorial on routing Tidio chat leads with Zapier shows the pattern.
What to ask, and what not to
Ask for as little as you can act on. An event venue needs a name, an email and a date. A translation agency needs an email, the language pair and a document type, not a phone number. A catering company needs a date, a headcount and an email. Anything beyond that is friction. Do not ask for payment details, health information or anything you would not want in a chat transcript. Add a line near the first question saying how the details will be used and link to your privacy page, because the form is collecting personal data.
If the leads end up in a spreadsheet and that is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.
How do you test a chatbot on a phone?
Test the chatbot by opening the live site in a private window on your own phone and checking the bubble position, cookie banner, chat window, first message, lead form and speed. Most Squarespace visitors arrive on a phone, and the chat bubble is where mobile layouts fail.
| Check | Pass looks like | If it fails |
|---|---|---|
| Bubble position | Sits in a corner and does not cover the main button on the page | Move it in the vendor's display settings, or change your button placement |
| Cookie banner | Bubble and banner do not overlap or block each other | Reorder, or delay the chat widget in its settings |
| Opening the chat | Window opens to a usable size and the keyboard does not hide the text box | Check the vendor's mobile display options; test a second phone |
| First message | States it is an AI and offers a person; reads well in two lines | Shorten the welcome text |
| Lead form | You can submit with a fake name and email, and the lead arrives | Check the lead destination and any required-field setting |
| Speed | Page loads with no obvious delay before the bubble appears | Remove other injected scripts you no longer use |
Submit a test lead on purpose and look for it where you expect it: the dashboard, the email notification and any sheet you set up. A bot that "works" but sends leads to an inbox nobody reads is the most expensive failure here, and you only find it by sending one through.
A walkthrough for a translation agency
Take a four-person translation agency on Squarespace's Core plan. Most of its enquiries arrive by email, and the same four questions repeat: turnaround time, which languages, how a quote is calculated, and whether certified translations are offered. The owner builds a Chatbase agent from her services page, her FAQ and a one-page quoting policy, and writes a rule that the bot never states a price unless the policy page gives it.
She adds a Collect Leads action in conversational mode, asking for email, language pair and document type, with the "when to use" text saying to collect these only when the visitor asks for a quote. She pastes the widget script into the Footer field, saves, and opens the site in a private window on her phone. The bubble appears but sits on top of the "Request a quote" button, so she moves the bubble to the other corner in the display settings.
Then she tests ten questions. Two answers are wrong because her turnaround times are only in a PDF the bot was not given, so she adds the PDF. One invented a discount, so she tightens the rule about prices. All figures here are illustrative; the lesson is that the first test finds problems the setup did not.
A sample chat and what to fix in it
Here is an illustrative exchange from a first test of the venue's bot, with the faults marked. Run something like it on your own bot before launch.
Visitor: Do you have the main hall free on 14 June?
Bot: Yes, the main hall is available on 14 June! The hire rate is $1,800.
Visitor: Can I bring my own caterer?
Bot: Absolutely, no problem at all.
Visitor: ok can someone ring me
Bot: Of course. What is your name and phone number?
Three faults. The bot confirmed a date it cannot see, which the rules forbid, so the instruction needs to be stronger and the training pages must not mention availability. It quoted a rate that may be from an old page, so find the source page and update or remove it. It said "absolutely" about outside caterers when the venue's policy says approved caterers only, so the answer was invented rather than read. The last turn is fine: it moved to lead capture quickly. A corrected first reply would be: "I can't see the diary, but I can pass your date to the team. What's your name and email?"
A second example, for a catering company on Squarespace: the owner adds the widget, then notices from the test conversations that visitors ask "do you do gluten-free?" in six different ways. She writes one clear dietary page, adds it to the bot's sources, and the six variants all resolve to the same correct answer. Fixing the source once beats patching answers one by one.
Why is the chatbot bubble not showing on Squarespace?
When the bubble does not show, the usual causes are the snippet in the wrong field, an unsaved change, a cached page, a page type that blocks code or a clash with another script. Work through these in order. Each is quick.
- Wrong place. The snippet is in the Header field when the vendor said Footer, or pasted into a page content block, which Squarespace may not run as a script.
- Not saved. The field looked saved but the page was left before the save finished. Reopen Code Injection and check the text is there.
- Cached page. Load the site in a private window, or on mobile data, to rule out a cached version.
- The page type. Squarespace says code injection does not appear on index landing pages, and checkout pages do not support custom code at all. Test on a standard page.
- A clash. Remove other chat or popup scripts, then add them back one at a time.
- The widget is paused. Check the vendor's dashboard for a disabled channel, an unpublished agent or an exhausted allowance. On Tidio's free plan the 50 AI conversations are a lifetime total, so they can run out.
If none of those work, remove the snippet, confirm the page is fine without it, and contact the vendor with the snippet and the page address. The Squarespace help centre will not troubleshoot custom code, so keeping your copy of the snippet saves time.
What should you check after the chatbot goes live?
After launch, read the first twenty conversations by hand within a week and look for three things: unanswered questions, wrong answers and leads that were not captured. Add unanswered questions to the training pages and fix wrong answers at the source page, not just the reply. For a venue, a missed lead is usually a visitor who asked about dates and left without giving an email, which tells you the "when to use" text is too narrow.
Keep a simple log: date, change, reason. Update the bot whenever your prices, hours or policies change, because a chatbot reading last season's rates is a way to promise things you do not offer. If you would like the setup mapped against your own enquiries by someone who has done it, that is what my AI implementation consultation covers. A careful afternoon with the checklist above gets most owners there on their own.
Squarespace chatbot questions owners ask
Which Squarespace plan lets me add a chatbot?
Core, Plus or Advanced, and some legacy plans. A chatbot widget needs code injection, which Squarespace's help article says is available on those plans. Check Settings on your own site, because plan names and features change and a trial site may restrict some injection areas.
Why can't I see the chatbot in the Squarespace editor?
Injected scripts often do not show in the editor view. Open the published page in a private browser window to see it as a visitor does. If the editor shows a preview error, Squarespace points to injected code as the usual cause and offers a Disable Scripts in Preview option.
Will the chatbot appear on checkout pages?
No. Squarespace says checkout pages do not support custom code, so a footer snippet will not run there. Decide whether that matters for you: visitors can still use the widget on product and information pages, but not once they are in the payment step.
Which is better for a small Squarespace site, Tidio or Chatbase?
Pick the one whose lead-capture setup you can finish and test in an afternoon. Tidio has a free plan with a lifetime allowance of Lyro AI conversations, so you can test at no cost. Chatbase's pricing page lists paid plans with a seven-day trial.
Can Squarespace support fix a broken chatbot snippet?
Not usually. Squarespace's code injection article says its support team cannot help add custom code or troubleshoot problems it causes. Use the chatbot vendor's help centre first, remove the snippet to confirm it is the cause, and keep a copy of what you pasted.
Can I put the chatbot on one Squarespace page only?
Yes. If you only want the bot on one page, such as a pricing or enquiry page, the page's own advanced settings have a header injection field. Even so, start site-wide, because a bot that appears on only one page is easy to overlook when you test. Code injection does not appear on index landing pages.
Further reads
- Best AI Chatbot for a Hotel Website: Score It on Real Guest Questions — Score a chatbot on real visitor questions.
- Best AI Chatbots for Small Business Websites — Compare other chatbot options for a small site.
- Squarespace AI Pricing: Which Plan Gives You Enough AI Credits? — See what Squarespace's own AI credits cover per plan.
- How Can a Local Business Use AI on Its Website? — Chat, page copy and booking on a local firm's site: list prices, four sample monthly budgets, a chat fact sheet, copy checks and a four-week test.
- How Much Does Squarespace's AI Website Builder Cost a Trade Firm? — What a trade business really pays for a Squarespace site built with Blueprint AI: plan prices, domain, booking add-ons and a worked three-year bill.
- Squarespace AI Website Builder Review: Does It Suit an Electrician? — A verdict for electricians, verified plan and credit limits, and the specific fixes an AI-built draft needs on claims, quote form and certificate wording.
Show 3 more related tutorials
- How a Web Agency Chooses a CMS With AI for Client Sites — Score WordPress, Webflow, Squarespace and Wix per client site on editor AI, hosting, cost and handover, then apply a simple decision rule.
- Squarespace AI SEO: Write Page Titles, Descriptions and Alt Text — Draft SEO titles, descriptions and alt text for a whole Squarespace site in one sitting with ChatGPT or Claude, then set and check them page by page.
- Squarespace Designer Cost vs Blueprint AI: Which Is Cheaper? — A cost model for a Squarespace designer versus Blueprint AI: plan prices, your own hours, a brief template and a cheaper hybrid.
Browse all AI-for-business tutorials
Sources: Squarespace help centre article on code injection; Tidio's Squarespace installation article, pricing page and plans; Chatbase pricing page, widget deployment guide and Collect Leads documentation (checked 17 Nov 2026).
