Product Tour: Website Monitoring and Visitor Analytics

First: does the site answer correctly, and do you hear about it when it does not? Then: how do visitors move through it? The walkthrough recording will run on a test site with scripted visits. The screenshots below come from the owner's own live website, with visitor IPs, domains and accounts redacted.

Version: release 81fce3de6 (2026-11-03)Plan: monitoring: Free; analytics, heatmaps, replay, rules: PersonalTest date: walkthrough not recorded yetEnvironment: planned: demo test server, test site, scripted visitsMaterial: screenshots: live site, redacted (2026-11-04); recording pending

Walkthrough

  1. Add an HTTP check for the test site with an expected status code and a keyword that must appear on the page.
  2. Break the page on purpose. After three consecutive failures the check is marked down and an alert is sent; after the fix, a recovery notice follows.
  3. Turn on analytics for the test site (or create a standalone property and paste its script snippet into a page).
  4. Generate visits with a script, then read page views, sessions, top pages, referrers and the real-time view.
  5. Enable heatmap and session replay for this test site only, add masking selectors for the form fields, and review a replay.
  6. Add a rate-limit or GeoIP rule and watch the matching test requests get blocked.

Screens from a live website

Read-only captures from the owner's own production site: real traffic, so visitor IPs, reverse DNS, domains and accounts are boxed out. The heatmap and replay were recorded only for a few minutes, and the visit they show is our own.

Health monitor list: one HTTP check every 60 seconds with 100% availability over 24 hours, status OK and a self-healing action attached; name, target and owner redacted
An HTTP check with its 24-hour availability and an optional self-healing action that runs on failure. Screenshot from a live website (the owner's own site, used with permission), 2026-11-04. Monitor name, target and owner are irreversibly redacted.
Website analytics overview for the last 7 days: page views, unique visitors, IPs, sessions and bounces, with a daily trend chart and dashed previous-period comparison
Seven-day overview of a real website: totals, daily trend and the previous period as a dashed line. Screenshot from a live website (the owner's own site, used with permission), 2026-11-04. Domain and accounts are irreversibly redacted.
Visit details list: time, visitor IP (redacted), country / city, ISP, connection type, reverse DNS and host (redacted) and the requested path for each page view
Every page view with location, ISP and path; searchable by IP, path, host or city. Screenshot from a live website (the owner's own site, used with permission), 2026-11-04. Visitor IPs, reverse DNS and the site domain are irreversibly redacted.
Click heatmap of a home page: the page is rebuilt from a snapshot and warm spots mark where clicks landed; 9 clicks and 10 scrolls over the last 7 days
Heatmap: clicks drawn over a rebuilt copy of the page. Off by default; switched on per site. Screenshot from a live website (the owner's own site, used with permission), 2026-11-05. The clicks come from our own test visit; the site logo is redacted.
Session replay player: a recorded visit to the home page paused mid-way, with the visitor's cursor, a timeline and playback speed controls
Session replay of one visit: cursor, scrolling and clicks, played back in the panel. Off by default; mask form fields before you enable it. Screenshot from a live website (the owner's own site, used with permission), 2026-11-05. The replay is our own test visit; site logo and domain are redacted.

Test record

Test record
Product versionrelease 81fce3de6
Statusnot recorded yet
Datatest site and scripted visits only; masking selectors are shown on screen
Manual interventionto be stated with the recording
Limits and prerequisites
  • JS analytics counts browsers that run the script; it is not the server’s total traffic.
  • Heatmaps and replay are off by default per site. Replay masks only password fields by default — other fields need your own selectors.
  • Country and city come from IP geolocation, which is an estimate, not a precise location or identity.
  • Probing from several regions needs Business (sync groups).

Read more: Monitoring & analytics · Connectivity monitor docs · Analytics docs

The sandbox is invite-only and not open yet; there is no public live demo. Please do not send passwords, keys or customer data with a request.

N Nodekeeper

All-in-one Linux server management agent.

Support
[email protected] WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.