free · no signup
Hotjar installation checker
Check if the Hotjar tracking code is on your site, flag duplicate or render-blocking loads, then confirm recordings with Hotjar's own verification.
Scans the page's HTML in seconds. It also reports every other tracking script it finds.
about Hotjar
Why it breaks quietly.
Hotjar's tracking code sets your site ID (hjid) and loads from static.hotjar.com. It powers session recordings, heatmaps and on-site surveys.
It usually fails in ways that look like quiet traffic. Recordings stop when a plan's session limit is hit, a content security policy blocks Hotjar's connections, or the code only loads after consent most visitors never give.
what the free scan checks
Whether Hotjar is in the page
The scan fetches the page's HTML and matches the vendor's script URL and install snippet.
Whether it blocks rendering
A script tag without async or defer delays the page from painting. Marketing scripts never need to.
Whether it's installed more than once
Duplicate installs usually send every event twice and inflate conversions.
How exposed the page is to blockers
A server-side readiness grade: whether tags load from domains blocklists target, and whether conversions have a server-side path.
It reads the HTML, so tags injected later (inside GTM, for example) don't show up, and it can't see events fire. That's what verification is for.
common failures
How Hotjar goes dark.
A content security policy blocks Hotjar
Hotjar needs its script, asset and websocket domains allowed in your CSP. If any are blocked, the code loads partly or not at all.
Daily session limits are reached
Hotjar plans cap how many sessions are captured per day. Once the cap is hit, recording stops until the next day.
Recordings render unstyled
Hotjar rebuilds pages from your CSS and assets. If those are behind a login, on localhost or blocked to Hotjar, recordings look broken.
The site ID belongs to another site
A copied snippet sends data to another Hotjar site, often one on a different account.
by hand
Check it yourself, step by step.
- 1
In Hotjar, open your site's tracking code settings and run the installation verification against your URL.
- 2
Browse the live site in a private window, then check Recordings for your session.
- 3
In Chrome DevTools, open the console and Network tab and look for blocked requests or CSP errors mentioning hotjar.
- 4
View the page source and confirm hjid matches the site ID shown in Hotjar.
questions
Asked and answered.
Can this check tell me if Hotjar is recording?+
No. The free check reads served HTML and can see whether Hotjar's script is present, duplicated or render-blocking. It cannot see Hotjar loaded through GTM or confirm recordings are captured. TracerKit's Verification tier watches real fires and alerts when a tag goes silent.
Why does Hotjar say my tracking code is not installed?+
The code may be missing from the URL Hotjar checked, blocked by a CSP, loaded only after consent, or using a different site ID.
Does Hotjar slow down my site?+
It loads asynchronously, so it should not block rendering. If this check flags it as render-blocking, the snippet was modified or loaded unusually.
check other tags
Know Hotjar is firing, every hour of every day.
Verification watches each tag on real traffic and emails you the moment one goes silent. 14-day trial, no card.