What is heatmapping?
A heatmap takes thousands of visits to one page and paints them on top of it. Red and yellow where people click or tap most, blue and green where they rarely go, gray where nobody does. Scroll maps show how far down the page visitors get, as a fade from hot at the top to cold at the bottom. Move maps track the mouse, which loosely follows attention on a desktop. Together they turn a page from a design into a record of behavior.
The tools (Hotjar, Microsoft Clarity, Crazy Egg and others) work by adding a small script to the site that records interactions anonymously and aggregates them. Most also offer session recordings, which replay individual visits so you can watch a real person struggle with the form, and they split the maps by device, since a phone and a desktop are two different pages.
Why it matters
Why heatmapping matters
Analytics tells you what happened: how many came, how many left, which pages they saw. Heatmapping tells you where on the page it happened, which is the question a designer actually has. It shows the button people try to click that is not a button, the headline nobody reads because the hero image pushes it below the fold, the call to action that sits exactly where the scroll map goes cold. It replaces arguments about layout with evidence, and it does so on the live site with real visitors rather than in a lab.
In practice
How heatmapping works in practice
- 01
Start with a question, not a tool. Why does this landing page convert worse on mobile? Where do people give up on the product page? Install the script, pick the pages that matter and let them collect for long enough to mean something, usually a few hundred visits per device. Then read the maps against the question: the click map for what people want, the scroll map for what they saw, the recordings for the moments the maps cannot explain.
- 02
The output is a change. Move the call to action to where the clicks are, make the clickable-looking image a link, cut the section above the content nobody reaches. Then run the maps again, because a heatmap is a before-and-after tool. Pair it with an A/B test when the stakes are high and the traffic allows, so the change is measured rather than assumed.
Watch out
What people get wrong about heatmapping
Reading a heatmap as proof. A hot spot on an image may mean people love it, or that they expected it to open and it did not. The map shows where, not why; the recordings and the question supply the why. Second, running maps on pages with no traffic and drawing conclusions from forty visits. Third, forgetting the heatmap only shows people who came: it cannot tell you about the visitors the page never attracted, which is often the bigger problem.
And one for the lawyers: recordings and maps collect behavior, so the privacy notice has to say so, and form fields must be masked.
