Free live visitor tracker · world map widget

Every blog wants to know 'where in the world are my readers right now?' — and every reader wants to see the same map. This widget answers both. A live world map (3D globe or flat 2D) with animated dots that light up the moment a new visitor lands. Free, no signup, no API key.

Live visitor map widget — animated dots, real-time geolocation

The live visitor map widget plots every active visitor on a 3D globe (or flat 2D world map) the moment their first page-view fires. Dots fade in, pulse for a few seconds, then fade out, so the map feels alive even on slow-traffic pages. The live visitor map widget geolocates from the visitor's IP server-side (no client-side permission prompt, no GDPR consent dialog needed for the embedder) and rounds to city centroid so individual visitors stay anonymous. Works on WordPress, Shopify, Webflow, Ghost, plain HTML. One script tag, no API key, no signup.

World map visitor tracker — what to look at, what to ignore

A world map visitor tracker tells you two things at a glance: geographic reach (am I getting readers in Asia, Europe, South America?) and freshness (is anyone here right now?). The FeedPulse world map visitor tracker is calibrated for both — the dot animation makes 'liveness' obvious, and the country-level click breakdown surfaces 'reach' on hover. What it deliberately does NOT show: precise lat/long (privacy), session length (use real analytics for that), or referrer (out of scope). It's a 30-second visual gut check, not a Mixpanel replacement.

3D globe website widget — when to use the globe vs the flat map

The 3D globe website widget option (?view=globe) is visually striking but expensive on low-end mobile devices — it renders ~5,000 vertices with WebGL. Use the 3D globe website widget on hero sections of marketing pages where impact matters more than throughput, or on portfolio sites where 'wow factor' is part of the brand. For sidebars, footers, or any high-frequency embed location, use the flat-map view (?view=flat) — it's a fraction of the GPU cost and conveys the same data. Both share the same script tag; only the query string changes.