Does Consent Pro Basic work on exported Webflow sites?

Consent Pro
1

Hi,

I have a Webflow site that has been exported and is hosted on my client’s own server (not on Webflow Hosting).

The Consent Pro runtime script is correctly loaded, but on the production domain I get:

“Consent Pro: not available for production use. Please purchase a plan…”

Before purchasing the Basic plan, I’d like to confirm:

  1. Does the Basic plan support exported Webflow sites hosted outside of Webflow?
  2. Is one license required per production domain?
  3. Is there anything else to configure after purchasing the plan?

Thank you!

2

Hey @fwilzius! Here’s what you need to know before pulling the trigger:

Yes, Consent Pro is fully supported on exported Webflow sites hosted on any server. The “not available for production use” message you’re seeing is expected behavior when the script runs on a custom domain without an active license tied to it — purchasing a plan is exactly what resolves that.

One license covers one custom domain, and there’s no special tier required for exported sites. The Basic plan works the same whether your site is Webflow-hosted or self-hosted. If your client has a single production domain, one license is all you need.

After purchasing, the most important step is linking your production domain to the license inside your Finsweet dashboard at my.finsweet.com/plans. That’s the step most people miss — the license exists but the domain hasn’t been registered to it yet.

Beyond that, make sure these are all in place for the exported site:

  1. Consent banners have been added inside Webflow
  2. You’ve scanned the site, labeled all trackers, and resolved any action items in the app
  3. The Consent Pro script is installed at the top of the <head> of your exported HTML
  4. A license is configured for your custom domain

Once all four are done, the app should show “You are all set” and the banner will work correctly on your production domain. :flexed_biceps:

One thing worth flagging for self-hosted setups — if your client’s server uses a strict Content Security Policy (CSP), you may need to add api.consentpro.com and *.consentpro.com to the connect-src directive. Otherwise the browser can block Consent Pro’s license verification requests. Easy fix in the server or hosting control panel config.

Here’s a link to the docs

Keep us updated, thanks