Live · Website builders
Train on your Webflow URLs, paste the embed into site custom code, and publish no Webflow app marketplace dependency required. Train on published Webflow CMS URLs—not only the homepage—then paste the footer snippet in Project Settings. Republish after pricing or policy edits so crawled sources match live pages.
Setup
01
Add your published Webflow domain (and key CMS collection pages) as training sources. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
02
In Site settings → Custom code, paste the FoundChat snippet into the Footer code section. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
03
Publish to staging/production and confirm the widget on a live Webflow page. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
Use cases
Answer feature questions on Webflow launch pages. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
Offer AI coverage without rebuilding the Webflow project. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
Evidence
Standard Webflow pattern: footer script loads on all pages after publish. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
Re-crawl when you publish content updates so answers stay aligned with the site. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
FAQ
Site settings → Custom code → Footer code, then publish. That pattern loads the widget across published pages.
Yes. Add published CMS collection URLs as training sources and re-crawl after major content publishes.
No. Custom code plus a FoundChat workspace is enough for most marketing sites.
Test on a staging domain first if you have one, then publish to production once escalation rules look right.
Related
Join founders using FoundChat for support, sales, onboarding, and lead capture.
No credit card required · Live in minutes · Cancel anytime.
