Try Omnifox free 7 days free. No credit card required.
Guides

Add Chat to Webflow: Site-Wide or Only on Specific Pages

Add a chat widget to Webflow with project custom code (Site settings → Custom code) or per page. Publish, test and set up proactive messages by URL.

September 06, 2026
Add Chat to Webflow: Site-Wide or Only on Specific Pages
In this article

    Webflow gives you two places to put a chat widget. Put the script in Site settings → Custom code → Footer code and every page gets the chat, including CMS collection pages you have not created yet. Put it in Page settings → Before tag and only that page gets it. The wrong pick either sprays a chat button across your legal pages and 404, or leaves your pricing page silent.

    The short answer for most sites: add chat to Webflow site-wide once, then use the chat platform's triggers to decide what happens on each URL. That keeps Webflow clean and moves the "which page gets what" logic to a place marketing can change without a designer publishing the site.

    Site-wide or per page: how to decide

    Situation Where to put the code Why
    Marketing site with blog, pricing and product pages Site settings → Custom code → Footer code One paste, applies to all current and future pages, including CMS templates
    Single campaign landing page on a subfolder Page settings → Before Nothing else on the site should show chat
    Multiple client sites managed by an agency Site settings on each site, one channel per site Each widget gets its own key and reports its own domain
    A page where the widget should be hidden (checkout, legal) Site-wide install plus a "hide widget" trigger by URL Avoids maintaining two installs

    If unsure, go site-wide. Hiding the widget on two pages with a trigger beats remembering to add code to every new page.

    Step by step: site-wide install in Webflow

    1. In your chat dashboard, copy the install line. In Omnifox: Channels → your website chat channel → Install.
    2. Open the project's Site settings from the Webflow dashboard.
    3. Open the Custom code tab.
    4. Paste the snippet into the Footer code box.
    5. Click Save changes.
    6. Publish the site. Custom code is not visible in the Designer preview; it only runs on the published site.

    The line you paste is one script tag:

    <script src="https://omnifox.io/widget/loader.js" data-widget-key="YOUR_KEY" async></script>
    

    After publishing, open the live site in a private window. The chat button appears at the bottom corner, and the dashboard lists the domain it was seen on. That "installed on" indicator is your proof the paste worked when a client asks "is it live?" and you are not in front of the site.

    Webflow's own documentation for this screen lives in Webflow University; search for "custom code in head and body tags" if the tab names change.

    Step by step: only on a specific page

    1. In the Designer, open the Pages panel and hover over the page you want; click the gear icon to open its settings.
    2. Scroll down to the Custom code section of the page settings.
    3. Paste the snippet into Before tag.
    4. Save and publish.

    Page-level code on a CMS collection template applies to every item in that collection, which is usually what you want for "locations" or "services". And if the same script is also in the site-wide footer, the widget loads twice on that page. Keep it in one place.

    Webflow plan limits, staging and custom domains

    A few Webflow-specific details trip people up:

    • Starter (free) plan. Custom code is limited on free sites; site-wide custom code has required a paid Site plan. Check the current plan comparison before debugging a widget that is simply not allowed to load.
    • webflow.io staging domain. The widget loads on yoursite.webflow.io, listed separately from your custom domain, so you can test triggers on staging first. If your site answers on both example.com and www.example.com, both may appear; that is expected.
    • CMS collection pages. Site-wide footer code covers them. If you use page-level code, remember it goes on the collection template, not on individual items.
    • Republish after every change, and to every domain: it is easy to publish staging and forget the custom domain.

    Triggers by URL: the part Webflow cannot do on its own

    Once the script is everywhere, the interesting work happens in the chat dashboard. Triggers combine conditions (URL contains, starts with or equals; time on page; scroll percentage; exit intent on desktop; device type) with actions: show a proactive bubble, open the chat, hide the widget, start an AI conversation, assign to a team or show the department selector.

    For a typical Webflow marketing site that means:

    • Homepage: nothing proactive, just the button. Let people read.
    • /pricing after 30 seconds on page: a bubble from a named person with an avatar.
    • /demo: open the pre-chat form after 20 seconds, asking for work email only.
    • /blog/*: an AI agent answers questions from the knowledge base; no bubble, no interruption.
    • /legal/*, /careers: hide the widget.

    The pricing bubble might read:

    Hi, I'm Sam from the Omnifox team. If you're comparing plans, I can tell you in one message which one fits a team of your size. Want me to?

    Set the pricing trigger to "once per session" so a visitor bouncing between pricing and features does not get the same bubble four times. More texts by page are in 12 proactive chat messages for your website.

    Webflow forms vs the pre-chat form

    A Webflow form submission goes to your email and the Forms tab, and then the visitor leaves and waits. The widget's pre-chat form asks the same fields (name, email, phone, anything you configure, required or optional) and immediately starts a conversation a human or an AI agent can pick up. A practical split:

    • Keep the Webflow form on the contact page for people who explicitly want to write a message and leave.
    • Use the pre-chat form on pricing and demo pages, where the visitor has a question now and will not wait for a reply email.
    • Make the pre-chat form skippable on content pages so nobody is blocked from asking a quick question.

    GA4 tracking without extra code

    Webflow sites usually already have GA4 through the site settings or Google Tag Manager. The widget sends four events (widget_loaded, widget_opened, conversation_started, message_sent) to dataLayer and gtag automatically if they exist. Nothing to add in Webflow: mark conversation_started as a key event in GA4 and it shows up next to form submissions. The conversation also stores landing page, referrer and UTM parameters, so a LinkedIn lead from the UK and a Google Ads lead from the US are told apart in the contact record.

    An agency running several Webflow client sites

    A design studio in Manchester manages seven Webflow sites: two dental practices, a solicitor, a boutique hotel and three B2B firms. Each site gets its own website chat channel with its own key, appearance and triggers, all in one account. The studio pastes each key into that site's footer code, publishes, and watches the "installed on" list confirm the domain. The hotel shows a booking bubble on room pages; the solicitor shows a pre-chat form asking only for name and email; the B2B firms route by department to the client's own sales team. The website chat for agencies post goes deeper into permissions and hand-over.

    Frequently asked questions

    Should I put the chat script in Head code or Footer code in Webflow?

    Footer code. The script is async and does not need to run before the page renders, so the footer keeps it from competing with your fonts and CSS. Head code works too, with no benefit.

    Does the widget show on the Webflow Designer preview?

    No. Custom code only runs on the published site, including the webflow.io staging domain. Publish, then test in a private browser window.

    Can I show chat on CMS pages but not on the homepage?

    Yes. Install site-wide, then add a trigger with the condition "URL equals your homepage" and the action "hide widget". The CMS pages keep the chat and the homepage stays clean.

    Install once, then let triggers do the routing

    The best Webflow setup is boring on the Webflow side: one script in Footer code, published once. Which page shows a bubble, which asks for an email and which stays silent lives in the chat dashboard, where it can change on a Tuesday afternoon without a redeploy.

    Start a 7-day free trial, paste the line into your Webflow footer, and see the domain appear in your dashboard within a minute. Everything the widget can do on a Webflow site, from URL triggers to co-browsing, is described on the website chat page.

    Ready to try it in your business?

    Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.

    7 days free. No credit card required.

    Comments (0)

    No comments yet. Be the first to share your thoughts.

    Leave a comment

    Your email is never published. Comments are moderated before appearing.

    Markdown supported. HTML is stripped.

    Read more

    Message us on WhatsApp