Hotjar for Landing Pages: What It Actually Shows You and When to Use It

Most people install Hotjar, watch ten session recordings, get bored, and forget about it. Then six months later they cancel because "we never use it."

That's a workflow problem, not a tool problem. Hotjar on a landing page is useful for about four specific questions. If you're asking those questions, it's worth it. If you're not, skip it.

This tutorial walks through what each Hotjar feature actually shows you on a landing page, how to set it up so you get answers in under an hour, and when a different tool would serve you better.

What Hotjar shows you (and what it doesn't)

Hotjar has four things worth using on a landing page: heatmaps, session recordings, surveys, and feedback widgets. Funnels and form analytics exist too, but on a single landing page they're overkill.

Here's what each one actually reveals.

Heatmaps

A heatmap aggregates clicks, mouse movement, and scroll depth across all visitors. On a landing page, you mainly care about two of the three:

• Click maps show where people are clicking. This includes rage clicks on things that aren't buttons (an image, a headline, a stat).
• Scroll maps show how far down the page people get before bouncing. You'll see a sharp drop somewhere, usually right after a section that didn't earn the next scroll.

Move maps (mouse movement) are mostly noise. There's weak correlation between where the cursor goes and where the eye goes. Don't make decisions based on them.

What heatmaps don't show: why people clicked, what they expected to happen, or whether the click led to anything useful. They show the what, not the why.

Session recordings

Recordings replay individual visitor sessions. You watch someone arrive, scroll, hover, click, scroll back up, and either convert or leave.

On a landing page, recordings answer questions heatmaps can't:

• Are people pausing on the pricing section or scrolling past it?
• Do they click the CTA, then come back and read more?
• Are they trying to click something that isn't clickable?
• Does the mobile layout break in a specific browser?

Watching ten recordings of people who didn't convert will teach you more about your page than a week of analytics dashboards. I'm serious. Block 30 minutes, watch ten, take notes.

Surveys and feedback widgets

The on-page survey is the most underused Hotjar feature. You can fire a one-question popup after a visitor has been on the page for 30 seconds, or when they're about to leave.

The two questions worth asking:

1. "What's stopping you from signing up today?" (exit intent)
2. "What were you hoping to find on this page?" (after 20-30 seconds)

You'll get raw qualitative input that no analytics tool can give you. Five honest answers will reshape your copy more than any A/B test.

When Hotjar is the right tool

Use Hotjar on a landing page when:

You have a conversion problem and no theory about why. Heatmaps and recordings give you hypotheses to test. Without a hypothesis, A/B testing is just guessing with extra steps. Here's how to A/B test without burning traffic on bad hypotheses.

You just launched and want to see how real visitors behave. First-week recordings catch broken layouts, confusing copy, and dead clicks you'd never notice yourself.

You're trying to figure out where people drop off. Scroll maps plus recordings tell you which section kills the page. Could be a confusing headline, a heavy image that loads slow, or a testimonial section that makes people bounce. More on diagnosing above-the-fold problems here.

You want qualitative input without running user interviews. Surveys do this cheaply.

When Hotjar is the wrong tool

Skip Hotjar (or pick something else) if:

You have very low traffic. With under 200 visitors a week, heatmaps don't have enough data to be meaningful, and you'll watch the same five recordings on loop. Spend that energy on copy instead.

You need long-term recording retention. Hotjar's retention windows are tight on lower tiers. Check Hotjar's pricing page for current limits. If you need to look back at sessions from months ago, look elsewhere.

You want session search by user attributes. Fullstory and Mouseflow are stronger here. See the Hotjar vs Fullstory vs Smartlook comparison for which fits your use case.

You're cost-sensitive and only need heatmaps. There are cheaper or free alternatives if recordings aren't your priority.

How to set up Hotjar on a landing page in 30 minutes

Here's the actual workflow. Don't skip steps.

Step 1: Install the tracking code

Drop the Hotjar script into your site head. Most landing page builders have a dedicated integration field. If you're on a custom build, paste it before the closing </head> tag.

Verify it's firing by opening your page and checking the Hotjar dashboard for live activity. If nothing shows up after a refresh, your CSP or ad blocker is probably blocking it.

Step 2: Create a heatmap for your landing page URL

In Hotjar, create a new heatmap and target the exact URL of your landing page. Use the exact match option, not "contains," so query strings from ad campaigns don't fragment your data.

Set it to collect at least 1,000 page views before you draw conclusions. With less than that, the patterns aren't reliable.

Step 3: Set up recordings with smart filters

Don't record everything. You'll drown in junk sessions. Filter to:

• Sessions where the visitor was on the page at least 10 seconds
• Sessions from your landing page URL only
• Exclude your own IP

Once you have 50+ recordings, sort by session duration descending. The longest sessions usually contain the most signal: people who engaged but didn't convert.

Step 4: Add one survey

Pick one question. I'd start with the exit-intent question: "What stopped you from signing up?"

Open-ended, single question, fires once per visitor. Don't make it a five-question feedback form. Nobody fills those out.

Step 5: Wait for data, then sit down for an analysis session

Give it a week. Then block 60 minutes and do this in order:

1. Look at the scroll map. Find the first big drop. That's your weak section.
2. Look at the click map. Find clicks on non-clickable elements. Those are missed expectations.
3. Watch 10 recordings, filtered to non-converters. Take notes on hesitations, scrollbacks, and rage clicks.
4. Read every survey response.

By the end, you'll have a list of five to ten specific problems. Pick the two most common and fix those first.

What to do with what you find

Hotjar surfaces problems. It doesn't fix them. The fixes usually fall into a few buckets:

• Copy that doesn't match visitor intent. Survey responses will tell you this directly. Rewrite the headline and subhead.
• A CTA that gets clicked but not converted. Recordings show people clicking, then leaving the next page. The problem is probably the form or the price reveal, not the CTA itself. Here's how to fix CTA drop-off.
• A section that kills scroll depth. Cut it or move it below the next CTA.
• Mobile layout breaks. Recordings filtered by device will show you exactly what's going wrong.

Once you have your fixes, run them as an A/B test. Don't just push the change live and hope. The step-by-step A/B testing guide covers how to do this without polluting your data.

The honest summary

Hotjar is a diagnostic tool, not a dashboard you check daily. Install it when you have a question. Use it to find the answer. Then stop opening it until you have another question.

If you treat it as a weekly habit, you'll churn out of frustration. If you treat it as a focused two-hour session every time you redesign or relaunch, it pays for itself.

---

Want to skip the Hotjar setup and get conversion-killing issues flagged automatically? PagePulse analyzes your landing page and tells you what's hurting conversions: weak headlines, confusing CTAs, scroll-killing sections, the exact things you'd find watching 50 Hotjar recordings. Paste your URL, get a report in under a minute.