How to measure whether a website is working, after 30 days
·3 min read·By Tovanin
Visits are not results. The four numbers a small business should watch after launch, where each one lives in GA4 and Search Console, and what to do when one is flat.
A website is working when the action it was built for happens, and you can count it. Everything else is context. This is the measurement setup we put on every site we build and every product we run, and the four numbers we look at with a client thirty days after launch. None of it needs a paid tool.
Decide what a result is before you look at any chart
For most small businesses the result is a lead: a form sent, a call booked, a WhatsApp conversation started, a purchase made. Name it, and make sure the site records it as an event the moment it happens. On this site the result is a contact form submission, and it is counted on the server when the message is stored, not when a button is clicked, so a double click or a failed send does not inflate the number. Google's documentation on GA4 events explains how to define one; the important part is choosing it before launch rather than after.
The four numbers and where they live
| Number | Where | What it tells you |
|---|---|---|
| Results (leads, purchases) | GA4 key events, plus your own database | Whether the site does its job |
| Impressions and clicks | Search Console, Performance report | Whether search is finding you |
| Visits by source | GA4, Traffic acquisition | Which channel brings people who convert |
| Errors and speed | Cloud logs, Core Web Vitals | Whether something is silently broken |
Keep your own count of results outside analytics too. Analytics scripts are blocked by some browsers and skipped by some visitors; your database is not. On the products this studio runs, the number of leads or purchases in Firestore is the number we trust, and GA4 is the tool that explains where they came from. When the two disagree, the database wins.
Set the measurement up on launch day
Everything above depends on a setup that takes a few hours and is skipped by most quotes. The GA4 property and the Search Console property are created in the business's own Google account, with the studio added as a user. The sitemap is submitted the day the site goes live. The one action that counts as a result is registered as a key event in GA4 and, separately, written to your database with a timestamp. Cloud logging is switched on so a failed form send shows up somewhere. And a short note records where each of these lives and who has access, so nobody has to remember it in six months.
We do this on every site we build because we do it on every product we run. Without it, the day 30 conversation is a set of opinions. With it, it is four numbers and a short list of things to change.
What to do at day 30
Sit down with the four numbers and ask one question about each. Results: is the count above zero, and what did those people do before converting? Search Console: which queries show impressions with few clicks, and does the page title answer them? Sources: is any channel bringing visitors who never convert, and should you stop paying for it? Errors: has anything failed that nobody noticed? Thirty days is early for search, so weak impressions are expected; a zero result count with real traffic is the one that needs action.
Common ways the numbers lie
- Counting a click on "Send" instead of a stored message. Failed submissions look like successes.
- Reading total visits. Bots and your own team inflate them; results do not.
- Comparing this week to last week. Small sites are noisy; compare months, or compare against the same period last year once you have one.
- Trusting a dashboard the studio controls. Insist on access to the raw GA4 property and Search Console in your own account.
Speed is a result too
A site that takes four seconds to become usable on a phone loses the visitor before they see the form. Google publishes the Core Web Vitals thresholds it considers good, and Search Console reports them per page. We check them on launch day and again at day 30, because content and images added after launch are the usual reason a fast site becomes a slow one.
If your site is live and you are not sure what it is producing, the fastest route is to send us the GA4 and Search Console access for an hour and we will tell you what the four numbers say. That readout is part of every website and SEO project we deliver, and it is how we run the products in our portfolio. You can ask for one on its own.
Deciding on a website, SEO or automation project? Write a few lines and we will tell you what fits.
Contact Tovanin