Visitors
Find out if anybody is actually reading it.
Page views, the pages people open, and where they came from — counted as your site is served, so there is nothing to install and nothing a reader can switch off.It is on your dashboard the day you publish.
Nothing to install
No script on your pages, no second account, no separate bill. It is counting before you have asked it to.
Nothing to consent to
No cookie and nothing stored on a reader’s machine, so there is nothing here for a banner to ask about.
Nothing a reader can block
Counted as the page is sent rather than in the browser, so an ad blocker cannot quietly remove a third of your readers.
The problem with the normal kind
Most analytics undercount the smallest sites the most.
The usual tool is a piece of code that runs in the reader’s browser and reports back. An ad blocker stops it. A privacy setting stops it. Somebody who closes the page quickly stops it. The readers it loses are not a random sample of your readers, so the number you are left with is not a smaller version of the truth — it is a differently shaped one.
This counts where the page is sent
Every page of your site is handed over by the same machinery, and that is where the counting happens. There is nothing between you and the number for somebody to switch off — not an extension, not a setting, not a script that failed to load on a bad connection.
A page held in memory still counts
Your pages are built when you publish and then kept ready, which is what makes them fast. That would defeat a count made anywhere further in — the page is sent without the site being asked to think about it — and this sits far enough out to see every one of them.
Robots are told apart, not counted
Search engines, link checkers, feed readers and our own automatic checks of your site are recognised and left out, so your numbers are people. The day we check your site is working is not the day it looks popular.
On your Overview
One card, at the top, with the four things you would act on.
The last 30 days, in your own time zone, the first thing you see when you open the site. Not a dashboard you have to learn — four answers and a chart.
How many, and whether it moved
Page views and roughly how many people, against the same stretch before it, so the number means something on its own. When the previous stretch is too quiet for a comparison to be worth anything, it is left off rather than dressed up — a big percentage off three visitors is noise, not news.
Which pages people read
Your most-read pages in order, each one a link straight to editing it. This is usually the most surprising line on the card and the most useful: the page you spent a fortnight on is often not the page anybody opens.
Where they came from
The sites people arrived from — a search engine, a social post, a directory you are listed in, somebody who wrote about you. Enough to tell which of the things you are doing is doing the work, which is the question behind most of a small marketing budget.
Phone or computer
One line, and often the one that changes what you ask for next. Most local businesses are read on a phone in a car park, and knowing that is what turns “make the homepage nicer” into “put the phone number where a thumb can reach it”.
There is also a line for AI crawlers, counted on their own rather than mixed into your readers or thrown away — more people find a business by asking an assistant every year, and whether those assistants are reading your site is worth knowing before it is obvious.
What is kept
Counts, and nothing about any one person.
The thing that makes most website statistics a privacy question is that they follow individuals about. This does not have anything to follow them with.
No cookie, no fingerprint, no script
Nothing is written to a reader’s machine and nothing runs in their browser. Your pages are exactly what you published — this adds no code to them and does not slow them down by a single byte.
What is stored is totals
How many views a day, which pages, which sites people came from, how many were on a phone. There is no row anywhere for a person, so there is nothing to look up, export, leak or be asked for.
The server log is short-lived
Like every web server, ours records the requests it answers, and that record is kept for 30 days so a counting mistake can be corrected. Nothing from it about any individual is ever carried across into the numbers you see.
What that does not do is settle your own obligations, and we are not going to pretend it can. Whether your site needs a consent banner depends on everything else on it — a booking widget, an embedded map, a chat bubble or a video may each bring requirements of their own. This is one item off that list, and the rest of the list is still yours.
And because the builder can read it too
“Which page gets read most? Put that one first.”
The same numbers are available to the AI while it is editing your site, so the question and the change are one conversation instead of a report you read on Monday and act on in a fortnight.
Questions about visitor numbers
Do I have to install anything?
No, and there is nothing you could install. The counting happens where your pages are handed to the person reading them, which is a place you do not have to touch. No script goes on your pages, no account is opened anywhere else, and there is no separate bill.
Do I need a cookie banner for this?
Nothing is stored on a visitor’s machine, so there is nothing for a banner to ask permission about on our side. What your own site needs overall depends on everything else on it — a booking widget, a map, a chat bubble or a video can each have their own requirements — so this is one thing off that list rather than the whole list.
How is this different from the usual analytics?
The usual kind is a script that runs in the reader’s browser, which means an ad blocker or a privacy setting can stop it — on a small site that quietly removes a large share of the real readers, and the ones it removes are not a random sample. This counts as the page is served, so nothing on the reader’s end can switch it off.
What counts as a page view?
Somebody being sent a page of your site. Robots, crawlers and the automatic checks we run against your site ourselves are all left out, and so is anything that is not a page — the files search engines and feed readers fetch are read by programs, and counting them would make a machine polling your feed look like your best reader.
Why is the visitor number approximate when the page views are not?
Page views are a count of things that happened, so they are exact. Telling two people apart without following anybody around is not exact: a family on one home connection looks like one person, and one person who reads on the sofa and again on the train looks like two. It is shown as an estimate because that is what it is.
How current are the numbers?
Up to an hour behind, and the card says which hour it counted to. There is no live counter ticking over, deliberately — a number that moves while you watch invites you to sit and watch it, and nothing about this hour is a decision you need to make today.
Can I ask the builder about them?
Yes. It can read the same numbers, so “which page gets read most?”, “did anybody find the article I published last week?” and “what should I fix first?” are questions you can simply ask while you are editing the site — and the answer can turn straight into the change.
Is this a full analytics product?
No, and it is not trying to be. There are no funnels, no goals, no segments and no date pickers. It answers how many people came, what they read, where they came from and whether they were on a phone — which is what a small business owner actually does something about. If you need the deep version, add one; your pages are yours and nothing stops you.