This guide shows how to add a Blogger heatmap in about a minute, with no third-party gadget: you paste one snippet into Theme → Edit HTML, before </head>, because it has to load on every page before your clicks happen, and it renders nothing visible. Nothing to install. Blogger's own HTML/JavaScript gadget takes raw markup, which is all this needs — and unlike a theme edit, a gadget survives changing your theme.
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 Blogger, the right spot is Theme → Edit HTML, before </head>. 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.
Blogger is free, and every method here works on every blog, on blogspot.com or a custom domain. The HTML/JavaScript gadget is the safest place for most widgets, because gadgets survive theme changes. Editing the theme's HTML also works, but it's parsed as XML, so a snippet with stray characters can stop the theme from saving.
Blogger themes are parsed as XML, so characters like &, <, > and quotes inside a script can trigger errors such as "The reference to entity must end with the ';' delimiter" and refuse to save. Our snippet is a plain async script tag with no bare ampersands, so it pastes cleanly — but if you ever hit that error, wrap the code in //<![CDATA[ ... //]]> or encode the five reserved characters. This is the main reason to prefer a gadget over a theme edit.
The post editor has two modes. Compose escapes anything that looks like markup, so the snippet renders as visible text instead of a widget. Switch to HTML view before pasting, and avoid flipping back to Compose afterwards — Blogger sometimes rewrites the markup when it converts between the two.
Changing theme, restoring a backup or applying one of Blogger's own themes replaces the whole template, taking any code you pasted into it with it. Gadgets live in your layout settings instead, so they survive. Unless you specifically need the <head> position, use a gadget.
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. Blogger's own HTML/JavaScript gadget takes raw markup, which is all this needs — and unlike a theme edit, a gadget survives changing your theme. Installing a gadget for this would mean another dependency and update cycle just to show one widget.
Theme → Edit HTML, before </head>, 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. Blogger is served by Google's own infrastructure and the snippet is one async tag, so it loads after your post is already on screen. There's no cache to purge — saving a gadget publishes it immediately.
Layout editor: Add a Gadget → HTML/JavaScript. Theme editor: Edit HTML, paste above </head> or </body>. Post editor: switch to HTML view, then paste. Blogger mobile app: not supported — use the desktop dashboard. 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.