This guide shows how to add a WordPress hit counter in about a minute, with no plugin: you paste one snippet into a footer widget area, because an all-time total is a footer artefact — nobody scrolls up to check it. No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.
The hit counter shows a running total of visits, the classic counter from the early web rebuilt with modern styles. It counts real page loads and filters known bots on the server, so the number isn't padded by crawlers. It suits personal sites, blogs and hobby projects where a visible total is part of the charm.
On WordPress, the right spot is a footer widget area. An all-time total is something people glance at, not something they look for, so the footer is the right home for it. Pick a theme that matches your site; louder themes suit personal pages, while plainer ones fit business sites.
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.
A visit total says nothing about who visited or whether they stayed. For decisions about your site, use your analytics; the hit counter is for showing a number, not analysing one.
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.
A footer widget area, because an all-time total is a footer artefact — nobody scrolls up to check it.
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.
Known bots and crawlers are filtered out on the server before a visit is counted, so the total reflects real browsers as closely as we can make it.