How to track visitors on Webflow.
Webflow keeps site-wide scripts in Site settings. Save the snippet, publish to the domain your visitors use, and verify a test visit in VisitorPing.
What you need
- • A Webflow site with an active Site plan or a Core, Growth, Agency, or Freelancer Workspace plan that enables custom code.
- • Access to Site settings and permission to publish.
- • A VisitorPing site key, in the form vp_ABC23456 — the prefix vp_ and eight characters. The alphabet leaves out I, O, 0 and 1, so there is nothing to misread when copying it.
Install it
- 1
Open custom code
From your Webflow dashboard open Site settings → Custom code.
- 2
Paste into Head Code
Put the tag in the Head Code section with your own key in place of vp_ABC23456, then Save Changes.
<script defer crossorigin="anonymous" src="https://cdn.visitorping.com/site/vp_ABC23456.js"></script> - 3
Publish to your live domain
Publish with your live domain selected. Custom code only reaches domains you publish to. Open the live site in a private window, complete any required consent, and confirm the test visit in VisitorPing.
Staging and live can disagree
Webflow publishes per domain. It is easy to publish to the webflow.io staging address, see the tracking working, and leave the customer-facing domain without it.
If visits appear from your staging domain but not your real one, that is what happened — publish again with your live domain selected.
What you will actually see
Per visit: the city and region the network resolves to, where the visitor came from, the page they landed on, their device and browser, and whether they have been before.
You do not get a name, an email address, or an identity. Nobody can give you that from a page view, whatever the marketing says. Geolocation resolves a network rather than a doorstep, so a visitor on a VPN or a mobile network can appear in the wrong city entirely. Treat location as a hint.
You are collecting visitor data, so say so in your privacy notice and check which consent rules apply where your customers are — a question for your own legal advice, not for a setup guide.
If it is not working
- Custom Code is greyed out
- An active Site plan or an eligible Core, Growth, Agency, or Freelancer Workspace plan enables custom code. Check your plan and site permissions.
- Changes are saved but not live
- Saving custom code does not publish it. Publish the site afterwards.
Find what is costing you search clicks, then watch the fix work.
VisitorPing reads your own Search Console data for the pages losing clicks, then rings your phone the moment someone lands on your website.