Webflow ships no consent banner for your visitors — you have to bring your own. Here's the one-script-tag install, plus how to gate the GA4, Meta Pixel, and embed scripts you've added.
Run the free cookie scanner on your site — no account needed. When you build your banner, the cookie categories are pre-selected from what the scan actually found.
In the dashboard, open Consent Banner, pick your position, theme, and colors, enable Google Consent Mode v2 if you use Google tags, and save. You'll get a one-line embed snippet with your banner ID.
In Webflow, open Site Settings → Custom Code and paste the snippet into Footer Code (before </body>). Save, then Publish — the banner deploys to your live domain with the next publish.
Your GA4, Meta Pixel, or Hotjar snippets live in the same Custom Code panels — change each to type="text/plain" with a data-consent-category so they only load after opt-in. Publish, open the site privately, and confirm the banner shows and consents appear in your log.
Custom code requires a paid Webflow site plan — the Custom Code fields are disabled on free staging-only sites.
<script src="https://policyforge.co/consent.min.js"
data-policyforge-consent="YOUR-BANNER-ID"></script>Paste it into Site Settings → Custom Code → Footer Code.
Webflow itself sets almost no cookies on published sites, so on Webflow nearly everything worth gating is code you pasted yourself — which is exactly what the text/plain + data-consent-category pattern handles. For YouTube or Vimeo embeds, either gate the embed code the same way or use YouTube's privacy-enhanced (youtube-nocookie.com) mode.
GDPR expects the banner to link to a policy that discloses every cookie your Webflow site sets. Generate one tailored to Webflow — default cookies and common integrations included.
What Webflow site owners ask before installing.
Banner, policies, scanner, and consent records — one plan, unlimited sites.
Included in Pro ($15/month) • Free cookie scanner, no account needed