You measure it. Two free tools cover almost everything a business needs: Google Analytics 4 tells you what people do once they arrive, and Google Search Console tells you how they found you. Set both up properly and you can stop guessing about your website.
We see a surprising number of live Webflow sites with no analytics at all, or with a tag that was pasted in once and never checked again. Both are the same problem in practice. If nobody has confirmed the data is arriving, you do not have analytics, you have a hopeful line of code. If your numbers still look short after a clean setup, that gap is what server-side tracking is meant to close.
This is a walkthrough of how we set it up on the Webflow projects we build, in the order we do it, with the checks we run to make sure it actually works.
For most businesses, two tools are enough. Google Analytics 4 handles behaviour on your site, so sessions, pages, and conversions. Google Search Console handles how Google sees you, so queries, impressions, and indexing problems. Everything else is optional until these two are earning their keep.
The temptation is always to add more. Heatmaps, session recordings, a chat widget with its own tracker, a marketing platform pixel. Each one is another script, another cookie, and another thing to maintain. We start with two and add a third only when someone can say exactly which decision it will inform.
The two tools answer genuinely different questions, which is why you want both. Analytics cannot tell you what someone searched to find you. Search Console cannot tell you what they did after they clicked. Together they cover the whole journey.
Create a web data stream in Analytics, copy the Google tag, and paste it into the head custom code in your Webflow site settings. Because Webflow injects that code on every page, one paste covers the whole site. You do not need to touch individual pages.
In Analytics, Google’s documentation walks through it: go to Admin, then Data Streams, click Add stream, choose Web, then enter the URL of your primary website and a stream name. Enhanced measurement is offered at this point and is worth leaving on for most sites, since it captures scrolls and outbound clicks without extra work.
Google is specific about what to copy. Your Google tag is the entire section of code beginning with the Google tag comment and ending with the closing script tag. Google’s instruction is to paste it immediately after the opening head tag on each page, which in Webflow means the top of the site-wide head code field.
You will also see a measurement ID, which Google notes starts with G- for Analytics properties. Keep that somewhere, because plenty of other tools ask for it later and hunting it down again is a small waste of everyone’s afternoon.
Publish the site, visit it yourself, then open the Realtime report in Analytics. If you appear, it works. Google’s documentation notes that data collection may take up to 30 minutes to begin, and suggests the Realtime report as the way to verify you are receiving data.
That 30 minute window is the reason for most false alarms. Someone publishes, checks immediately, sees nothing, and assumes the setup failed. Wait properly before you start debugging, or you will spend an hour fixing something that was never broken.
The check we never skip is the staging domain. Webflow publishes to a webflow.io subdomain as well as your custom domain, and if your tag runs on both, your own testing quietly pollutes the data. Excluding that traffic at the start is far easier than untangling it a year later.
Add your site as a property and verify ownership. Search Console supports several methods, including an HTML file upload, an HTML meta tag on your homepage, your existing Google Analytics code, Google Tag Manager, or a DNS record with your domain provider.
On Webflow, two of those are easy. The HTML tag method works by pasting the meta tag into your site-wide head code, exactly like the Analytics tag. If you already have Analytics running, the Analytics verification method can work without pasting anything new at all, provided you have edit permission on the property.
Once verified, resist the urge to check it daily. The Performance report defaults to the past three months of data, and Google notes the newest data can be preliminary and may still change over the following hours. Weekly is a sensible rhythm. Our fuller guide to using Search Console to improve your rankings covers what to look at once the data builds up.
A Domain property covers every version of your site at once, across protocols and subdomains. A URL-prefix property covers only the exact address you enter. Domain properties give you the complete picture, which is why we set them up wherever the client controls their DNS.
The catch is that they need DNS verification. Google’s documentation is clear that the DNS record method is required for a Domain property and cannot be replaced by the HTML file upload, which only works for URL-prefix properties. So a Domain property means adding a TXT or CNAME record at your registrar.
If you cannot get DNS access, a URL-prefix property is a reasonable fallback. Just be aware you may need more than one of them to cover the www and non-www versions of your site, and the data will not be combined for you.
Less time than most people assume. For standard Google Analytics 4 properties, user-level and event-level data retention can be set to either 2 months or 14 months. Check which setting your property is on, because it is not one anybody opens unprompted, and the shorter option quietly throws away detail.
This does not wipe out your reporting entirely. Google notes that retention settings affect explorations and funnel reports, while standard aggregated reports are unaffected. So your traffic trends survive, but the ability to dig into a specific cohort from last year does not.
Some data has its own clock regardless of your setting. Google states that a two month retention period is always applied to age, gender, and interest data, and that Google signals data has a maximum retention of 26 months. Changing this is one setting and thirty seconds, and it is the first thing we do on any new property.
Yes, a little, and a lot more if you keep adding them. Every tag is a third-party request the browser has to make to a domain you do not control. One analytics tag is a fair trade. Six marketing tags on a landing page is how a fast build becomes a slow one.
The honest position is that you cannot measure without some cost. What you can do is keep the count low, review it regularly, and remove tags for tools nobody has logged into for six months. That audit finds something almost every time we run it on an inherited site.
We wrote about the mechanics of this in our piece on how third-party scripts slow down your website. The short version is that the damage is rarely one script. It is the accumulation nobody is tracking.
If you have visitors in regions with consent laws, you need a consent banner that actually gates the tags, not one that just appears. A banner that sets cookies before anyone clicks anything is decoration. The tags have to wait for permission before they run.
This is where a lot of Webflow sites get it wrong, because the banner and the analytics tag are usually added by different people at different times and never tested together. The test is simple: load the site in a private window, decline consent, and check whether the analytics tag fired anyway.
Getting this right without wrecking your site is its own subject, and we covered the practical side in our guide to handling cookie consent. Do not treat it as a legal checkbox bolted on at the end. It changes what your data means.
Do Search Console first, then Analytics. Search Console starts collecting the moment you verify and cannot be backfilled, so every day without it is data you will never get. Analytics is the same, but Search Console is quicker to set up and tells you more in the first month.
After both are live, spend twenty minutes on the boring configuration. Set data retention to 14 months, exclude your staging domain and your own office traffic, and confirm at least one real conversion is being recorded. Analytics that tracks pageviews but not enquiries will not answer any question worth asking.
If you have a Webflow site with tags you inherited and are not sure what is firing or whether the numbers can be trusted, we’re happy to take a look. Reach out at phoenix.studio and we’ll tell you what is working, what is redundant, and what is quietly slowing you down.
Tell us where you want to go. We'll tell you how we'd get you there.