To add chat to Squarespace, paste the widget script into the Footer field of the Code Injection panel. Squarespace then inserts it on every page of the site, and the Meetlead widget loads as a separate script in the visitor's browser. Before you start, check one thing: not every Squarespace plan includes Code Injection. This guide shows how to verify that, where to paste the code and how to test the first conversation.
The focus here is technical: the plan, the code, domains, page exclusions and the phone view. If you are still deciding whether you need chat at all and who will answer it, start with the guide on how to choose and implement website chat. Shopify stores and WordPress sites have their own separate instructions.
Where to paste the chat code in Squarespace
Paste the chat code into the Footer field of the Code Injection panel. Squarespace places the contents of that field before the closing body tag on every page, so one entry covers the whole site. The Header field also works, because the Meetlead script uses the async attribute and does not hold up page rendering. The footer is still the natural spot for a tool that does not need to start before the rest of the page. Squarespace Help does not give a fixed menu path and links straight to the panel instead, so look for the name Code Injection rather than following a screenshot from someone else's tutorial.
Squarespace Help describes the Header and Footer fields, page-level code and the fact that checkout pages do not support code injection. It also states that the support team cannot help you add or troubleshoot custom code. The page does not describe any specific chat tool. Squarespace Help: Using code injection.
Which Squarespace plans allow code injection
Check this first, because without Code Injection you cannot add a script that runs across the whole site. According to Squarespace Help, the feature is available on the Core, Plus and Advanced plans and on some legacy plans. The Squarespace pricing page does not list it for the Basic plan. Plan names and line-ups vary by region and purchase date, so compare the table with what you see in your site's billing settings.
Scroll the table sideways to see all columns.
| Plan | Code Injection | What to do |
|---|---|---|
| Basic | Not on the pricing page | Upgrade before rollout or offer another contact channel |
| Core, Plus, Advanced | Available according to Help | Paste the code into the Footer field |
| Legacy plan | Only on some plans | Check whether the Code Injection panel is active |
The Squarespace pricing page shows Code Injection on the Core and Advanced plans, not on Basic, and names live chat services as an example use. It says nothing about legacy plans or the trial period, and it does not list the Plus plan that Help mentions. Squarespace: Pricing.
Before you paste: domains, access and the old chat
- You have admin access to the Squarespace site, or someone who does is involved.
- In Meetlead you have a site with its own clientId and the embed code copied from its settings.
- Every exact host is on the allowed domains list: the domain with and without www.
- If you test before connecting your domain, the built-in Squarespace address is on the list too.
- You know whether another chat already runs on the site, and you have a plan to switch it off.
The domain list is what most often blocks the launch. Meetlead does not support wildcards, so you add each host separately, without paths, and each entry counts toward the domain limit of your plan. Add a test address for the rollout and remove it once the site runs on its real domain. An old chat in Squarespace may come from the Code Injection field, a code block on one page or an extension; we cover the two-widget problem and how to track it down in the guide to chat on Shopify.
Step-by-step installation
- Copy the code from Meetlead.In the site settings, copy the script with the correct clientId. The ID is public, but it must belong to this site, or conversations will land in the wrong place.
- Open Code Injection.Find Code Injection in the Squarespace admin. If the menu looks different from the instructions, use the admin search.
- Paste the script into Footer.Put it on its own line. Above it, add an HTML comment with the tool name and date, so the next person knows where it came from.
- Save the change.Click Save. Code in this field applies to the whole site, so you do not need to add it again on individual pages.
- Open the site in a private window.Check the home page, an offer page and the contact page. The launcher should appear without being logged in to Squarespace.
- Send a test message.Write from your phone and reply from the Meetlead panel. Only a reply that reaches the visitor confirms the rollout.
The private window is not a formality. Squarespace Help explains that custom code can be disabled in the editor preview and recommends a private window to view the live site with code running. If the widget does not show in the editor, do not assume something is broken. You later change the look, languages and greetings in Widget Studio; the footer code only loads the widget.
Pages where the chat should stay hidden
Squarespace lets you inject code on a single page through its advanced settings. That makes it tempting to control chat visibility page by page, but with a dozen pages you soon lose track of where the code lives. It is simpler to keep one script in the footer and set visibility in Meetlead. The rules show the widget on all pages, only on listed path prefixes or on all pages except listed ones, and you can also choose devices.
Take a fictional yoga studio: chat should run on the class and pricing pages, but not in the members area or on the terms pages. You enter those paths as exclusions and save, without reopening Code Injection. When the team is away for a few days, the widget's master switch hides it across the whole site. Squarespace checkout does not accept custom code anyway, so answer payment questions earlier, on the offer page.
Phones: the launcher and Squarespace buttons
On a phone, the chat launcher shares the bottom of the screen with elements you set up in Squarespace itself. Most often that means the cookie banner, a promotional pop-up or a sticky button in the template. Open every important page on a real device, in portrait and landscape. If the icon covers a booking or consent button, change the screen side or the launcher offset in Meetlead. The guide on sticky elements covering buttons explains how to find such collisions.
- The launcher does not cover the booking, purchase or form button.
- The cookie banner and the widget do not overlap on the first visit.
- The chat window opens full screen and is easy to close.
- The keyboard does not hide the message field or the send button.
- A message from the phone reaches the panel, and the reply gets back to the visitor.
Chat: Meetlead, site [name], clientId from the panel. Code in Code Injection, Footer field, added on [date] by [person]. Squarespace plan: [name]. Hosts on the list: [domain], [www.domain]. Excluded paths: [list]. Old chat removed from: [location].
Frequently asked questions
Can I add chat on a plan without Code Injection? Not as a script that runs across the whole site. You can upgrade, or offer another contact channel, such as a form, until you decide. A code block is no workaround: according to Squarespace Help, JavaScript in code blocks also requires Core or higher, so on Basic the chat script will not run. Before you buy, check the pricing page for your region to see which plan includes the feature.
How is this different from WordPress? In WordPress you can connect the site with the official Meetlead plugin, without pasting a script, as the guide to chat on a WordPress website describes. In Squarespace the route is Code Injection. The remaining steps are shared: the domain list, a single widget, visibility rules, a phone test and a conversation someone actually answers.
