Measure what you will act on, and nothing else

The numbers that change decisions

How many people came. Which pages they landed on. Which searches brought them. How many got as far as the contact form.

That is nearly the whole list for a small business. Those four tell you whether the site is working and which page to improve next.

Everything beyond them is interesting rather than useful, and interesting data still has to be explained in your privacy policy.

Notice what is not on that list: bounce rate, session duration, and most of what a default dashboard puts at the top. They are interesting and they almost never change a decision a small business makes.

• How many people came
• Which pages they landed on
• Which searches brought them
• How many reached the contact form
• How many actually sent it
• Which pages nobody ever opens

Where the detail comes from

A standard analytics tag watches sessions in the browser. It builds a picture of a returning visitor over time, which is why it usually needs a cookie and therefore consent.

It also hands the data to another company, which is a third party you now have to name.

None of that is wrong. It is simply a large amount of machinery for four numbers.

Counting on the server instead

Your server already records every request. Counting those gives page views, landing pages and rough traffic patterns without adding anything to the browser.

No cookie, no consent question, no third party, and no script slowing the page down.

What you give up is the cross visit picture of an individual. For most local businesses that was never the question anyway.

It is also immune to ad blockers, which on some audiences suppress a third of browser-based measurement and make every trend you read a trend about blocking rather than about visitors.

The search side is separate

Which searches bring people is not analytics, it is Search Console, and it comes from the search engine rather than from your visitors.

That is the most useful data most small sites have, and it needs no tracking at all.

Connect it, look at it once a month, and you have the one number that tells you what people actually want from you.

That is the more useful instrument for most small sites, and it is covered in the search performance report.

If you keep a full analytics tag

Turn off what you will not use. Shorten the retention period. Turn on address anonymisation if the tool offers it.

Load it only after consent, and mean it, so that declining actually stops the script rather than hiding the banner.

Name the provider in your privacy policy and say what they receive. A visitor cannot judge what they agreed to otherwise.

Reading the numbers honestly

Consent rates mean analytics now shows a partial picture on almost every site. A drop in reported visits can be a drop in consent rather than a drop in people.

So compare like with like, and be careful about small changes. A month with nine visitors and a month with eleven is the same month.

Server counts avoid this problem because there is nothing to decline.

What our pages do by default

Nothing is added to a visitor's browser unless you choose to add it. Visits are counted on the server, and your own analytics tag is optional and loads only after consent.

Every page passes a check that runs before anything publishes, validated against Google Search Essentials and modern web standards, and the in-app assistant tells you what a page loads.

Nothing here is legal advice. The general rule holds anyway: collect what you will act on, and explain what you collect.

If you do add a tag, name the provider in your policy and say what they receive, which is the inventory described in what your website collects.