This guide shows how to add a WordPress live visitor map in about a minute, with no plugin: you paste one snippet into the post or page itself, because it's the most visual widget you have, so it earns a spot in the content rather than the chrome. No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.
The visitor globe shows where your recent visitors are on an animated globe or flat world map. It's the most visual widget in the set, and it suits sites with an international audience, such as travel blogs, online courses, open-source projects and remote-first companies. Locations come from visitors' IP addresses and are shown at country level, never as an exact address.
On WordPress, the right spot is the post or page itself. Because it's eye-catching, it earns a place in the content: an About page, a 'our community' section or the bottom of the home page. Give it enough room to read on a phone, and don't stack it next to other moving elements.
WordPress.org sites you host yourself can use every method on this page. On WordPress.com, adding scripts with a Custom HTML block or a header plugin needs a plan that allows plugins and custom code (the Business plan or above at the time of writing), because lower WordPress.com plans strip script tags. If you're not sure which you have, check whether your dashboard has a Plugins menu.
WP Rocket, W3 Total Cache, LiteSpeed Cache and your host's edge cache all serve a stored copy of your HTML. Until you purge, you'll be looking at the version from before you pasted and assuming the widget is broken. The widget's own data is fetched client-side on every load, so page caching never makes the numbers go stale — it only hides a freshly-added snippet.
Optimisation plugins that concatenate or defer every script can break an async third-party tag by moving it out of order. If the widget renders nothing after a purge, add the script URL to your plugin's JS exclusion list — in WP Rocket that's File Optimization → Excluded JavaScript Files. Nothing else needs changing.
WordPress sanitises script tags typed into a paragraph or the Visual editor tab, silently. The Custom HTML block, the Classic editor's Text tab, and Elementor's HTML widget all pass markup through untouched. If your snippet vanished on save, that's why.
If most of your visitors come from one city, the globe will show one cluster, which says little. IP location also isn't perfect, so the odd visitor can appear in the wrong country.
No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs. Installing a plugin for this would mean another dependency and update cycle just to show one widget.
The post or page itself, because it's the most visual widget you have, so it earns a spot in the content rather than the chrome.
It adds one small script, loaded asynchronously, so it doesn't block your page from rendering. Any third-party script has some cost, so check your page speed before and after adding it. Your caching and optimisation plugins keep working exactly as before — the only thing to remember is to purge the cache after you paste, otherwise you'll be looking at the stored copy of your old HTML.
Elementor: drag in the HTML widget and paste there. Divi: use a Code module. Beaver Builder: use the HTML module. WPBakery: use the Raw HTML element. Any builder with a raw-HTML or code block will render it.
No. Locations are approximate, based on IP address, and shown at country level. No exact address or personal data is displayed.