Adding AI chat to a Webflow site takes one snippet in Site Settings, Custom Code, Footer Code. There is no app to install and nothing to add to the canvas, so it appears on every page and survives a redesign.
The more interesting part is what it can read, because Webflow sites usually keep most of their real content in CMS collections rather than static pages.
Add it in three steps
- Add your site address and let the assistant read it. It crawls your published pages the way a visitor sees them, including every CMS item that renders as a page.
- Check what it read. Every indexed page is listed, so you can see what it knows before a visitor talks to it. Add PDFs or spec sheets that never made it onto a page.
- Paste one snippet into Site Settings, Custom Code, Footer Code, then publish. That is the whole install.
Footer rather than head matters: it loads after your page, so it never blocks rendering and your Core Web Vitals are unaffected.
How CMS collections are handled
This is where Webflow differs from a static site, and where people expect trouble.
The assistant reads published pages, not your CMS. In practice that is the same thing for anything with a collection page template: every blog post, case study, help article, product or listing that renders at its own URL is read like any other page.
What it cannot see is a collection item that never renders. If you keep fields in a collection that are only used inside a component elsewhere, or items with their template disabled, they are invisible to it. Worth checking before you conclude something is missing.
Keeping it current when you publish
Webflow sites change often, which is the point of the CMS. An assistant that read your site once and never again will confidently repeat last quarter's pricing.
Rescanning on a schedule handles that, and new pages get picked up as they appear. If you publish something time-sensitive, rescan on demand rather than waiting for the schedule.
Styling it to match
Webflow sites are usually designed carefully, and a chat widget in the wrong colour is the fastest way to make one look cheap. Set the widget colour, avatar, greeting and position to match before you launch, not after somebody notices.
Position deserves a moment of thought. Bottom right is conventional, but if your design already has something anchored there, move the widget rather than letting two things fight.
What it answers, and what it hands over
It answers from your published pages and uploaded files, and links the source page under each reply. When your content does not cover something, it says so and offers a person rather than guessing, which matters more on a marketing site than people expect: the questions arriving through a Webflow site are usually pre-sale, and a wrong answer there costs a customer rather than a ticket.
When a person is needed, the conversation goes to your team with the full history attached. How handoff works.
FAQ
Answers, before you ask.
Do I need a Webflow app or plugin?
No. One snippet in Site Settings, Custom Code, Footer Code. It applies to every page and survives a redesign, because it is not tied to anything on the canvas.
Does it read Webflow CMS collections?
Yes, because it reads published pages. Any collection item with a live page is read like any other. Items that never render as a page are not visible to it.
Will it slow my site down?
No. The snippet loads asynchronously after your page, so it does not block rendering and does not affect Core Web Vitals.
What happens when I republish?
Nothing breaks. The snippet lives in site settings rather than on the canvas. Content changes are picked up on the next scheduled rescan, or immediately if you rescan on demand.
Add it to your Webflow site today.
Paste your address, watch it read every page and collection item, then drop one line into footer code. Free to start.
No credit card to start.