Google Analytics is not a bad product. It is a comprehensive, mature tool optimised for the marketing-funnel framing it was built around. For an SEO-driven website — content network, publisher, programmatic SEO operation — that framing can feel like an obstacle rather than a help.
The questions an SEO operator asks are narrow and concrete: which pages are being read, by which traffic source, including which AI assistants are reading or referring. The questions a marketing analyst asks (events, audiences, conversion paths, attribution windows) are a superset that buries the SEO questions in surface area.
What an SEO-first analytics tool looks like
When you start from "operators of content sites need a clear per-page picture", you end up with a small surface:
- A tight events table with pathname, traffic_category, referrer_source, and the five canonical UTM fields.
- A separate
bot_visitstable for AI/search crawlers — never mixed with human aggregates. - A dashboard whose default surface is "top pages, top sources, top AI surfaces" rather than a funnel.
- URL-driven site/range filters so you can deep-link to any slice without UI gymnastics.
Honest comparison
WebmasterID does not try to replace Google Analytics for ad-funded businesses or e-commerce funnels. It is intentionally smaller. What you get is a tool you can read end-to-end in an afternoon, install with a single script tag, and operate without a consent SDK on your hot path.
What you give up: cross-site cohorts, per-visitor profiles, retargeting audiences, GA's built-in connectors. If you need those, GA (or a paid funnel-analytics tool) is the right answer. If you do not, every line of code that supports those features is overhead for your use case.
Where to start
Read /architecture for the system shape, and /use-cases for whether your operation matches the audiences this is built for. The BuildDesignHub case study walks through what the install actually looked like.