This guide shows how to add a Webflow heatmap in about a minute, with no app: you paste one snippet into Site settings → Custom code → Head code, because it has to load on every page before your clicks happen, and it renders nothing visible. Nothing to install. Webflow renders raw HTML and script tags inside a Code Embed element, so no third-party app sits between you and the widget.
A click heatmap records where visitors click on each page and draws those clicks as a colour overlay, so the hot spots stand out at a glance. It answers practical questions quickly: do people click the main button, do they try to click things that aren't links, and which parts of a long page get clicked at all? It records clicks only. It doesn't record sessions or keystrokes, and it doesn't show anything to your visitors.
On Webflow, the right spot is Site settings → Custom code → Head code. Because it has to see every click, the heatmap loads once in the head of every page and renders nothing visible. Give it a week or two of normal traffic before drawing conclusions, and look at your most important pages first: the home page, your best-selling product or your main sign-up page.
Webflow's Code Embed element and its site-wide and page-level custom code fields only run on a paid Site plan or a paid Workspace. On a free webflow.io staging site the fields are visible but the code doesn't run on the published page, which looks exactly like a broken snippet. Custom code also doesn't run inside the Designer, so always test on the published site.
Site settings → Custom code and the page-level code fields are gated behind a paid Site plan or a paid Workspace. On a free webflow.io staging project they're visible but inert, which looks exactly like a broken snippet. The Code Embed element has no such gate, so free projects are not locked out — put the snippet on the canvas instead.
A Code Embed shows a grey placeholder in the Designer, and site-level code doesn't execute on the canvas at all. Preview is unreliable for third-party scripts too. Publish, then check the live domain in a normal tab. Most 'the widget doesn't work on Webflow' reports are an unpublished change.
Webflow already loads its own jQuery; importing another version breaks interactions site-wide. Our snippet has no jQuery dependency, so nothing to do here — but if you're pasting several third-party tags, that's the usual culprit. Each code field also caps at 50,000 characters; past that, host the file externally and link it.
A heatmap shows what people did, not why. It can't replace talking to customers or a proper A/B test, and on pages with only a handful of visits the patterns are mostly noise.
Nothing to install. Webflow renders raw HTML and script tags inside a Code Embed element, so no third-party app sits between you and the widget. Installing an app for this would mean another dependency and update cycle just to show one widget.
Site settings → Custom code → Head code, because it has to load on every page before your clicks happen, and it renders nothing visible.
It adds one small script, loaded asynchronously, so it doesn't block your page from rendering. Any third-party script has some cost, so check your page speed before and after adding it. Webflow serves your site from its own CDN and the snippet is a single async tag, so it loads beside your content rather than in front of it. Put JavaScript in Footer code rather than Head code when you don't need it early — Webflow recommends the same thing. Nothing to purge; publishing replaces the page.
Webflow Designer: Add (+) → Code Embed. Page settings: paste inside the <head> tag or before </body> for one page. Site settings: Custom code → Head or Footer for every page. CMS Collection templates: drop a Code Embed into the template. Any builder with a raw-HTML or code block will render it.
No. It records click positions on the page, not session videos, form input or keystrokes, and it isn't shown to your visitors.