When a website is not converting, owners tend to reach for one of two kinds of evidence. Heatmaps and session recordings show where visitors click, scroll and hesitate. Chat transcripts show what visitors actually say when they cannot find what they need. Both are useful, and they answer different questions. A heatmap tells you what people did; a transcript tells you why they were confused, in their own words. Used together, they can find friction faster than either alone, and neither needs a large budget or a data team. This guide explains what each shows and what it hides, which problems each is best at revealing, how to combine them in a simple monthly workflow, what to fix first and the privacy points to respect. It is written for small businesses with a website and a chat assistant, and it avoids implying that one replaces the other.
What a heatmap shows
- Click maps: where people click or tap, including things that are not links.
- Scroll maps: how far down the page visitors go.
- Move maps: where cursors hover on desktop, which loosely tracks attention.
- Session recordings: replays of visits, showing hesitation and frustration.
| Strength | Limit |
|---|---|
| Shows real behaviour, not opinions | Does not say why someone clicked or left |
| Reveals dead clicks, ignored buttons and buried content | Mobile behaviour is harder to read |
| Works without visitors having to say anything | Needs enough traffic to be reliable |
| Good at layout and design problems | Can raise privacy concerns if recordings capture personal data |
What chat transcripts show
- The exact questions visitors ask, in their words.
- What they could not find on the page.
- Objections: price, trust, timing.
- Intent: whether they were ready to book or just browsing.
- Where the conversation ended, and what the last message was.
| Strength | Limit |
|---|---|
| Explains the reason behind an action | Only covers visitors who chose to chat |
| Reveals missing content and unclear wording | Does not show what people did on the page |
| Feeds directly into improving documents | Needs someone to read a sample |
| Captures intent and language for marketing copy | Volume can be small on low-traffic sites |
What each is best for
| Question | Best source |
|---|---|
| Are people seeing my booking button? | Heatmap and scroll map |
| Why do they not book? | Transcripts |
| Which page do people give up on? | Heatmaps and recordings, plus analytics |
| What information is missing from that page? | Transcripts |
| Is a design change working? | Heatmap before and after |
| What words do customers use? | Transcripts |
| Are mobile visitors struggling? | Recordings, checked on a phone yourself |
The blind spots
A heatmap of a pricing page might show that visitors scroll to the price table and then leave. It cannot tell you whether the price was too high, the conditions were unclear or the visitor simply had the answer they wanted. A transcript that includes 'is that per hour or per visit?' points straight to the confusion. Conversely, transcripts miss the silent majority who never open the chat. A heatmap shows those visitors' behaviour. Neither has the whole picture.
A simple monthly workflow
- Pick one page that matters, such as your services or contact page.
- Look at the heatmap and scroll map for that page. Note ignored elements, dead clicks and where most people stop scrolling.
- Read the chat transcripts that started on or mentioned that page: what did they ask? Sample twenty.
- Form a hypothesis: for example, 'Visitors want the price but it is below the fold.'
- Make one change: move the price up, add a sentence, rename a button.
- Check again in a few weeks: look at the heatmap and the questions asked.
One page, one change, one comparison. It is slower than redesigning the whole site, but you learn what works.
Common patterns and fixes
| Heatmap sign | Transcript sign | Likely fix |
|---|---|---|
| Many clicks on non-clickable text | Visitors asking how to do it | Make it a link or add a button |
| Scroll stops before the price | Questions about price early in the chat | Move price information up |
| Booking button ignored | Visitors asking 'can I book online?' | Make the button clearer; the assistant can offer times |
| Rapid back-and-forth clicking | Complaints that a page does not work | Test on the reported device |
| Visitors reach the contact page and leave | Questions about location or parking | Add the details to the page |
Privacy and consent
- Heatmap and recording tools use cookies or similar technologies; get consent where the law requires it.
- Mask form fields and any personal data in recordings.
- Do not record on pages with sensitive information.
- Tell visitors what you collect in your privacy notice.
- Chat transcripts contain what visitors typed: handle them as personal data, limit access and set retention; see GDPR checklist for website chatbots.
If you have no heatmap tool
You can learn a lot without one. Look at your analytics for pages with high exit rates, walk through your website on a phone, and read transcripts. Add a heatmap when you have a specific question that behaviour data would answer. Where a chat assistant is present, the questions people ask on each page are a heatmap of confusion in words; see where and when visitors open the chat.
Common mistakes
- Looking at heatmaps without asking a specific question.
- Ignoring transcripts because there are 'too few'.
- Changing many things at once.
- Recording visitors without consent or masking.
- Treating a heatmap as proof of why.
A worked example
A physiotherapy clinic sees that few visitors reach the booking button on its services page. The scroll map shows most people stop about halfway down, above the button. Twenty chat transcripts from that page contain the same questions: 'How long is a session?', 'Do I need a referral?' and 'Is it covered by insurance?'. The clinic moves a short summary of duration, referral rules and insurance to the top of the page and places the booking button beside it. A month later the scroll map shows more visitors reaching the button, and those three questions almost vanish from the chat. Neither source alone would have told the whole story: the heatmap found the problem area, and the transcripts supplied the fix.
| Evidence | Finding | Action |
|---|---|---|
| Scroll map | Most visitors stop before the button | Move key information and the button up |
| Transcripts | Same three questions repeated | Answer them at the top of the page |
| Follow-up | Fewer repeat questions, more clicks | Keep the change; look at the next page |
This pattern applies to any page that matters: find where behaviour stalls, find what people ask, fix the gap and check again.
Frequently asked questions
Are heatmaps or chat transcripts better?
Neither. Heatmaps show what visitors do, transcripts show what they say and why. Together they find friction faster.
Do I need a heatmap tool?
Not to start. Analytics, a phone walkthrough and chat transcripts already reveal a lot. Add a heatmap for specific questions.
How many transcripts should I read?
About twenty for a page or topic is enough to see patterns.
Is recording visitors legal?
It depends on where you operate. Get consent where required, mask personal data and disclose it in your privacy notice.
What should I fix first?
Missing or buried key information such as price, hours and how to book.
How do I know the fix worked?
Compare the heatmap and the questions people ask before and after.
See the AI assistant feature, the playground and read tracking where chat visitors drop off.
Further reading
- Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.
RISPONDI A OGNI VISITATORE. PRENOTA CHI È PRONTO.
Installa Crescelo sul tuo sito in 15 minuti
Addestra il tuo assistente sui tuoi listini, documenti e condizioni di servizio. Attiva risposte fondate sulle tue fonti 24 ore su 24 e prenotazioni in chat senza sovrapposizioni.