What Analytics Does a Cafe Need? The Minimum That Works
A cafe owner has been told, more than once, to look at their numbers. They open a dashboard, or three half connected tools nobody fully set up, and cannot say what any of them actually shows. They run a cafe. They have maybe twenty minutes a week for this, not twenty hours.
Short answer: a cafe needs three views and nothing more to start. Which pages people visit, where they came from, and whether they took one of a handful of actions that actually matter, a phone call, a directions tap, an order click. On Wix, the built in Analytics covers the first two directly. Google Search Console adds a third piece, what people searched to find the site in the first place. Anything beyond these three should wait until they are being read every week for a full month first.
This post gives the setup steps, the weekly routine, and an honest note about a pattern worth knowing: direct traffic in analytics tools does not always mean someone typed the address in by hand.
The Three Views
The first view is pages: which pages on the site people visit. This answers whether the homepage is doing the work, whether a menu page gets looked at, whether a blog post anyone bothered to write is being read by anyone. Without this view, an owner is guessing at what matters on their own site.
The second view is sources: where visitors came from before they landed on the site. A search engine, a social platform, a link from another site, or arriving with no referring source at all, usually labeled direct. This tells an owner which channels are bringing people in, rather than assuming based on where effort was spent, which are not always the same thing.
The third view is actions: whether a visitor did one of a small number of things that matter to a cafe once they land on the site. A phone call placed through a click to call link, a directions tap that opens a map, an order click if the site takes online orders. Pages and sources describe traffic. Actions describe whether that traffic did anything a cafe would care about.
It is worth being honest about why these three, and not some longer list. A cafe website exists to do a small number of jobs: tell someone what the place is, where it is, and how to get there or reach it. Pages, sources and actions map directly onto those jobs. Pages tells you what people are looking at once they arrive. Sources tells you which channel is worth continuing to invest attention in. Actions tells you whether any of it led to something real. Anything beyond these three views is measuring something a cafe with twenty minutes a week rarely has the bandwidth to act on anyway.
Why Three and Not More
It is tempting, once a dashboard is open, to add every report available just because it exists. Scroll depth, session duration, device breakdown, referral chains several steps deep, all of these are real metrics a full analytics platform can show. None of them tell a small cafe anything the three core views above do not already cover more directly.
A metric is only useful if looking at it would change what the owner does next. Session duration on a five page site rarely changes any decision a cafe owner would make. Whether the homepage or the menu page gets more visits, and whether a call button gets clicked, changes something real: what gets updated, what gets promoted, what gets left alone. The test for adding any new metric to the weekly routine should be exactly that, would seeing this number change what I do next week. If the honest answer is no, it does not belong in a twenty minute a week routine yet, however interesting it might look sitting in a dashboard.
Setting Up the Stack
On a Wix site, the first two views, pages and sources, live inside Wix's own built in Analytics, accessible directly from the site dashboard without installing anything separate. This covers traffic overview and traffic sources as its own reports, labeled clearly within the dashboard, and requires no configuration beyond the site simply being live.
Search Console adds the third piece Wix Analytics does not cover on its own: what people typed or searched to find the site, along with how often the site appeared in those results and how often it was clicked. Verifying a site with Search Console, described in Search Console Help's own guidance on ownership verification, connects this data to the same Google account managing the property.
None of this requires a heatmap tool, a paid dashboard, or a tag manager. Those tools solve problems a cafe with twenty minutes a week and a small site does not yet have. The three views above cover pages, sources and search intent, which together answer nearly every practical question a cafe owner has about their own site's traffic.
Saving Data Before It Disappears
Wix Analytics keeps a limited retention window, and data older than that window is not available to look back on once it has aged out. This is a genuinely important detail for any cafe owner who wants to compare this month to six months ago later, since that comparison is only possible if the older data was saved somewhere before it expired.
The practical habit worth building is a monthly export. Once a month, download the traffic overview and traffic sources reports as a spreadsheet and save them somewhere outside Wix itself, a simple folder on a computer or a shared drive works fine. This takes a few minutes and turns a rolling, disappearing window into a permanent record an owner owns.
Search Console does not have the same short retention limit, but it is still worth treating the same way out of habit, since export routines are easier to keep up consistently when they apply to everything rather than only to the tool with the shorter window.
Set a recurring calendar reminder for this rather than trusting memory. The most common reason owners lose months of comparison data is simply forgetting the export happened once and assuming it would keep happening on its own. A reminder that fires on the same day each month, paired with a folder that already exists and is easy to find, turns this from an easy to forget chore into a small, automatic habit that takes only a few minutes once it is set up correctly.
The Weekly Ten Minute Routine
Set aside ten minutes, the same time each week if possible, and check three things in order. First, pages: has anything unusual happened, a page suddenly getting far more or far less traffic than normal. Second, sources: has the mix of where visitors come from shifted noticeably. Third, actions: has the number of calls, direction taps or order clicks moved in either direction.
For a brand new or small site, most weeks will show very little movement worth acting on, and that is completely normal rather than a sign the routine is not working. The purpose of a weekly check on a small site is less about catching dramatic swings, which rarely happen on low traffic, and more about staying familiar enough with the normal shape of the numbers that a genuine change, when it does happen, stands out.
Hillcane's own dashboard offers a dated, small sample example of what this looks like in its first weeks. The site launched September 9, 2026, and by day eight, impressions in Search Console had reached roughly 124 per day, with the first organic click on day seven and the first AI tool tagged visits appearing on days eight and nine. Roughly 2,000 of 7,738 total hits in the first twelve days came from AI bot traffic specifically. These are dated, one site, small sample figures, not a benchmark for what any other cafe's dashboard should show in its own first weeks.
What Direct Traffic Might Actually Mean
One pattern worth flagging honestly, labeled clearly as an observation rather than a formal study: on other sites Thomas has run, direct traffic, the category analytics tools use for visits with no identifiable referring source, appears to include a meaningful share of visits coming from AI assistants that do not carry standard tracking tags when they send someone to a site.
This is an owner reported observation, not a measured finding from Hillcane's own site specifically, and it should be read that way. What it suggests, cautiously, is that direct in an analytics dashboard should not automatically be read as people who typed the address into their browser by hand. Some meaningful portion of that traffic may be arriving by way of an AI tool that simply does not identify itself the way a normal search click or a social link does.
This does not change the weekly routine described above. It simply means an owner glancing at a spike or dip in direct traffic should hold that number a little more loosely than they might have a year or two ago, since the category itself has likely gotten less straightforward to interpret than its plain label suggests.
What To Do Once the Routine Is Solid
After a full month of checking the three views every week, a pattern usually starts to emerge on its own. Maybe one page consistently gets more traffic than any other and deserves a clearer call to action. Maybe one traffic source keeps quietly growing while another has gone flat. Maybe calls happen mostly on weekend afternoons, which says something worth acting on about staffing or phone availability during that window.
This is the point where adding one additional tool, if it genuinely answers a question the current three views cannot, starts to make sense. Not before. A cafe that adds a heatmap tool before it has ever consistently checked its own basic pages and sources reports is buying complexity it has not yet earned the need for. A cafe that has spent a month noticing, for instance, that visitors consistently land on the menu page and leave without clicking anything else, has a specific, answerable question that a more advanced tool might help solve.
The order matters more than the tools themselves. Build the habit first, on the smallest stack that answers the real questions, and let the actual patterns that show up over a month of honest checking decide whether anything more is worth adding. Most cafes, most of the time, will find the three view minimum stack keeps answering what they need to know for far longer than they expected.
The habit itself, ten minutes a week, checked consistently, is worth more than any single additional tool would be added on top of an inconsistent routine. A cafe checking three simple views every week, without fail, ends up with a far better working understanding of its own site than one that installed five tools and opens none of them regularly. Consistency, not complexity, is what makes analytics useful for a small business with limited time to spend on it.
Related Reading
More from Hillcane on this topic, plus the pages on the site that sit next to the work.
Frequently Asked Questions
What analytics does a cafe need?
Three views: which pages people visit, where visitors came from before landing on the site, and whether they took an action that matters, a call, a directions tap, an order click. On Wix, built in Analytics covers the first two directly, and Google Search Console adds what people searched to find the site. Nothing beyond that is needed to start.
Does a cafe need Google Analytics 4 to get started?
Not necessarily. This post describes a minimum stack built from Wix's own Analytics plus Search Console, which together cover pages, sources and search intent. A more advanced tool can be added later once these three are being checked consistently every week for a month, but they are not required for the minimum stack to work.
How long does Wix Analytics keep data?
Wix Analytics keeps data for a limited retention window, meaning older data is not available to look back on indefinitely. The practical fix is a monthly export, saving the traffic overview and traffic sources reports as a spreadsheet outside Wix so an owner has a permanent record rather than relying on a rolling window that eventually drops older data.
How much time should a weekly analytics check take?
About ten minutes, ideally at the same time each week. Check pages first for anything unusually up or down, then sources for a shift in where visitors come from, then actions: calls, direction taps, and order clicks. On a small or new site most weeks show little worth acting on, which is normal. The goal is knowing the usual shape of your numbers well enough that a genuine change stands out when it happens.
What counts as an action worth tracking for a cafe?
Three actions matter most: a phone call placed through a click to call link, a directions tap that opens a map, and an order click if the site takes online orders. Pages and sources describe traffic, while actions show whether that traffic did something a cafe cares about. If calls cluster on weekend afternoons, for example, that pattern says something useful about staffing or phone availability during that window.
How quickly did hillcane.co start showing data?
Quickly, but on a small scale. Hillcane launched September 9, 2026; by day eight, Search Console impressions reached roughly 124 per day, the first organic click arrived on day seven, and the first AI tool tagged visits appeared on days eight and nine. About 2,000 of 7,738 total hits in the first twelve days were AI bot traffic. That is one new site and a small dated sample, not a benchmark.
Does direct traffic always mean someone typed in the web address?
Not necessarily. This post shares an owner reported observation, not a formal study, that direct traffic on other sites appears to include visits from AI assistants that do not carry standard tracking tags. Direct traffic figures should be read a little more loosely than the plain label suggests, since the category has likely gotten harder to interpret cleanly.
Should a cafe use a heatmap tool or paid dashboard right away?
Not as a starting point. Heatmaps, paid dashboards and tag managers solve problems a cafe with twenty minutes a week and a small site does not yet have. The three view minimum stack, pages, sources and actions, answers nearly every practical question most cafes have before any of those tools become worth the added setup.
How does Search Console differ from Wix Analytics for a cafe?
Wix Analytics covers which pages people visited and where they came from. Search Console adds a piece Wix Analytics does not cover on its own, what people actually searched to find the site, along with how often it appeared and was clicked in those results. Together the two cover a fuller picture than either alone.
How can Hillcane help set up a cafe's minimum analytics stack?
Hillcane can walk you through the three view stack: Wix's built in Analytics for pages and sources, Google Search Console verification for search queries, and click tracking for calls, directions, and orders. We can also set up the weekly ten minute routine and a monthly export with a calendar reminder, so older data is saved before it ages out. Reach out at hillcane.co/contact or call (256) 384-2449.
Work with Hillcane
A cafe owner has twenty minutes a week for numbers, not twenty tools. Three views cover it: pages, sources, and whether a visitor took an action that matters.
If your cafe needs a simple analytics routine that actually gets checked every week, reach Hillcane at hillcane.co/contact or call (256) 384-2449.
Comments