Figment.so
BlogHow to usePricing

Cookie Banners on Website Builders: What Each One Offers

Three of the four major builders covered here ship a native cookie consent banner you turn on in settings; Webflow does not, and documents tracking-consent options and specific app integrations instead. This post describes what Squarespace, Wix, Webflow, and Shopify each say their own tool does — not what the law requires of your specific site. Cookie and consent obligations vary by where your visitors are and what you track, so check your own legal requirements (or a lawyer) separately from anything below.

Squarespace's banner lives in the Cookies & Data Privacy panel, and its behavior changes based on two toggles: whether visitors get a Manage cookies option, and whether they get a Decline all button. With both off, visitors only see an Accept-all button and the banner won't reappear for 30 days once accepted. With Manage cookies on, visitors can accept all or set granular preferences; with Decline all also on, they can reject everything outright. Squarespace's help center is careful about scope: restricting non-essential cookies covers "Squarespace, and some third party integrations," and it adds that "if your site has custom code injection that drops non-essential cookies, you may want to ensure your cookie banner can interact with the code" (Squarespace Help Center, "Providing cookie consent options with a banner", checked September 2026).

Squarespace also supplies default disclosure text, and is upfront that it isn't a legal guarantee: "Cookie notice requirements vary depending on your location and cookie use. While we provide sample text you can use, you shouldn't assume that it satisfies your particular legal requirements" (same source). You can style the banner's color, position, and text size, and choose whether a visitor can reopen their preferences later via a Subfooter or Pill layout, or hide that option entirely.

Wix's banner is built on a partnership, not a fully in-house tool: "Wix has partnered with Usercentrics to offer you a consent banner solution that includes anytime site scans, translation in up to 60 languages, and is supported for Google Consent Mode v2" (Wix Help Center, "Displaying a Usercentrics for Wix Cookie Banner", checked September 2026). The base version is free: "The basic version of the Usercentrics cookie banner is free to use and fully GDPR-compliant." Premium features — "privacy trigger placement, translations, customizable text and legal document linking" — need a paid Usercentrics subscription, offered with "a 14-day trial period on sign up" (same source).

Turning it on has a real functional effect on other tools, which Wix documents by category: "Once you add a cookie banner to your site, it automatically disables the usage of non-essential cookies and scripts until your visitor provides consent," naming specific examples — "Functional cookies: Hubspot and apps created by POWr. Marketing cookies: Marketing integrations such as Facebook Ads, Google Ads and Facebook Pixel. Analytics cookies: Analytical tools like Google Analytics, Hotjar and Wix Analytics" (same source) — meaning those integrations simply won't fire until a visitor consents. Wix also names what the banner can't guarantee to control: "Third-party apps from the app market" and custom code that hasn't been categorized (same source). Separately, Wix's general privacy article confirms the banner logs consent automatically: "By default, consent collected through the Cookie Banner and the Do Not Sell My Personal Information Link is automatically logged so you can access the info at any time," including each visitor's "IP address, the date & time of their visit and the exact types of cookies they've accepted or refused" (Wix Help Center, "Displaying a Usercentrics for Wix Cookie Banner", checked September 2026).

Not one it documents as native. Webflow's own Help Center groups consent-related settings under a "Consent management" section, and every article in it is either about tracking defaults for Webflow Analyze and Optimize (Webflow's own analytics and testing tools) or about integrating a named third-party app — there's no article describing a general-purpose, site-wide cookie banner that Webflow ships itself (Webflow Help Center, "Consent management", checked September 2026).

What Webflow does document is three tracking-default options for its own Analyze/Optimize tools, and two of them explicitly require you to bring your own consent tool: "Let visitors opt out... You must integrate a consent management solution to utilize this option," and "Don't track by default... Waits for consent before tracking begins. You must integrate a consent management solution to utilize this option" (Webflow Help Center, "Analyze & Optimize compliance with privacy laws", checked September 2026). Webflow's own disclaimer on that page is worth repeating here rather than paraphrasing away: "The content presented here is provided only for informational purposes and is not meant to serve as legal advice" (same source).

The two integrations Webflow's help center walks through by name are Consent Pro and DataGrail. Consent Pro is the more fully documented of the two: "Consent Pro integrates directly with Webflow and provides a solution to manage consent tracking and give site visitors the option to opt in or out of site tracking," and it "integrates automatically with Webflow Insights (i.e., Analyze and Optimize), blocking or loading scripts based on user consent" (Webflow Help Center, "Integrate Consent Pro for consent management", checked September 2026). It has a real free/paid split worth knowing before launch: "The Consent Pro app is free to use on staging .webflow.io URLs. If you want to use Consent Pro on your custom domain, you'll need an active Consent Pro plan" (same source) — so a banner that works fine in staging can simply not appear once you publish to your real domain without upgrading.

Shopify's is a built-in admin setting, not a bolt-on app: "A cookie banner is a notification that displays on a website to inform visitors about the use of cookies and asks for their consent to the use of cookies and similar technologies" (Shopify Help Center, "Configuring customer privacy settings", checked September 2026). You configure it from Settings > Customer privacy > Cookie banner, choosing either automated defaults or manually setting which regions see it and customizing its appearance and color.

Shopify scopes it explicitly to its own commerce surfaces — the banner covers "storefront, cart, and checkout and customer account pages" (same source) — and to its own tracking tools: it "governs Shopify-specific tools, including cookies and Shopify Pixels." By default it auto-activates for "visitors in the UK and EEA regions, if you have active markets in these regions," though a merchant can turn it on for other regions too (same source). That regional default is worth checking directly if most of your traffic is outside the UK and EEA — the banner won't show elsewhere unless you change that setting yourself.

Side-by-side: what each one actually is

BuilderWhat ships nativelyScopeReal limit
SquarespaceBuilt-in banner in Cookies & Data Privacy panelSite-wide; explicitly covers Google Analytics consentDoesn't disable most connected third-party services on its own
WixBuilt-in banner, powered by a Usercentrics partnershipSite-wide; blocks named Functional/Marketing/Analytics integrations until consentCan't guarantee blocking app-market apps or uncategorized custom code; premium features need a paid Usercentrics plan
WebflowNo native banner documented; tracking defaults for Analyze/Optimize plus named app integrations (Consent Pro, DataGrail)Depends entirely on which integration you addConsent Pro's banner only works on your custom domain with a paid plan — free on staging only
ShopifyBuilt-in banner in Settings > Customer privacyStorefront, cart, checkout, and account pages; governs Shopify's own tools and PixelsAuto-activates only for UK/EEA markets by default

What should I actually do before launch?

  1. Check which regions your visitors are actually in, since Squarespace, Wix, and Shopify's automated defaults assume specific jurisdictions (or none at all) unless you change them.
  2. Confirm the banner reaches your real domain, not just a preview. Webflow's Consent Pro is the clearest example of a tool that behaves differently on staging vs. production.
  3. List what the banner does and doesn't cover. None of the four tools here claims to block every third-party script automatically — Squarespace and Wix both say so directly.
  4. Get your own legal read on what you're required to disclose and collect, since none of these vendors states that their default text or settings satisfy your specific obligations.

This is one part of getting a generated or rebuilt site ready to launch — see Check an AI-Generated Website Before Launch for the fuller pre-launch checklist that a cookie banner setting fits into.

Bottom line: Squarespace, Wix, and Shopify each give you a built-in cookie banner you switch on and configure in settings, with different default scopes and different named limits on what it can't control. Webflow's help center documents tracking-consent options for its own analytics tools plus specific app integrations instead of a native banner — so on Webflow, the actual banner comes from whichever third-party tool you connect, not from Webflow itself.


Get the latest content from Figment. Subscribe today for Figma design guides and website building tips.


Figment.so

Contact

Twitter

Pricing

Privacy

Terms