Squarespace

Inclusify installs on Squarespace as one paste into the Footer field of Code Injection, which Squarespace injects before the closing </body> tag on every page of the site. Code Injection is a billing-plan feature: Squarespace lists it on the Core, Plus and Advanced plans and on some legacy plans, and it is the only supported way to add a site-wide third-party script. One field and one Save, on 7.0 and 7.1 alike. Check the result in a private window, because Squarespace can disable injected scripts in your own preview while you are logged in.

Register the domain first

Add your domain in the Inclusify panel before you paste the script tag. Bundles are built per registered domain, and an unregistered one fails silently: the script URL still returns HTTP 200, but what it serves is a single console.log saying the domain is not registered. There is no error to find and no widget appears.

Installation Steps

1

Open Code Injection

In your Squarespace dashboard, go to Website Pages, then Website Tools Code Injection. Squarespace’s own deep link to the panel is /pages/website-tools/code-injection on your site’s dashboard, which is the quickest way to check you are in the right place on either site version.

2

Add to Footer

Paste the widget code in the Footer field. Squarespace injects it before the closing </body> tag on every page of the site.

HTML
<script src="https://app.inclusifyapp.com/w/YOUR-DOMAIN.com.js" async></script>

Replace YOUR-DOMAIN.com with your actual domain.

3

Save

Click Save, then load the live site in a private window. Squarespace caches rendered pages at the edge, so hard-reload or add a query string such as ?cachebust=1 if you still see the old page.

Notes

  • • The Footer field applies to every page of the site, including member-only pages, which still render the site template
  • • Works on 7.0 and 7.1 and every template family, with one 7.0 exception: Squarespace notes that code injection does not appear on Index landing pages
  • • Squarespace states that checkout pages do not support code, so the widget does not appear there and no field reaches them
  • • The lock page, order confirmation and order status fields are separate from the Footer field and scoped to those pages only. The widget belongs in Footer
  • • Use Code Injection for the script and the Custom CSS Editor for styles. Squarespace notes that Ajax loading can stop CSS added through code injection from loading correctly

What needs attention on Squarespace

Code Injection is a billing-plan feature

Squarespace lists Code Injection as available on the Core, Plus and Advanced plans and some legacy billing plans. There is no add-on and no plugin route: on a plan without it there is no supported way to add a site-wide third-party script.

The Footer field is exactly the right field

Squarespace documents the Footer code injection field as injected before the closing </body> tag on every page in the site, which is where an async widget tag belongs. The Header field injects into <head> on every page and buys nothing here. The lock page, order confirmation and order status fields are separate and scoped to those pages only.

Squarespace can hide your code from you while you edit

Custom code can interfere with secure editing, and Squarespace responds by offering to disable scripts in preview. When that happens you stop seeing your own widget while logged in, without anything changing for visitors. Squarespace's instruction is to open a private window to view the code, which is why the verification steps here start there.

Trial sites are fine, with one exception

The only trial-period restriction Squarespace documents for Code Injection is the lock screen: it is not possible to inject code to the lock screen during a site's trial. Header and Footer injection is not called out, so a trial site is not in itself a reason the footer tag would fail.

Version 7.0 Index landing pages skip it

On version 7.0, Squarespace notes that code injection will not appear on Index landing pages. If the widget is present everywhere except one landing page on a 7.0 site, that is the reason, and the page's own Advanced settings are where a per-page injection goes instead.

Verify the installation

  1. Open the live site in a private window. Squarespace can disable injected scripts while you are logged in and editing, and its own advice for viewing your custom code is to open a private or incognito window and load the page there.
  2. Use View Source and search for "inclusifyapp" to confirm the footer injection rendered.
  3. Check a blog post and a store page as well as the home page.
  4. If a banner at the bottom of your site says it detected an error loading the site preview, that is Squarespace telling you injected code is interfering with secure editing. It affects the editor, not visitors, but resolve it before judging the install.
  5. Do not test on a checkout page. Squarespace states that checkout pages do not support code, so the widget is absent there by design.

Widget bundles are served from a CDN and cached for a few hours. If you changed widget settings in the panel and the site still shows the old configuration, wait for the cache to expire or load the script URL directly with a cache-busting query string (`?v=2`) to confirm the new version is being served.

Troubleshooting Squarespace installs

There is no Code Injection option in the dashboard.
The site is on a billing plan that does not include it. Squarespace makes Code Injection available on the Core, Plus and Advanced plans and on some legacy plans; anything else has no way to add a site-wide third-party script.
The widget is missing on one landing page of a 7.0 site.
Code injection does not appear on Index landing pages in version 7.0. Add the tag to that page's own Advanced settings through Page Header Code Injection instead.
The widget is gone while you are logged in but visitors still see it.
Scripts have been disabled in your site preview, which Squarespace does when injected code interferes with secure editing. Check the live site in a private window; if you want to find the offending snippet, add /safe after /config in the editing URL to bring up the message.
The widget does not appear during checkout.
That is expected: Squarespace states that checkout pages do not support code. There is no field that reaches them.
Nothing changed after saving.
Squarespace caches rendered pages at the edge. Hard-reload the live URL, or append a query string such as ?cachebust=1 to bypass it.

Squarespace questions

Which Squarespace plan do I need?
Core, Plus or Advanced, or one of the legacy plans that carried Code Injection. Those are the plans Squarespace lists for it, and Code Injection is the only supported way to add a third-party script site-wide.
Does it work on both 7.0 and 7.1?
Yes, with one 7.0 caveat: Squarespace notes that code injection does not appear on Index landing pages in that version. Footer injection otherwise behaves the same on both versions and every template family.
Does the widget load in Squarespace member areas?
Yes. Member-only pages still render the site template and its footer injection, so the script loads for authenticated visitors.
Should I use header or footer injection?
Footer. Squarespace injects that field before the closing </body> tag on every page, which is where an async script belongs, and it keeps the request off the critical path.
Can I add the widget on a trial site?
Yes, as long as the trial is of a plan that includes Code Injection. The only trial restriction Squarespace documents is that code cannot be injected into the lock screen during the trial period.

Squarespace documentation

Every Squarespace-specific requirement, menu path and limit on this page comes from these pages. Menus move, so check them against your own admin if something does not match.

Related