Dev.to WebDev 🛠 Dev Sun, 08 Nov 2026 12:41:54 +0000 👁 0 📖 4 min read

7 privacy-friendly analytics tools, and what each one can (and can't) tell you about search traffic

Plenty of developers have swapped heavyweight analytics scripts for lightweight, privacy-focused alternatives. Smaller scripts, often no cookies, sometimes no consent banner needed (check with your own legal advice, as r

Then someone asks "how's our organic traffic doing?" and you discover that some of these tools see search engines very differently from what you were used to.

Here's a look at seven options through an SEO lens: what they can tell you about search, and where you'll need something else. Features change, so check each project's current docs before you decide.

First: what any analytics tool can and can't know about search

A few limits apply to all of them:

Search queries are mostly not visible. Search engines generally don't pass the query to your site in the referrer. Query data comes from the search engines' own tools, like Google Search Console and Bing Webmaster Tools.
The referrer is often all you get. Analytics tools typically classify a visit as "from Google" by looking at the referrer domain. Browser referrer policies limit this to the domain in most cases.
Blocked scripts are invisible. Any client-side script can be blocked by browser extensions. Server-side and log-based tools avoid that, with their own trade-offs.

So the realistic job for analytics in SEO is: which pages do search visitors land on, and what do they do next? Queries, impressions and rankings come from search engine tools.

1. Plausible Analytics

Open source (self-hostable) with a hosted option. A small script, cookie-free by design.

For SEO: shows referrer sources, so search engine traffic is visible as its own source, with entry pages per source. It also offers an integration with Google Search Console to show search queries in the same dashboard, pulling the data from Search Console rather than guessing.

Watch out for: goals and funnels are simpler than in heavyweight tools, by design.

2. Umami

Open source and self-hostable, also available hosted. Lightweight, cookie-free.

For SEO: referrers, landing pages and UTM parameters, with filters to combine them, such as "entry pages for visits from google". Self-hosting means the data sits in your own database, which is handy if you want to query it with SQL.

Watch out for: you run the server and database if self-hosting, including upgrades and backups.

3. GoatCounter

Open source, minimal, with a hosted option that's free for non-commercial use (check current terms). Can work without JavaScript via a tracking pixel, or by importing server logs.

For SEO: referrers and pages, kept deliberately simple. The log import is interesting for developers who want numbers that don't depend on a client-side script.

Watch out for: intentionally minimal; if you want segmentation, look elsewhere.

4. Matomo

Open source and self-hostable, plus a cloud version. Much more feature-rich than the others, and can be configured to run without cookies.

For SEO: channel reports including search engines, landing pages, and goals and conversions per channel. Can import server logs. There are plugins for search engine keyword data via Search Console integration.

Watch out for: heavier to run and configure. Privacy depends on how you set it up; the defaults aren't necessarily the most private options.

5. Fathom Analytics

Commercial, hosted, privacy-focused. A small script and a simple dashboard.

For SEO: referrers and landing pages, with search engines visible as sources. Good for a quick "are search visits going up?" view.

Watch out for: not self-hostable, and a paid service. Detailed segmentation is limited by design.

6. Cloudflare Web Analytics

Free for sites, with a small JavaScript beacon, and doesn't need your site to be proxied through Cloudflare. If your site is proxied, there are also edge-level traffic analytics.

For SEO: referrers and top pages, plus some performance data from real visitors. Useful as a free baseline.

Watch out for: fewer analytics features than dedicated tools; data retention and sampling vary by plan.

7. Your own server logs (with a tool like GoAccess)

Not an analytics service, but worth including. GoAccess is an open-source log analyser that turns access logs into terminal or HTML reports.

For SEO: logs see every request, including search engine crawlers, which no client-side script can. That makes logs the place to answer "is Googlebot actually fetching my new pages?" They also see visitors who block scripts.

Watch out for: logs count bots as well as people, and separating them takes work. Referrer data is there, but you'll be doing more of the analysis yourself.

How we'd combine them

For most small and medium sites, a sensible SEO setup looks like:

Search Console and Bing Webmaster Tools for queries, impressions, clicks and indexing.
One lightweight analytics tool for what search visitors do once they arrive: landing pages, engagement, conversions.
Server logs when you need to understand crawlers.

None of these on its own gives the full picture. Together, they cover it without the weight of a full marketing analytics suite.

A quick sanity check after switching

After you change analytics tools, compare clicks in Search Console against search-referred visits in your new tool over the same few weeks. They'll never match exactly; they measure different things, in different ways. But they should move in the same direction. If Search Console shows clicks going up while your analytics shows search visits falling, investigate before trusting either.

At seotto.com we care about measurements that are honest about their limits. Knowing what your analytics can't see is as important as what it can.