The 60-second Squarespace chatbot path
Squarespace has a single canonical install path for third-party scripts: Settings, Advanced, Code Injection. Once you're on a Business or Commerce plan and inside the Code Injection panel, the install takes about 60 seconds.
The chatbot snippet is one line:
<script async src="https://chatraj.com/widget.js" data-bot-id="YOUR_BOT_ID"></script>
Inside your Squarespace dashboard, navigate to Settings (gear icon), Advanced, Code Injection. Paste the script tag into the Footer section. Hit Save. The chatbot bubble now appears in the bottom-right corner of every page of your Squarespace site within seconds of the next page load.
That's the whole integration. No Squarespace App to install, no permission scope to grant, no template setting to update, no theme-style overrides to retrain your team on. The widget loads asynchronously after your page renders, never blocks Largest Contentful Paint, and shows up on every page that includes your site's published footer (which is every page, by default).
Why Footer, not Header
The Code Injection panel exposes two main slots, Header and Footer, plus specialized slots for Lock Page, Order Confirmation, and Order Status (the last two only on Commerce plans). For the chatbot loader, Footer is the correct placement.
The Footer slot injects code just before the closing body tag, after all your page content has rendered. The Header slot injects code into the document head, before the body. For the chatbot loader specifically:
- Footer (recommended): the async loader runs after the page is interactive, so the chatbot bubble appears 1-2 seconds after the page loads with zero impact on First Contentful Paint or Largest Contentful Paint.
- Header (not recommended): the async attribute still prevents render-blocking, but the loader is competing for browser resources during the initial paint window. Slightly less optimal, no real upside.
Use Footer. The convention for chat widgets is body-end placement, and Squarespace's Code Injection panel makes that the path of least resistance.
Three places to put code on Squarespace (and which to pick)
Squarespace gives you three places to inject custom code, depending on whether you want site-wide, page-level, or block-level scoping:
Option A: Site-wide Code Injection (recommended for chatbots). Settings, Advanced, Code Injection, Footer. The script runs on every page of your site. This is the standard pattern for embedded chat widgets and the one we recommend.
Option B: Per-page Header/Footer Code Injection. Open the page in the Squarespace Editor, click the gear icon next to the page in the Pages panel, scroll to Advanced. Squarespace gives you Page Header Code Injection. Paste the script tag here if you only want the bot on one specific page (your Pricing page, your Contact page, etc.). Hit Save.
Option C: Code Block element (rarely needed for chatbots). Squarespace's Code Block element lets you embed HTML into the body of a specific page section. This is useful for inline embeds (Twitter widgets, custom CTAs, calendar booking widgets) but overkill for a floating chatbot bubble. Use Options A or B instead.
Will it work on my Squarespace template?
Yes. ChatRaj's widget is an iframe rendered above all your site content via z-index 2147483647 (the maximum 32-bit signed integer, so no other element on the page can sit on top of it accidentally). It does not import any CSS into your Squarespace template, does not add classes to your body element, and does not load fonts that conflict with your Squarespace design system.
We've verified the script on every official Squarespace 7.1 family (Bedford, Brine, Five, Hayden, Marquee, Skye, Tudor, and the rest) and on the latest Fluid Engine pages. The widget renders correctly above Squarespace's standard global headers, sticky navigation bars, full-bleed image sections, parallax scroll effects, and the Lightbox component.
The only conflicts we've seen are a handful of custom-CSS-heavy sites that override z-index on body elements (unusual; most Squarespace designers don't touch root-level z-index). The fix is a one-line CSS override added via Settings, Design, Custom CSS: #chatraj-iframe { z-index: 2147483647 !important; }. If you hit this, ping support.
Squarespace 7.0 vs 7.1: which do you have?
Squarespace has two active template versions: 7.0 (older) and 7.1 (current, all new sites). Most existing Squarespace sites are still on 7.0; new sites created in 2023 or later are on 7.1. The chatbot install path is the same on both.
If you're not sure which version you're on: Settings, Advanced (or check the URL pattern of your Site Editor). Either way, Settings, Advanced, Code Injection works identically. The install does NOT require migrating to 7.1.
Lead capture, ungated, plus Squarespace Commerce angles
For Squarespace Commerce sites, ChatRaj's lead capture maps to two clear flows:
Product Q&A and email capture. When a visitor asks a product question and doesn't add to cart, the bot can offer a discount code in exchange for their email. The captured email flows to a CSV export or a webhook of your choice. Most Squarespace Commerce operators send it to Mailchimp, Klaviyo, or Squarespace Email Campaigns for the abandoned-cart automation.
Service-business lead capture (Squarespace Member Areas, Acuity Scheduling). For Squarespace sites running on Acuity Scheduling (owned by Squarespace) or Squarespace Member Areas, the bot captures the visitor's email and a brief note about what they want to book or sign up for, then hands off to your scheduling tool via a follow-up email. Function-calling (auto-book the Acuity slot) is on our 2026 roadmap.
Captured leads are exportable on demand from the Leads tab in the ChatRaj dashboard and are not locked into the ChatRaj platform. Push to your CRM, push to a CSV, or build a Zapier flow (planned native Squarespace integration).
Matching the chatbot to your Squarespace design system
Squarespace's appeal is its design polish: curated templates, refined typography, consistent spacing, considered color palettes. A chatbot that looks like a generic third-party widget will clash with that visual language. ChatRaj's customize panel was built specifically to avoid this:
- Theme color. Match your Squarespace site color (Settings, Design, Site Styles, look up your primary brand color and paste the hex into ChatRaj's Theme Color picker).
- Avatar. Upload the same logo or wordmark you use in your Squarespace header navigation. The widget renders it as a 32 px circle in the chat header.
- Welcome message. Write something that matches your site's voice. Squarespace sites tend to have considered copy; the chatbot welcome message should match that tone rather than read like a template.
- Suggested questions. Add 3-4 that match what visitors actually ask on your Squarespace site (refer to your Acuity inbox or contact form for inspiration).
Once these four are dialed in, the chatbot reads as part of your Squarespace brand rather than a third-party bolt-on. This matters more on Squarespace than on most platforms because Squarespace buyers select the platform partly for its design language.
Squarespace Email Campaigns + the lead-capture flow
For sites running Squarespace Email Campaigns (Squarespace's native email tool, available across all plans), captured ChatRaj leads can flow back into your email lists with two steps:
- Export captured leads from the ChatRaj Leads tab as a CSV.
- Import the CSV into your Squarespace Email Campaigns audience via the Squarespace dashboard, Email Campaigns, Audience, Add Subscribers, Upload CSV.
This is the manual path. The faster, webhook-based path uses Zapier (or a similar automation tool) to send each captured lead to Squarespace Email Campaigns the moment it's captured. Configure ChatRaj's webhook URL to point at a Zapier hook, and Zapier routes new leads into your Squarespace audience automatically. A native Squarespace Email Campaigns integration is on our roadmap.
For Mailchimp, Klaviyo, ConvertKit, ActiveCampaign, or any other ESP you might use alongside Squarespace, the same webhook pattern applies.
Multi-language sites
Squarespace's official multi-language support is limited (the platform recommends third-party tools like Weglot or Bablic for true multi-language sites). ChatRaj's chatbot, however, auto-detects the visitor's language from their first message and replies in the same language regardless of how your site is structured.
If you use Weglot, Bablic, or another translation overlay tool on your Squarespace site, the chatbot reads the language variant visible on the page the visitor is browsing. A visitor on the Spanish version of your Squarespace site (rendered through Weglot's overlay) gets answers in Spanish based on the Spanish-rendered content.
If your audience is mono-lingual (most Squarespace sites are), the bot picks up the visitor's language naturally without any configuration. You can also set a per-bot Force response language in Settings if you want to lock the bot to a single language regardless of visitor input.
GDPR + Squarespace's cookie banner
ChatRaj never trains models on your visitors' chat logs and never shares visitor data across customers. Each bot is fully isolated by chatbot_id; the only data we store about visitors is a random visitor_id cookie (used to give conversation continuity across page loads) and the messages they send.
For GDPR compliance on EU traffic, ChatRaj signs a Data Processing Agreement (DPA) with every paid customer. Visitor consent for the chat widget should fold into your Squarespace site's existing cookie banner. Squarespace has a built-in Cookies & Visitor Data banner (Settings, Cookies & Visitor Data) that you can configure to delay third-party scripts until consent is granted.
For stricter consent flows, ChatRaj's widget loader honors a window-level flag (window.chatrajConsent = true) so you can keep the bot hidden until your consent layer fires. Most Squarespace operators don't need this; the chatbot widget is functional (not advertising) and falls under most jurisdictions' standard functional-cookie consent.
When you should NOT use ChatRaj on Squarespace
A few honest signals that ChatRaj might not be the right fit for your Squarespace site:
- You're on the Squarespace Personal plan. Code Injection is blocked on Personal, so no third-party chatbot can be installed. You'll need to upgrade to Business or Commerce first. Business is the entry tier for Code Injection.
- You need real-time order status answers ("where is my order #1234?") from your Squarespace Commerce store. ChatRaj indexes your public store content; it does not connect to Squarespace Commerce's order API and cannot see live order data. For order-status queries, use Squarespace's built-in customer account pages or Acuity Scheduling's confirmation emails.
- Your site is fewer than 50 visits per month. At that volume the chatbot's value is hard to justify against your setup time. Focus on driving traffic first via SEO, paid social, or partnerships.
For everyone else: the 60-second install path is real, and the free ChatRaj tier is enough to confirm whether the bot's answers from your Squarespace content are good enough before you spend a dollar.