Skip to main content
Can AI see it

Know what AI sees. Measure what it's worth.

What is Hotjar?

Direct Answer: Hotjar is a user analytics and feedback tool operated by Hotjar, now part of Contentsquare.

Operator: Hotjar Type: Monitoring Bot Purpose: User experience analytics and feedback collection

Hotjar provides user analytics and feedback tools for website owners, including heatmaps, session replay, funnels, surveys, and user tests. It is operated by Hotjar, which is now part of Contentsquare. The platform helps users understand and improve their website or app experiences.

User-Agent Identification

The following user-agent strings identify Hotjar in your live traffic data:

  • Mozilla/5.0 (iPhone; CPU iPhone OS 11_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Hotjar Version/11.0 Mobile/15E148 Safari/604.1

robots.txt Rules for Hotjar

Respects robots.txt: No

Robots.txt has limited effect on user-initiated bots

Hotjar is triggered by user actions within Hotjar's products. While Hotjar states it respects robots.txt, the bot operates differently from autonomous crawlers — it fetches specific URLs on demand rather than systematically spidering your site. Server-log monitoring is the only reliable way to verify what actually happens.

Need continuous verification across 500+ bots? Can AI See It automates this.

Crawl Behavior

Frequency:Not Documented

Request Pattern:Not Documented

Crawl Activity Index

Relative crawl activity for Hotjar over the past 28 days. Higher values indicate increased crawling intensity compared to the period baseline.

View recent activity data (last 7 days)
Date Activity Index
Mar 28, 2026 42.0
Mar 29, 2026 39.7
Mar 30, 2026 48.5
Mar 31, 2026 52.7
Apr 1, 2026 47.7
Apr 2, 2026 44.6
Apr 3, 2026 29.9

Source: Cloudflare Radar

Why track Hotjar traffic?

Distinguish monitoring traffic from real crawler activity. Hotjar checks your site availability at regular intervals. Without proper identification, these requests can inflate your bot traffic metrics and distort crawl analysis.

Validate monitoring coverage. Track which pages Hotjar checks and how frequently, so your monitoring setup matches your infrastructure requirements.

Log Verification

To verify Hotjar traffic in your live traffic data:

  1. Search access logs for the user-agent strings listed above
  2. Check if the IP addresses match documented ranges (if provided by Hotjar)
  3. Verify the crawl pattern matches documented behavior
  4. Use reverse DNS lookup for additional verification if available

Note: Observed behavior in production environments may differ from official documentation. Live traffic monitoring provides the only reliable verification of actual bot behavior.

Undocumented Information

The following information is not officially documented for Hotjar:

  • crawl frequency
  • IP verification
  • JavaScript rendering
  • request pattern

Official Documentation

View Official Hotjar Documentation →

Information sourced from official documentation. Content generated with AI assistance.