Guides Instructions
Cookie banner for Webflow: GDPR-compliant & warning-proof
Webflow is great for design - but it often lets you down when it comes to data protection. The native consent feature does not reliably block trackers before someone consents. This makes your Webflow page legally compliant.
The Webflow data protection problem
Webflow’s built-in cookie consent feature often loads embedded services (Maps, YouTube, Analytics, marketing pixels) before consent has been given — this could result in a warning.
As soon as you use integrations in Webflow such as Google Analytics, the Meta Pixel, YouTube embeds or Maps, these often fire as soon as the page loads. The native consent feature doesn’t cover all scenarios and sometimes kicks in too late.
For a GDPR-compliant Webflow site, you need genuine pre-consent blocking — trackers must only load after active consent has been given.
What "GDPR-compliant" actually means
Three key elements: a banner with an equivalent ‘Reject all’ option, effective blocking prior to consent, and a privacy policy that is appropriate for the services being loaded.
- A banner with “Reject All” is equivalent to Level 1.
- Trackers blocked until consent is given — including Webflow embeds.
- Privacy policy listing all identified providers (Art. 13 GDPR).
Integrate cookie banner in Webflow
The BlueOcean snippet appears in Webflow under Site Settings → Custom Code → Head Code, as the very first script — before all the others.
Here's how:
- Webflow → Site Settings → Custom Code → Head Code.
- Insert the BlueOcean snippet as the first script (before GA, Pixel, Embeds).
- Publish — done. Banners, blocking and privacy text run automatically.
Important: The snippet must be placed at the very top so that the auto-blocker can intercept any subsequent trackers.
Check whether it is really blocking
Do the counter-check: a scan will show whether trackers are still active before you give your consent — and give you a clear GDPR rating.
With BlueOcean’s free website check, you can see in just a minute which trackers are loading on your Webflow site before consent is given. Simply enter your URL above.
Let's take a quick look at your sites
In a 15-minute call you’ll see where your client sites stand — and how to secure them effortlessly.
FAQ
Is Webflow's native cookie consent sufficient?
Often not. It doesn’t reliably block embedded services and marketing pixels before consent is given. For GDPR compliance, you need genuine pre-consent blocking.
Where do I insert the cookie banner in Webflow?
Under Site Settings → Custom Code → Head Code, as the very first script — before Google Analytics, Meta Pixel and any embeds.
Do I need a separate privacy policy for Webflow?
Yes. It must list all the services that are actually loaded. BlueOcean generates this list based on the scan and keeps it up to date automatically.