Simple Website Analytics for a One-Person Site
Home › AI Workflows › Simple Website Analytics for a One-Person Site
Most analytics dashboards are built to make you feel busy, not to help you decide anything. For a solo operator, that's a trap: you open a wall of charts, watch the pageview line wiggle, and learn nothing you can act on. The fix isn't a bigger dashboard — it's simple website analytics pointed at the two or three numbers that actually change what you publish next. We run a one-person site and track a deliberately short list. Here's what's worth measuring, what's safe to ignore, and the free, privacy-friendly stack that covers all of it.
Vanity metrics vs the numbers that change a decision
Start by separating the metrics that flatter you from the ones that inform you. Raw pageviews and total sessions are vanity numbers — they go up when you publish and feel good, but on their own they don't tell you what to do differently. The metrics that earn a place on a solo dashboard are the ones tied to a decision: which pages bring people in, what they searched to find you, whether they stay or bounce, and which posts actually lead somewhere. A good test for any metric is simple — if the number doubled or halved, would you do something different? If not, it's decoration. That single question quietly removes about three-quarters of what a default analytics view shows you.
GA4 vs privacy-first: the honest tradeoff
The default instinct is to install Google Analytics 4 and move on, but for a small site it's worth a second look. GA4 is free and powerful, but it's heavy, it leans on cookie consent, and — the part that bites small sites — it applies data thresholding (hiding low-count rows for privacy) and filtering, so low-traffic reports can be meaningfully incomplete. Several EU regulators have also challenged Google Analytics on privacy grounds, which is why a wave of lightweight, cookieless alternatives has matured. They typically ship a script under 5 KB, skip the cookie banner entirely, and show you a single clean screen instead of a configuration maze.
| Tool | Cost | Best for |
|---|---|---|
| Google Analytics 4 | $0 | Deep segmentation — if you'll actually use it; heavy, cookie-consent, sampling on small sites |
| Plausible / Fathom | ~$9–14/month | Zero-setup, cookieless, GDPR-clean — a single readable screen |
| Umami (self-hosted) | $0 software (+~$5/mo server) | Full control on a small server, if you're comfortable with Docker |
For most one-person sites the honest pick is a cookieless analytics tool — hosted (Plausible, Fathom) if you'd rather pay a few dollars than maintain anything, or self-hosted (Umami) if you already run a small server and want the software free. A quietly important perk for a small site: these tools make it trivial to exclude your own visits and they filter bot and referral spam by default — when your real traffic is small, a few bot hits or your own refreshes can badly distort the numbers, so clean counts matter more, not less, at low volume. The same open-source-over-paid logic applies here: pick the lightest option that answers your real questions, and don't install a heavyweight you'll never fully use.
The free baseline every site needs: Search Console
Whatever traffic tool you choose, there's one free source you should not skip, because it answers a question analytics can't: what people searched to reach you. Google Search Console shows the actual queries that surfaced your pages, your average position for each, and your click-through rate — the raw material for deciding what to write and what to improve. Analytics tells you what happened on your site; Search Console tells you how people found it, which for a content site is often the more actionable half. It costs nothing, it's first-party Google data, and it's the closest thing to a free editorial roadmap a solo blogger gets. If you install only one thing this week, install this.
Simple website analytics is a short list, not a wall of charts
With the tools chosen, the discipline is restraint. A one-person dashboard should fit on one screen. Concretely, the five numbers worth a weekly glance are:
- Top pages — which posts actually pull traffic (where to double down).
- Rising search queries (Search Console) — what people increasingly find you for (what to write next).
- Top sources — search vs social vs referral (where your audience really comes from).
- Bounce / engagement on your best pages — do they stay or leave instantly.
- One conversion — an email signup, a click, a download — the single action that means the page worked.
That's it. The relevance filter here is the same one that governs a good tool-choice framework: start from the decision you need to make, then keep only the numbers that inform it. Everything else is noise dressed up as insight. Reviewing five real numbers once a week beats staring at fifty every day — and it's the difference between analytics that guide your next post and analytics that just consume the time you meant to spend writing it.
What we actually run
For transparency: our measurement stack is deliberately boring. Search Console for the queries and positions that tell us what to write next, one lightweight cookieless analytics tool for traffic and top pages, and a short weekly check — not a daily one — against a five-line list rather than a sprawling dashboard. We treat the numbers the same way we treat any AI output: as input to verify, not gospel to obey, the same task-first discipline we apply across the whole operation. Two honest limits keep it grounded. First, a new site has so little traffic that early numbers are mostly noise — don't over-read ten visitors, and don't redesign around a single good day. Second, no analytics tool counts perfectly; treat every figure as directional, not exact. The point of measuring isn't a prettier chart — it's one better decision a week about what to publish, the engine behind running a lean one-person operation.
Bottom line
Simple website analytics for a one-person site comes down to three cheap parts: Search Console for the searches that bring people in, one lightweight cookieless tool for traffic and top pages, and a short weekly review against a five-number list. Skip the vanity metrics, skip the heavyweight dashboard you'll never fully use, and judge every number by one question — if it changed, would you act differently? Measure the few things that move a decision, ignore the rest, and your analytics stop being a time sink and start earning their place in the stack.
Related — more on AI workflows & systems:
- Building a One-Person AI Office: A Realistic System
- One Video, Six Channels: A Content Repurposing Workflow
- Building a Personal AI Knowledge Base That Compounds
- A Free Trend Radar: RSS + AI for Spotting What's Next
Tools, pricing, and privacy rulings current as of June 2026; platforms and regulations change — verify before relying on them. This is the measurement setup we run for our own site, not a vendor pitch.
About the author: AI Stack Lab is written by a solo operator running a one-person business entirely on AI tooling, sharing tested, budget-real workflows rather than vendor hype.
Comments
Post a Comment