- A cookie banner on its own does nothing. The important part is stopping scripts from running until a visitor agrees.
- At the time of writing, Webflow's own integration pages say it has no built-in consent layer, so you use an app, a consent tool or custom code.
- Webflow's consent API only controls its own Analyze and Optimize tools, not third-party scripts.
- If you use Google tags, set Consent Mode defaults before any tag runs.
- This is general information, not legal advice. Ask a qualified adviser what applies to you.
The short answer
To handle cookie consent on Webflow, you add a consent tool, through an app or custom code, and make sure that non-essential scripts do not run until a visitor agrees. Then you test it by looking at what actually loads. Many sites have a banner that looks right while tracking runs anyway.
This article is general information, not legal advice. The rules depend on where your business and visitors are, so ask a qualified adviser what applies to you.
What the rules are generally about
Laws differ, so treat this as a broad picture:
- EU and UK. The rules generally ask for consent before setting non-essential cookies, such as analytics and advertising cookies. Cookies that are strictly necessary for a service the visitor asked for are usually exempt. Consent should be a real choice, and people should be able to change their mind.
- Parts of the US. Some state laws, such as California's, focus more on notice and on the right to opt out of the sale or sharing of data.
- Elsewhere. Rules vary, and they change.
Regulators also look at design. Making "Accept" large and hiding "Reject" can be a problem in some places. Your adviser can confirm this for your markets.
What Webflow does and does not do
At the time of writing, Webflow's own integration pages describe consent as something you add, rather than a built-in banner. Check Webflow's current docs, as this could change.
Webflow does have a consent API in the browser, with methods such as wf.allowUserTracking() and wf.denyUserTracking(). These apply only to Webflow's Analyze and Optimize. They do nothing for Google Analytics, ad pixels or anything else you have added. If you use Analyze or Optimize, connect your consent tool to this API as well.
Also, adding scripts through custom code needs a paid site plan.
Your three main options
1. A Webflow Marketplace app. For example, Consent Pro by Finsweet is listed on the Marketplace, and says it blocks scripts until consent and can show banners by region. An app like this is a good start for most teams. It also lets you style the banner to match the site.
2. A consent management tool. Tools such as Cookiebot, Osano and Termly add a script to your site, and offer features such as scanning and consent records. These suit bigger sites or teams with several markets. Check current pricing and features.
3. A custom build. A small banner you write yourself, which only loads tags after a choice. It can be light and match your design, but you own all of the upkeep: categories, records, withdrawal and new rules. We only suggest this for simple setups with few scripts, and after checking it with your adviser. Finsweet Cookie Consent sits between this and an app.
No tool makes you compliant by itself. It depends on how you set it up.
Step 1: list what your site loads
Before you choose anything, make a list of what runs on your site:
- Analytics, such as GA4.
- Ad pixels from LinkedIn, Google or Meta.
- Session recording and heatmap tools.
- Chat widgets and CRM tracking.
- Embedded video, maps and booking tools. These often set cookies too.
- Everything inside Tag Manager.
Check the site settings, each page's custom code and any embed elements. Then sort each item into a category: essential, analytics, marketing or preferences.
Step 2: get the order right
This is where most setups fail. Scripts in Webflow's head code run on page load, and Webflow does not manage the order for you. So:
- Put the consent tool first in the head code.
- Move trackers into Tag Manager or the consent tool where you can, so that they can be held back.
- Remove any hard-coded duplicates. GA4 installed in both the Webflow settings and Tag Manager is a common example, and it means one copy may ignore consent.
- Replace embeds that set cookies with a click-to-load version, or check how your tool handles them.
Step 3: Google Consent Mode
If you use Google tags, read Google's consent mode guide. It tells Google tags what a visitor has chosen. There are two key steps:
- Set defaults before any tag runs. Where consent is needed, you start with denied values for
ad_storage,analytics_storage,ad_user_dataandad_personalization. - Update when the visitor chooses. Your tool sends an update, including if someone changes their mind later.
Consent Mode is a signal to Google's tags. It does not block other vendors, and it does not replace a banner. In its basic form, tags do not load until consent. In its advanced form, tags load but behave differently without consent. Ask your adviser which one suits you.
Step 4: design the banner
- Say plainly what you use cookies for.
- Offer clear Accept and Reject choices. We give them equal weight.
- Add a way to choose by category, if you use more than one type.
- Link to your privacy or cookie policy.
- Add a "Cookie settings" link in the footer, so people can change their mind later.
- Keep it usable with a keyboard and on a phone. See WCAG.
- Do not let it push the page around. It should not cause layout shift.
Consider your speed too. Consent tools and the scripts they control add weight, so check your Core Web Vitals afterwards.
Step 5: test what actually happens
Do not trust how the banner looks. Open a private window and use your browser's developer tools:
- Before any choice. Look at the Network tab and the cookies list. Non-essential trackers should not be there.
- After Reject. Reload and browse a few pages. There should still be no trackers.
- After Accept. Tags should load, and your analytics should record the visit.
- Change your mind. Reopen settings and withdraw. Trackers should stop.
- Different regions. If banners vary by location, test using a VPN.
Google's Tag Assistant can show your consent state for Google tags. Retest whenever someone adds a tag. Many problems appear months later, when a new script goes in with no review.
Expect a change in your numbers
Once tracking only runs after consent, analytics will usually show fewer visits. That does not mean that traffic fell. It means you can only see part of it now. Note the date of the change in your reports, and tell whoever reads them. Search Console and your CRM can act as a cross-check.
Keep your policy in line
Your privacy or cookie policy should match what the site does: which tools you use, what they do, how long the choice lasts and how to change it. When you add a tool, update the policy. Some consent tools can help by keeping a list of cookies. Have your adviser review the wording.
What to do next
Start with the list of scripts. It often turns up tags that you can simply remove, which helps both privacy and speed. If you want help with the setup, see analytics and tracking or contact us. We can set up and test the technical side, but your adviser decides what you legally need.
More reading: launch checklist and Webflow site speed.
Terms used: Webflow, Google Tag Manager



