Do I need a paid Webflow plan?

Yes, but either kind counts: a Core, Growth, Agency or Freelancer Workspace, or an active Site plan on the project. Webflow lists both as unlocking custom code in Site and Page settings.

Does the script survive a Designer republish?

Yes. Custom code lives in Site settings under the Custom code tab rather than in the canvas, so redesigning pages does not remove it and every publish includes it.

Does it work with Webflow Ecommerce and Memberships?

Yes on storefront and member pages, which render the normal site template. Webflow also notes that scripts you add sit outside its control and may carry implications for your own PCI obligations, which is worth reading before adding anything to an Ecommerce site.

Can I load the widget on some pages only?

Yes: leave the site-wide Footer code field empty and add the tag to the Before field in each page's own settings. Do not do both, because page code is added on top of site-wide code, not in place of it.

Will the widget show in the Designer or in preview?

In preview, yes: Webflow says the effects of custom code appear in preview mode. It does not go live until you publish, and the staging subdomain has to be registered in Inclusify before it will run there.

Webflow

Inclusify installs on Webflow as one paste into the Footer code field in Site settings Custom code, which Webflow renders before the closing </body> tag on every page. Webflow’s requirement is either a Core, Growth, Agency or Freelancer Workspace, or an active Site plan on the project, and the role has to be Site manager or Designer. One field, one Save, one publish. Publish to the staging subdomain first: Webflow names it as the place to test custom code, and it is a separate hostname you will need registered in Inclusify.

Register the domain first

Add your domain in the Inclusify panel before you paste the script tag. Bundles are built per registered domain, and an unregistered one fails silently: the script URL still returns HTTP 200, but what it serves is a single console.log saying the domain is not registered. There is no error to find and no widget appears.

Installation Steps

Open Site settings

Open Site settings for the project. Webflow used to call this Project Settings.

Navigate to Custom code

Click the Custom code tab on the left.

Add Footer code

Paste the widget code in the Footer code field, which Webflow renders before the closing </body> tag on every page:

HTML

<script src="https://app.inclusifyapp.com/w/YOUR-DOMAIN.com.js" async></script>

Replace YOUR-DOMAIN.com with your actual domain.

Save & Publish

Click Save changes, then publish. Webflow says the effects of custom code appear in preview mode, so seeing the button there is not proof it is live: nothing reaches a visitor until you publish, and the publish dialog asks which domains to publish to. Tick every domain you want updated, including the webflow.io staging subdomain if you test there.

Page-Specific Installation

To add the widget to specific pages only, leave the site-wide Footer code field empty and use the page’s own field instead. Do not use both: Webflow documents page custom code as applying to that page and appearing after any site-wide custom code, so the two are additive and the tag would run twice on that page.

Open the page in the Designer
Open Page settings for that page
Scroll to Custom code
Paste the code in the Before </body> tag section and save

Notes

• Custom code needs either a Core, Growth, Agency or Freelancer Workspace, or an active Site plan on the project. Either one is enough; a free Starter Workspace with no Site plan is not
• The Head code and Footer code fields hold up to 50,000 characters each, and so do their Page settings equivalents. The widget tag is under 100
• Works on all Webflow templates and custom designs, and on Memberships and Ecommerce storefront pages, which render the normal site template
• Webflow notes that scripts you add are outside its control and may carry implications for your own PCI obligations. Worth reading before you add anything to an Ecommerce site
• Newly published Webflow sites include jQuery, and Webflow warns against importing another copy of it. The widget bundle has no jQuery dependency, so it does not participate in that conflict

What needs attention on Webflow

A Workspace plan unlocks it too, not only a Site plan

Webflow's requirement is either side of an or: a Core, Growth, Agency or Freelancer Workspace, or a site with an active Site plan. Site managers and Designers on one of those can add custom code. A site on a free Starter Workspace with no Site plan has the tab but nothing that survives publishing.

Page-level code adds to the site-wide code, it does not replace it

Webflow documents page custom code as applying to that page and appearing after any site-wide custom code in the markup. So a page that has its own Before </body> code still gets the site-wide tag, and pasting the widget tag in both places is how you end up with two buttons on that page.

The staging subdomain is a different hostname

Every site gets a yoursite.webflow.io subdomain, and Webflow recommends it for testing custom code before pushing to production. The bundle checks window.location.hostname against the domains registered to your Inclusify website before it renders anything, and logs "Inclusify: This widget is not licensed for" and that hostname when it does not match. localhost and 127.0.0.1 are the only exemptions. So the staging subdomain has to be registered in Inclusify as well, or the console will report the widget as not licensed on the one URL you were told to test with.

The Head code and Footer code fields in Site settings hold up to 50,000 characters each, and so do the equivalent Page settings fields. The widget tag is under 100 characters, so a character-limit error means something else in the field needs pruning.

Verify the installation

Publish to the Webflow staging subdomain first. Webflow names that subdomain as the place to test custom code without pushing changes to your custom domain.
Register the staging hostname in Inclusify before testing there. The bundle checks window.location.hostname against the domains registered to your Inclusify website before it renders anything, and logs "Inclusify: This widget is not licensed for" and that hostname when it does not match. localhost and 127.0.0.1 are the only exemptions.
Open the published URL in a private window and confirm the accessibility icon appears.
In the publish dialog, check that every domain you use is ticked. Webflow publishes to the domains you select, so a custom domain can sit on an older build than the staging subdomain.
Custom code effects show in Webflow's preview mode as well, but preview is not proof: nothing is live until you publish.

Widget bundles are served from a CDN and cached for a few hours. If you changed widget settings in the panel and the site still shows the old configuration, wait for the cache to expire or load the script URL directly with a cache-busting query string (`?v=2`) to confirm the new version is being served.

Troubleshooting Webflow installs

The widget works on yoursite.webflow.io but not on the custom domain.: The custom domain was not ticked in the publish dialog, so it is still serving an older build. Open Publish, check every domain you want updated, and publish to the selected domains.
The staging subdomain logs that the widget is not licensed.: yoursite.webflow.io is a separate hostname from your custom domain and has to be registered in Inclusify too. Add it in the panel, or do your testing on the production hostname instead.
The Custom code tab is present but the field is disabled.: Neither condition Webflow requires is met: the project has no active Site plan, and the Workspace is not on Core, Growth, Agency or Freelancer. Either one unlocks the field.
Webflow rejects the code with a character-limit error.: The field is at its 50,000-character cap. Remove unused snippets to make room; the widget tag itself is well under 100 characters.
The widget appears twice on one page.: The tag is in the site-wide Footer code and in that page's Before </body> field. Page-level code is added after site-wide code rather than instead of it, so both run. Remove one.

Webflow questions

Do I need a paid Webflow plan?: Yes, but either kind counts: a Core, Growth, Agency or Freelancer Workspace, or an active Site plan on the project. Webflow lists both as unlocking custom code in Site and Page settings.
Does the script survive a Designer republish?: Yes. Custom code lives in Site settings under the Custom code tab rather than in the canvas, so redesigning pages does not remove it and every publish includes it.
Does it work with Webflow Ecommerce and Memberships?: Yes on storefront and member pages, which render the normal site template. Webflow also notes that scripts you add sit outside its control and may carry implications for your own PCI obligations, which is worth reading before adding anything to an Ecommerce site.
Can I load the widget on some pages only?: Yes: leave the site-wide Footer code field empty and add the tag to the Before </body> field in each page's own settings. Do not do both, because page code is added on top of site-wide code, not in place of it.
Will the widget show in the Designer or in preview?: In preview, yes: Webflow says the effects of custom code appear in preview mode. It does not go live until you publish, and the staging subdomain has to be registered in Inclusify before it will run there.

Webflow documentation

Every Webflow-specific requirement, menu path and limit on this page comes from these pages. Menus move, so check them against your own admin if something does not match.

Inclusify for Webflow covers what the widget does on a Webflow site, and pricing.
Script installation generates the embed code for your domain.
Customization covers the position, colour and size of the widget button.