Webflow

With the Okito app (recommended)

1. Install the Okito Cookie Consent app from the Webflow Apps marketplace, or open Webflow in the Okito dashboard and click Connect.
2. Authorise the app for your Webflow site. Okito asks only for permission to read your sites and manage custom code.
3. Sign in to Okito (or create an account) and pick the Okito website that matches your Webflow site's domain.
4. Okito adds its script to your site's custom code. Publish your Webflow site.

The app adds one small loader, https://cdn.okito.com/wf/1.0.0/YOUR_WEBSITE_KEY.js, which loads your Okito script. Webflow pins it with an integrity (SRI) hash under version 1.0.0. The loader is the same for every site and never changes, so changes to your banner (texts, languages, an A/B test) and Okito updates apply without applying the script again or publishing.

Connected your site before the loader? Then the app registered the Okito script itself (/js/YOUR_WEBSITE_KEY), whose pinned hash stops matching when your banner settings change or Okito updates, and the browser then refuses to load the banner. Switch once: open Webflow in the Okito dashboard, click Update Okito script, then Publish your Webflow site.

The app doesn't add the early blocker. If tracking tags (Meta Pixel, Hotjar …) are written into your site's custom code, paste only its line, not the rest of the installation code, as the first line of Site settings → Custom code → Head code, above those tags:

<script src="https://cdn.okito.com/js/YOUR_WEBSITE_KEY/blocker.js"></script>

By hand

1. In Webflow, open Site settings → Custom code → Head code.
2. Paste the code from Install banner in the Okito dashboard.
3. Save and Publish the site.

Custom code requires a paid Webflow site plan.

Remove Okito

Installed with the app

1. In the Okito dashboard, open Webflow and click Disconnect. Okito removes its script from your site's custom code and ends its access to your Webflow site. You can also uninstall the Okito Cookie Consent app in Webflow (Site settings → Apps & integrations); Okito then removes its script too.
2. Check Site settings → Custom code. If Webflow ended the app's access before Okito could remove the script, an Okito script (OkitoCookieConsent, loading from cdn.okito.com) can still be there: remove it.
3. If you pasted the early blocker line by hand, delete it from Head code.
4. Publish your Webflow site. Until you publish, the live site keeps the banner.

Installed by hand

Delete the Okito code (and the early blocker line, if you added it) from Site settings → Custom code → Head code, save and Publish the site.

Removing the script from your site doesn't delete your Okito website or its consent records; delete the website in the Okito dashboard if you no longer need them.