Accurate measurement is a prerequisite for accurate diagnosis. When I begin work with a new client, verifying the GA4 implementation is one of the first things I do — before reviewing rankings, before interpreting traffic trends, before drawing any conclusions about what's working.
The reason: GA4 breaks quietly, and it breaks in ways that don't announce themselves.
What Broken GA4 Looks Like in Practice
Across a multi-client audit engagement, I found GA4 implementations at various stages of dysfunction: missing event configurations, conversion tracking that wasn't firing against actual user behavior, traffic sources miscategorized in ways that distorted channel attribution, and in at least one case, a setup that required rebuilding from scratch because there was nothing functional to inherit.
None of this showed up as a ranking drop. The sites were getting traffic. The issue was that the traffic data being reported — and the decisions being made based on it — were structurally wrong.
When conversion events aren't configured correctly, you can't attribute leads. When traffic sources are miscategorized, channel-level performance looks different than it actually is. Budget decisions, campaign priorities, content investments — all of it gets made against a distorted picture.
Why This Matters Before Anything Else
If the measurement layer is wrong, every report built on top of it is wrong too. That's true regardless of how sophisticated the reporting dashboard looks, how regularly it's reviewed, or how many people are looking at it.
The fix is an implementation audit: validate that events are configured, that they're firing against real user behavior (not just assumed behavior), and that source/medium attribution is clean. For clients with longer histories in GA4, it's also worth reviewing whether historical data is reliable or whether the misconfiguration predates the current reporting period.
What an Implementation Audit Actually Checks
- Event coverage: Are the conversion events you care about (form submission, phone click, booking, purchase) actually configured — and are they firing when those actions happen?
- Event accuracy: Do the events fire only on the real action, or are they triggered by adjacent activity that inflates conversion counts? A “form_submit” event tied to a button click instead of a successful submission is a common false positive.
- Source/medium attribution: Is direct traffic actually direct, or is it absorbing what should be organic, paid, or referral traffic because of UTM gaps or self-referrals?
- Internal traffic exclusion: Are office IPs, staff sessions, and developer activity filtered out, or are they polluting the data?
- Cross-domain tracking: If the site spans multiple domains (booking subdomains, payment processors), is the user journey being stitched together or fragmented across sessions?
- Historical reliability: When did the misconfiguration begin? Any reporting period that predates the fix needs to be flagged as unreliable, not compared against post-fix data as though they're the same dataset.
The Broader Principle
Diagnostic work in SEO depends on trustworthy data. Before interpreting any performance signal — traffic, conversions, rankings, engagement — the measurement infrastructure needs to be verified. It's not a detour. It's the starting point.
If you've been making decisions on a GA4 setup nobody has validated in a year or two, the first useful thing isn't a new strategy. It's checking that the data underneath the strategy is real.