Set a Baseline Before You Change Your Cafe Website
You are about to rebuild a few pages, rename your titles, or move your whole site to a new platform, and right now you have no record of how things look today. Short answer: stop and spend one hour writing down your current numbers before you touch anything. Without a before, there is no honest way to say whether a change helped, hurt, or did nothing at all.
This is not a complicated audit. A baseline is a dated snapshot of a handful of numbers you can pull from tools you already have: search impressions and clicks, your top pages, where visitors come from, how many pages are indexed, and a few screenshots of how your site and your Google profile look right now. Write the date on it, save it somewhere it will not vanish, and move on with your changes.
Why a Baseline Matters More Than It Sounds Like It Should
Think of it the way a contractor thinks about a renovation. Nobody tears out a kitchen without a photo of what it looked like first, not because the photo improves the renovation, but because without it there is no way to describe what changed. A cafe website works the same way. If you rewrite your titles, add schema, or switch from one platform to another, and you did not write down your numbers first, any later claim about what worked is a guess dressed up as an observation.
This matters especially for a small cafe site, because the numbers involved are usually small too. A jump from six clicks a week to nine clicks a week can look dramatic on a chart and mean almost nothing, or it can be the first real sign that a change worked. You cannot tell the difference without a starting point recorded on a specific date, because a small site's numbers move around on their own even when nothing changes.
A baseline also protects you from a different kind of mistake: blaming a change for a problem it did not cause. If your impressions drop the week after you update your homepage, it is tempting to assume the update caused it. A baseline that shows your numbers were already unstable before the change gives you the context to know that swings like that happen on their own, and that one bad week is not proof of anything.
None of this requires software you have to buy. It requires an hour, a spreadsheet or even a plain document, and the discipline to do it before you start changing things, not after you notice something looks different.
The Metrics That Belong in a Baseline
Keep the list short enough that you will actually finish it. Six things cover what a small cafe site needs to compare later: search impressions and clicks over a set period, your top performing pages, where your traffic comes from, how many pages are indexed, your Google Business Profile views and actions, and a handful of screenshots.
Impressions and clicks come from Search Console, and the standard window is the last 28 days, since that is the default range the tool opens to and it smooths out day to day noise better than a single day would. Record the total impressions, total clicks, average click through rate, and average position for that window, plus your top 10 queries and top 10 pages by clicks. Write the exact date range next to the numbers, not just the date you pulled them, because 28 days ending today looks different from 28 days ending next month even if nothing changed.
Your top pages and traffic sources usually live in your platform's own analytics, whether that is Wix Analytics, Squarespace Analytics, or something similar. Record which pages get the most visits and which channels send them, search, direct, social, or referral. Indexed page count comes from the Page indexing report in Search Console, which tells you how many of your pages Google has actually indexed versus how many it has seen but excluded, a number worth knowing before you restructure your site and possibly orphan pages you did not mean to remove.
Your Google Business Profile has its own numbers worth a line in the same document: profile views and the count of actions like calls, direction requests, and website clicks, usually available as a recent range inside the profile's own performance view. Round out the baseline with a few screenshots, your homepage, your Google Business Profile as it currently displays, and your top two or three pages, so you have a visual record alongside the numbers.
Why the Clock Matters: Wix Keeps Less Than You Think
One detail changes how urgent this is. Wix retains only 62 days of analytics data. If you wait two months to pull a baseline, the data you would have wanted is already gone. That is a hard limit, not a suggestion, and it is the single best argument for doing this today rather than filing it under someday.
Search Console works differently and keeps performance data on a longer horizon, which is part of why the two tools are worth pulling separately rather than relying on just one. The practical takeaway is simple: export what Wix shows you promptly, because it will not be there to look back on later the way Search Console data will be. If your site is on a different platform, check that platform's own stated retention before assuming your numbers will still be there in three months.
This is also why a baseline is not a one time favor to your future self, it is closer to a monthly habit for anyone making frequent changes. If you are running several rounds of edits over a few weeks, take a fresh snapshot before each round starts, not just once at the very beginning, so each change has its own honest before.
Hillcane's Own Baseline, as a Worked Example
Hillcane's own site is a useful case here, not because it proves anything about what works, but because it shows what a real baseline looks like on a small, brand new site. Hillcane.co launched September 9, 2026. In the first eight days, the site was already showing roughly 124 impressions per day in Search Console, and the first organic clicks appeared on day 7. The first AI referred visits carrying a ChatGPT tag showed up around days 8 to 9. These are small numbers on a small, dated sample, not a benchmark for what any other cafe site should expect, and they are worth stating that way every time they come up.
In the same window, bot traffic made up a real share of total hits, about 2,000 AI related bot hits out of 7,738 total hits in the first 12 days. That is a detail a baseline would have missed entirely if the snapshot had only looked at human visitor counts, and it is exactly the kind of thing that matters once you start comparing before and after.
Hillcane also ran nine separate batches of title, meta description, and schema rewrites across roughly 858 posts in a short span. With that much change landing quickly, a single baseline taken before batch one would already be stale by the time batch nine finished. The honest approach was to treat the baseline as a moving reference point, checked again at intervals, rather than a single snapshot expected to still apply weeks later. If your own site is about to go through a similarly fast run of changes, plan for the same thing: more than one snapshot, not one.
None of these Hillcane numbers say anything about what should happen on your site. They are a dated case on one small, new site, useful for showing what a baseline record looks like in practice, not a target to hit or a promise about your own results.
The One Hour Checklist
Set a timer for an hour and work through this in order. First, open Search Console and record the last 28 days: total impressions, total clicks, click through rate, average position, top 10 queries, and top 10 pages. Second, open your platform's analytics and record your top pages and traffic sources for the same or nearest comparable window. Third, open the Page indexing report and write down how many pages are indexed versus excluded.
Fourth, open your Google Business Profile and record recent views and actions. Fifth, take screenshots of your homepage, your profile as it currently appears, and your top two or three pages. Sixth, put every number into a simple table with four columns: metric, value, date range, and source screen, so anyone reading it later, including you in three months, can see exactly where each figure came from.
Name the file something that will still make sense later, like a plain date and the word baseline, and store it somewhere durable, a shared drive folder or a document outside whatever platform you are about to change, not a screenshot buried in your camera roll. If you are moving platforms entirely, save a copy before the migration starts, since some of these numbers may not transfer with the site.
Finally, write one sentence at the top noting what changes you are about to make and why. That sentence turns a pile of numbers into a real baseline, a record not just of where you started but of what you were about to do differently, which is the whole point of writing any of this down in the first place.
What a Baseline Will Not Tell You
Be honest with yourself about the limits here. A baseline does not predict whether a change will help. It does not prove causation later either, since plenty of things move a small site's numbers besides the change you made, including nothing at all. A noisy small site stays noisy after you take a baseline; the baseline just gives you a documented range to compare against instead of a vague memory of what things used to look like.
That is why a baseline records a range over a set window rather than a single day's numbers. One day's impressions on a small site can bounce around for reasons that have nothing to do with your site at all. Twenty eight days of data smooths that out enough to be useful without pretending to be more precise than a small site's numbers are.
A baseline also will not tell you whether a specific change worked in isolation if you made five changes at once. If you rewrote your titles, added schema, and changed your homepage layout all in the same week, your baseline can tell you what things looked like before all three changes together, but it cannot cleanly separate which one moved the needle, if any did. If you want to judge one change at a time, space your changes out and take a fresh snapshot between each one.
Treat the baseline as the first step in a two part habit, not the whole job. The second half is the later comparison, checking your numbers again on a set schedule after the change, reading them against the same table you built here, and being willing to say plainly that a change did nothing if that is what the numbers show. A baseline you never look at again is just an old spreadsheet. A baseline you compare against later is the only honest way a small cafe site can learn from its own history.
Related Reading
More from Hillcane on this topic, plus the pages on the site that sit next to the work.
Frequently Asked Questions
What exactly should I record in a baseline?
Six things: Search Console impressions and clicks over the last 28 days including top queries and pages, your platform analytics for top pages and traffic sources, your indexed page count from the Page indexing report, your Google Business Profile views and actions, and a handful of dated screenshots of your homepage, profile, and top pages. Put every number in a table with the metric, value, date range, and source screen.
How long does it take to build a baseline?
About an hour for a small cafe site. Most of that time is spent opening the right screens in Search Console, your platform's analytics, and your Google Business Profile, then writing the numbers into a simple table. It is not a technical task and does not require any paid tools, just access to accounts you likely already have.
How long does Wix keep my analytics data?
Wix retains 62 days of analytics data. That is a firm limit, so if you wait longer than two months to pull a baseline, the numbers you wanted may already be gone. This is the main reason to take a snapshot now rather than treating it as something to get to eventually, especially if you are on Wix specifically.
Does Search Console keep data longer than Wix?
Search Console's performance data is retained on a longer window than Wix's 62 day analytics retention, which is part of why it is worth exporting both separately rather than relying on one tool to cover everything. Pull and save your Search Console numbers alongside your platform analytics rather than assuming either will still show the same history months from now.
Should I take one baseline or several?
If you are making one clean change, one baseline before it is usually enough. If you are running several rounds of changes over weeks, like Hillcane's nine batches of title, meta, and schema rewrites across roughly 858 posts, take a fresh snapshot before each round. A single snapshot taken before batch one is already stale by the time batch nine lands.
Will a baseline tell me if my changes are working?
A baseline does not predict or prove that a change worked. It gives you an honest record of where you started so any later comparison is grounded in real numbers instead of memory. A noisy small site will still be noisy after you take a baseline; the baseline just gives that noise a documented starting range instead of leaving it a guess.
What if I already made changes without taking a baseline first?
Take one now. It will not recover the exact before state, but it establishes a clean starting point for judging whatever you do next. Going forward, treat every future change, however small, as a reason to check whether your last snapshot is still recent enough to be useful, and take a new one if it is not.
What did Hillcane's own baseline look like when the site launched?
Hillcane.co launched September 9, 2026. Within the first eight days it was showing roughly 124 impressions per day in Search Console, with first organic clicks appearing on day 7 and first ChatGPT tagged visits around days 8 to 9. About 2,000 of the 7,738 total hits in the first 12 days were AI related bot traffic. These are small, dated numbers from one new site, a case, not a benchmark for any other cafe.
Do I need paid tools to build a baseline?
No. Search Console, your platform's built in analytics such as Wix Analytics or Squarespace Analytics, and your Google Business Profile's own performance view are free and cover everything a baseline needs: the last 28 days of impressions and clicks, top pages, traffic sources, indexed page count, and profile views and actions. Screenshots need nothing beyond your phone or browser, and the whole checklist fits in about an hour.
Where should I store my baseline file?
Somewhere durable and outside the platform you are about to change, such as a shared drive folder or a plain document, not a screenshot buried in your phone's camera roll. Name the file with a clear date so it stays identifiable months later, and keep a copy safe before any platform migration, since some numbers may not carry over automatically.
Work with Hillcane
You are about to rebuild your cafe website and nothing is written down about how it performs today. Spend one hour recording your numbers before you touch anything.
Need help setting up a baseline or reading what it shows you afterward? Reach Hillcane at hillcane.co/contact or call (256) 384-2449.
Comments