Webflow · free forever · no signup

Add a free hit counter to Webflow

This guide shows how to add a Webflow hit counter in about a minute, with no app: you paste one snippet into Site settings → Custom code → Footer code, because an all-time total is a footer artefact — nobody scrolls up to check it. Nothing to install. Webflow renders raw HTML and script tags inside a Code Embed element, so no third-party app sits between you and the widget.

What this Webflow hit counter shows

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.

How to add a hit counter to Webflow

  1. 1Go to Site settings → Custom code and scroll to Footer code.
  2. 2Paste the snippet there — it lands before the closing </body> tag on every page.
  3. 3Save changes and Publish.
  4. 4Footer is the right slot for anything script-based: it keeps the tag out of the critical path on every page at once.
On a free webflow.io staging site? Each custom code field caps at 50,000 characters. You are nowhere near that with one snippet, but if you're already at the limit, host the script externally and reference it by URL.

Where it works best on a Webflow site

On Webflow, the right spot is Site settings → Custom code → Footer code. 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.

Webflow plan and editor requirements

Webflow's Code Embed element and its site-wide and page-level custom code fields only run on a paid Site plan or a paid Workspace. On a free webflow.io staging site the fields are visible but the code doesn't run on the published page, which looks exactly like a broken snippet. Custom code also doesn't run inside the Designer, so always test on the published site.

Three things that trip people up on Webflow

Custom code fields need a paid plan

Site settings → Custom code and the page-level code fields are gated behind a paid Site plan or a paid Workspace. On a free webflow.io staging project they're visible but inert, which looks exactly like a broken snippet. The Code Embed element has no such gate, so free projects are not locked out — put the snippet on the canvas instead.

The Designer never runs your code

A Code Embed shows a grey placeholder in the Designer, and site-level code doesn't execute on the canvas at all. Preview is unreliable for third-party scripts too. Publish, then check the live domain in a normal tab. Most 'the widget doesn't work on Webflow' reports are an unpublished change.

Don't add a second jQuery, and watch the 50k cap

Webflow already loads its own jQuery; importing another version breaks interactions site-wide. Our snippet has no jQuery dependency, so nothing to do here — but if you're pasting several third-party tags, that's the usual culprit. Each code field also caps at 50,000 characters; past that, host the file externally and link it.

Honest limits

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.

What you get, and what it costs

  • Free forever — there is no paid tier, no trial and no card
  • No signup for the badge-style widgets; the live ones create a site ID inline from your URL
  • Async script — it never blocks your page from rendering
  • Works in the Designer, in page-level and site-level custom code, and inside CMS Collection page templates
  • Bots filtered server-side on every visitor-counting widget

Webflow questions

Do I need an app to add a hit counter to Webflow?

Nothing to install. Webflow renders raw HTML and script tags inside a Code Embed element, so no third-party app sits between you and the widget. Installing an app for this would mean another dependency and update cycle just to show one widget.

Where exactly does the snippet go on Webflow?

Site settings → Custom code → Footer code, because an all-time total is a footer artefact — nobody scrolls up to check it.

Will it slow my Webflow site down?

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. Webflow serves your site from its own CDN and the snippet is a single async tag, so it loads beside your content rather than in front of it. Put JavaScript in Footer code rather than Head code when you don't need it early — Webflow recommends the same thing. Nothing to purge; publishing replaces the page.

Does it work with page builders like Webflow Designer?

Webflow Designer: Add (+) → Code Embed. Page settings: paste inside the <head> tag or before </body> for one page. Site settings: Custom code → Head or Footer for every page. CMS Collection templates: drop a Code Embed into the template. Any builder with a raw-HTML or code block will render it.

Does the hit counter count bots?

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.