How to add a cookie consent banner to Webflow

How to add a cookie banner to Webflow

KookiOk does not have a native Webflow app - on Webflow it installs as a single pasted script, the same way you would add any third-party snippet. Here are the exact steps:

• Create a free KookiOk account and add your Webflow site's domain. KookiOk scans it automatically and classifies the cookies it finds.
• Design your banner: pick a template and your brand colour, add custom CSS if you want, or describe your brand and let AI style it.
• Copy your one-line KookiOk install script from the dashboard.
• In Webflow, open Site settings -> Custom Code and paste the script into the Head Code field. This loads the banner site-wide on every page.
• Optional - to load it on a single page only, open that page's settings, find the page-level Custom Code panel, and paste the script there instead.
• Click Save Changes, then Publish your Webflow site so the change goes live on your real domain.

That is the whole install - no developer required and nothing to maintain inside Webflow. When you publish, the banner appears and non-essential scripts stay blocked until the visitor opts in.

What you get free with KookiOk on Webflow

KookiOk is free for Webflow site owners, with no per-site fee and no page-view metering - useful when one Webflow account hosts several projects or client sites. Everything you need for a compliant banner is included:

The only trade-off on the free plan is a small "Powered by KookiOk" badge on the banner.

Why a Webflow site needs a cookie banner

Webflow itself is just the platform - it is the tools you add on top that set non-essential cookies and trigger the need for consent. If your Webflow site uses analytics, advertising pixels or embedded third-party content, you are storing or reading information on the visitor's device, which under the EU ePrivacy rules requires prior consent.

On a typical Webflow build, the usual culprits are:

• Analytics such as Google Analytics, added via Webflow's integrations or Custom Code.
• Advertising and remarketing pixels (Google Ads, Meta Pixel, LinkedIn, TikTok).
• Embedded content like YouTube videos, Google Maps, social widgets or third-party forms.
• Heatmaps, A/B testing or session-recording scripts pasted into Custom Code.

The ePrivacy Directive requires consent before these load, and the GDPR sets the conditions for that consent to be valid: freely given, specific, informed and as easy to withdraw as to give. A consent banner that blocks non-essential cookies until the visitor agrees is the standard way to meet both. KookiOk also detects and honours GPC, so the same setup helps with US opt-out signals too.

Not sure what your Webflow site actually loads? Run a free cookie scan first - KookiOk crawls your published site with a headless browser and lists every cookie and tracker that fires before consent, so you know exactly what the banner needs to cover.

Frequently asked questions