A bright patch on a heatmap looks like an answer before anyone has asked what it represents. It might show clicks, cursor movement, scroll reach or measured gaze. Those signals describe different things, and confusing them can turn an attractive visualisation into a misleading account of what people noticed or wanted.
A heatmap uses colour to show the distribution or intensity of recorded data. In UX research, it often combines activity from several visits or participants into a view of a page, helping teams identify areas worth investigating more closely.
Read the measure before reading the colours
A click map shows recorded clicks or taps; it does not establish whether those actions were successful or deliberate. Repeated clicks on a static image might indicate that people expect it to enlarge, but they could also arise from another interaction pattern. A scroll map records how far visits reached, which is evidence of potential exposure rather than proof that the content was read.
Cursor movement is not a direct measurement of gaze. People can leave a pointer stationary while reading elsewhere. Similarly, an “attention” map may be based on dwell time rather than eye tracking, depending on the product. Microsoft Clarity’s heatmap documentation illustrates the range of available map types. Check the actual calculation instead of relying on the label.
Maps derived from eye tracking offer a different measurement, with their own accuracy and interpretation limits. None of these displays establishes comprehension simply by colouring an area red.
Check which experiences were combined
Inspect the sample size, reporting period and filters. Separate mobile and desktop when their layouts differ, and check how the tool handles dynamic content, overlays and personalised pages. A map overlaid on the current screenshot may otherwise place old activity against a layout that visitors never encountered.
Colour scales also affect comparison. The hottest area on one map need not contain as much activity as the hottest area on another if each is scaled independently. Use counts or rates with clear denominators when making a quantitative claim.
Follow a useful pattern into a specific question
In a fictional pricing page, few recorded visits reach the plan comparison near the bottom. Before moving it, investigate whether the intended audience needs that comparison, whether equivalent information is already available above it and whether visitors are leaving for unrelated reasons.
Session replay can help inspect the surrounding behaviour, and a focused usability study can examine how people choose a plan. Those methods may support an explanation; the heatmap supplies the starting observation.
Use the resulting hypothesis to guide a change and evaluate the relevant outcome. More clicks on a newly prominent button may be useful, but the product goal is usually what people can accomplish after clicking it. The map is most valuable when it helps the team reach that question.