Adding an assistant to a Webflow site

Webflow gives you two places to put third party code, and choosing the wrong one causes the two most common problems people hit.

Where the code goes

For a site wide widget, use Project Settings, Custom Code, Footer Code. This injects before the closing body tag on every published page. Putting a widget script in the head is possible but usually unnecessary and more likely to affect render timing.

For a single page, use Page Settings, Custom Code instead. Page level code is the right choice if you only want the assistant on documentation or pricing.

Constraint one: custom code requires a paid plan

Custom code in Project Settings is not available on the free Webflow plan and requires a site plan. This catches people out mid setup. Check before you promise a client a same day install.

Constraint two: code only runs on published sites

Custom code does not execute in the Designer preview. You have to publish, including to the staging webflow.io subdomain, to see the widget at all. Testing in the Designer and concluding the embed failed is a common false alarm.

Training sources on a Webflow site

Webflow sites usually have a clean sitemap at /sitemap.xml, which makes source selection straightforward. Two things to exclude:

• CMS collection item pages that are near duplicates, such as a large tag or category archive.
• Any staging webflow.io URLs, so the assistant does not index and quote a staging copy of your site.

That second one matters more than it sounds. If both the custom domain and the webflow.io subdomain are crawlable, you can end up with two copies of every page in the index and inconsistent answers depending on which chunk retrieval picks.

Interaction conflicts

Webflow Interactions are a common source of z-index and scroll conflicts with a fixed position widget. If your site has a sticky nav, a full screen menu overlay or a scroll driven animation, check the widget launcher at mobile widths with the menu open. The usual fix is a z-index adjustment on your own overlay rather than on the widget.

A note on performance

Webflow sites often already carry jQuery plus the Interactions runtime. Adding a widget script is additive, so check your measured page performance before and after rather than assuming the impact is negligible. If the site was already close to a threshold, a third party script can push it over.