Paste the ConsentLayer tag into the client’s Squarespace code injection (Core plan or higher). It holds known trackers until the visitor chooses, including the ones pasted into code injection, and records every decision. When the site loads no trackers through code, Squarespace’s own banner can do the job. Switch it on under Settings > Website > Cookies and turn on both Decline all and Manage cookies. Then set Non-essential Cookies to Restrict under Advanced Privacy settings.
Which Squarespace cookie banner route fits the client site
A Squarespace site has two workable routes to a cookie banner, and the right one depends on how the site’s trackers were added.
The first route is the banner Squarespace builds in. You set it up in the Cookies panel: the consent buttons, the text with a link to the privacy policy, a restriction on non-essential cookies, and a style that matches the site.
The second route is a separate consent tool loaded through code injection. It suits client sites where someone pasted a Google Analytics snippet, a pixel, or a chat widget into the header field, or where pages carry embedded video and maps. Squarespace’s banner was not built to control code it did not add. Those scripts need a tool that sits in the head and holds trackers until consent.
In both routes the work finishes only after a check on the live domain in a logged-out browser. A banner that shows in the editor but not to visitors, or that shows while trackers have already fired, gives the client no real consent record.
Before you set up the cookie banner
Collect these before you open the client’s settings:
- Admin access to the client’s Squarespace site, for the Cookies panel and code injection.
- A privacy or cookie policy page that already exists, for the banner to link to on day one.
- Private browser windows for every preview.
- A list of everything the site loads and how each item was added: a built-in integration, code injection, or an embedded block.
That last list decides the route. A site where Google Analytics came in through Squarespace’s integration panel and nothing else loads can run on the built-in banner. If someone pasted a Meta pixel into the header, the site needs a tool that controls that code. The ConsentLayer route depends on code injection, and Squarespace only opens code injection on the Core plan or higher. Confirm the client’s plan before you promise that route.
Turn on the Squarespace cookie banner
Step 1: Open the Cookies panel and switch on the banner
Go to Settings > Website > Cookies to open the Cookies panel (Squarespace titles it Cookies & Data Privacy). Then switch on the Cookie banner toggle.
Step 2: Choose the consent buttons
Squarespace lets you show Decline all, Manage cookies, or both. You can rewrite each button label and the disclaimer text. With both buttons off, non-essential cookies stay restricted until the visitor acknowledges the banner. Manage cookies alone brings the banner back after its 30-day sub-footer.
| Button settings | What the visitor can do |
|---|---|
| Both buttons off | Accept all only; the banner hides for 30 days after acceptance |
| Manage cookies on, Decline all off | Accept all or manage preferences; a sub-footer shows for 30 days |
| Both buttons on | Accept all, decline all, or manage preferences |
On every client site, turn on both buttons: a visitor who wants to refuse should not have to dig through preferences to do it.
Step 3: Write the banner text and link the privacy policy
Squarespace has sample banner text, but it tells you to check that text against your own requirements. Treat it as a draft and rewrite it for the client. Add a link to the client’s Privacy Policy page inside the banner text field.
Step 4: Choose where saved preferences appear
Pick Subfooter or Pill for the saved-preferences link, where visitors can change their choice later. I’d avoid Hidden, which removes that link and leaves a visitor who accepted by mistake with no way back in.
Step 5: Restrict non-essential cookies
Under Advanced Privacy settings, find Non-essential Cookies and select Restrict. To lift it later, use the same option, now labeled Remove Restriction.
Step 6: Style the banner to match the site
Open Customize Banner Style, or the Cookie Banner panel in Site Styles, to set color, position, and text size. Button font, shape, outline, and padding sit in the Buttons panel, and the Colors panel sets the button and toggle colors. Clients spot a banner in the default colors on a branded site straight away, so match it to the site’s own buttons.
Step 7: Save the settings
Save your changes, then preview the banner logged out or in a private window, because it does not show while you are logged in.
Add ConsentLayer through Squarespace code injection
Step 1: Create the site in ConsentLayer
You can set it up by prompt through the AI agent you already use, or from the dashboard at app.consentlayer.com. To use your agent, first connect your agent to ConsentLayer and sign in through your browser. Then send one prompt:
“Set up cookie consent on clientsite.com”
Your agent runs setup_site, one tool call that creates the site and scans it. It also configures consent categories and returns the tag with a real project key.
Without an agent, add the client’s domain in the dashboard at app.consentlayer.com and copy the tag once the scan finishes.
Step 2: Paste the tag in code injection
Put it first, above any other script in that field, and leave it exactly as given. It must load synchronously, with no defer and no async, before other scripts, and from there it sits in the site’s head on every page.
Step 3: Switch off the built-in banner and publish
Switch off the built-in banner you turned on in Step 1 of the Squarespace section, so visitors see only one banner. Then save to publish the ConsentLayer banner on the live domain.
Check that the cookie banner works
Check the built-in banner in a private window
Open the live domain in a private window and confirm the banner appears. Make sure Decline all sits next to the accept button, then open Manage cookies to see the categories.
Check the ConsentLayer install
Ask your agent: “Check the ConsentLayer install on clientsite.com”. It runs check_installation, a tool that fetches the live homepage and confirms the tag is in <head> without defer or async. The compliance score rates the site from 0 to 100 across 10 checks and names the open items to work through before you hand the site back.
Common problems and fixes
The banner does not show when you preview
Squarespace hides the banner from you while you’re logged in, so your preview is not what a visitor sees. Run this check:
- Log out of Squarespace, or open a private window.
- Load the live domain, not the editor preview.
- Confirm the banner appears on the first page load.
Google Analytics in code injection runs before consent
Picture a client site where someone pasted the GA4 snippet into the header field two years ago. Squarespace says custom code that drops non-essential cookies may need to interact with the banner. For Google Analytics added through code, it points you to its code injection guide. Until then, that snippet can load before anyone clicks.
With ConsentLayer in place, static scripts already in the HTML are execution-blocked, and the GA4 snippet waits for the visitor’s choice. Check every other script in that field too, since each one is a candidate for the pixels that fire before consent.
Embedded content still sets cookies
Content inside some blocks keeps setting cookies with the banner on, and the visitor’s decline does not reach it. Squarespace says “the cookie banner won’t block that content” for tracking added through some blocks, with an audio block as its example, and it does not block or restrict OpenTable or Tock content.
Restricting non-essential cookies also “doesn’t disable all cookies placed by third-party services” connected to the site. ConsentLayer replaces embeds from YouTube, Vimeo, DailyMotion, Google Maps, reCAPTCHA, X, and Instagram with a click-to-load placeholder until consent, through its script and embed blocking.
Visitors cannot decline cookies
Only one button setting gives the visitor an explicit decline option. Check which buttons are on, then fix it in three moves:
- Open the Cookies panel from Step 1.
- Switch on Decline all next to Manage cookies.
- Save, then confirm the new button in a private window.
Squarespace cookie banner FAQ
Does the Squarespace cookie banner work with Google Consent Mode?
Squarespace sends consent signals to providers that support a consent mode, and Google Analytics and Meta Pixel use it when you add them through the API keys panel. ConsentLayer includes Google Consent Mode v2 on every plan, including Free.
Does the cookie banner change what Squarespace Analytics shows?
It can, through an activity log option in the banner setup that sets whether its data is included in Squarespace Analytics. Decide with the client whether they want that data counted.
Can the built-in banner make a Squarespace site GDPR compliant?
Not every website is subject to GDPR, Squarespace says. It tells site owners to check with a legal professional and does not advise on privacy or cookie policy content. A ConsentLayer consent log, Free plan included, records each decision and gives the client proof of every choice.
How do you honor Global Privacy Control on a Squarespace site?
Use ConsentLayer, whose banner honors Global Privacy Control by default on all plans. A browser that sends the opt-out signal gets treated as opted out without any extra setting. Here’s how Global Privacy Control shows up in a consent log when a client asks for proof.
Going further on client Squarespace sites
Copy the setup to the next client site
Once one Squarespace client site is set up, export its full ConsentLayer configuration as JSON and import it into the next site. The export carries design, behavior, categories, services, cookies, translations, and geo groups, so you start the next site with the banner and blocking you already tuned.
Create the new site first, then import the file. Read more about cookie consent for client sites if your roster keeps growing.
Set up ConsentLayer on your client’s Squarespace site with the quick start guide.
