SEO Tracking Examples: What Great SEO Tracking Looks Like
A great SEO tracking setup looks different depending on the business, but the underlying pattern is consistent: every meaningful action a visitor takes is captured as a clean, well-named event, that event is tied back to the search query or landing page that produced it, and someone can open a dashboard and answer “is this working” in under a minute. What follows is a set of illustrative, composite examples — patterns we recognize from years of client work rather than any single named account — showing what that looks like in practice across five common business types.
None of the scenarios below represent a specific client; they’re archetypes built to show the difference between a tracking setup that merely exists and one that earns its keep. Read them side by side and you’ll notice the same habits recurring: clear conversion definitions, deliberate GA4 and GTM architecture, and reporting built for the person who has to look at it.
Example One: A Multi-Location Local Service Business
Picture a plumbing or HVAC company with six locations across a metro area. A well-built tracking setup here starts with a single GA4 property rather than one property per location, with a location custom dimension populated automatically from the page template so every event carries a “which branch” tag without fragmenting the data across separate properties. Conversion events are narrowed to the handful that map to real revenue: a quote-request form submission, a phone call over a defined duration threshold captured through dynamic number insertion, and a “Book Now” click that reaches the scheduling step.
Google Business Profile is folded into the same picture rather than left in its own silo. Click-to-call and direction-request actions from each location’s GBP listing get UTM-tagged where the platform allows it, and GBP Insights data is compared monthly against the same location dimension in GA4 so a spike in profile views can be checked against an actual increase in tracked calls, not just assumed.
What a Weaker Setup Gets Wrong Here
The common failure mode is one GA4 property per location, which multiplies maintenance six-fold and makes cross-location comparison painful. The second is counting every phone click as a conversion regardless of call length, which inflates the numbers and eventually erodes trust once someone notices half those “conversions” were ten-second hang-ups.
Example Two: An Ecommerce Site
For an online retailer, a strong tracking setup means GA4’s ecommerce events are implemented properly rather than approximated. That means view_item, add_to_cart, begin_checkout, and purchase events firing with full item-level parameters — product ID, category, price, and quantity — pushed through the data layer via GTM rather than hand-rolled as generic click events. Done correctly, this lets the funnel report show exactly where shoppers drop off between viewing a product and completing checkout, broken down by traffic source.
The part that separates a good ecommerce setup from an adequate one is product-level attribution back to organic search. Search Console’s query and page data is cross-referenced against which product pages actually convert, not just which ones rank or get clicks — because a page can rank well and drive traffic while converting poorly due to a weak description or missing reviews, and that gap only becomes visible when the two data sources are examined together.
- Full-funnel ecommerce events: view_item through purchase, with item-level parameters intact
- Product-page organic performance: Search Console query data joined against GA4 conversion rate by landing page
- Enhanced conversions and consent mode configured so conversion data stays accurate as browser privacy defaults tighten
Example Three: A B2B or Lead-Generation Site
B2B buying cycles rarely convert on a single visit, so a good tracking setup for a B2B or lead-gen site is built around multi-touch visibility rather than last-click attribution alone. GA4’s built-in attribution reporting is supplemented with GTM events that capture meaningful engagement short of a form fill — a pricing-page view, a case-study download, a demo-video watched past the halfway point — each pushed as its own named event rather than lumped into generic “engagement.”
The setup earns its value at the handoff point: a form submission event carries hidden fields — source, campaign, and the landing page that started the session — that get passed into the CRM with the lead record. That connection lets a lead eventually be scored or marked “closed-won” in the CRM and, ideally, reflected back into GA4 or Looker Studio via an offline conversion import, so the team can see which organic pages produce leads that actually become customers, not just leads that fill out a form.
Closing the Loop Between Marketing and Sales
Without that CRM connection, B2B tracking only ever measures the top of the funnel. A genuinely good implementation treats the lead-scoring handoff as part of the build, not a separate project handled months later, because retrofitting attribution onto historical leads is far messier than building the connection in from day one.
Example Four: A Content or Publisher Site
For a site whose business model runs on traffic volume and engaged reading time rather than a single conversion event, tracking looks noticeably different. Scroll-depth events, time-on-page thresholds, and outbound link clicks to affiliate or ad partners become the primary engagement signals, tracked through GTM’s scroll and timer triggers rather than treated as an afterthought. A well-built setup segments this engagement data by traffic source, which reveals patterns a simple pageview count never would — organic search visitors from a Search Console-linked query, for instance, often read further and return more often than visitors from social referral, and that difference matters for editorial and monetization decisions alike.
This is also the example type where AI-search visibility deserves its own tracking layer. Referral traffic from AI Overviews, ChatGPT, Perplexity, and similar answer engines shows up in GA4’s referral and channel data, and a good setup adds a dedicated segment isolating it rather than letting it blend invisibly into “organic search” or “unassigned.” Because these platforms often answer a query directly and cite a source without generating a click — the classic zero-click pattern — publisher sites benefit from also watching branded search volume and direct traffic trends as a secondary signal of AI-driven visibility that referral numbers alone will understate.
Where ad revenue is part of the business model, correlating engaged sessions against ad revenue per session (pulled from the ad network and matched against GA4 session data by date and page) shows whether traffic growth is actually translating into revenue growth, or whether a spike in low-engagement sessions is just diluting the average.
Example Five: A Multi-Brand or Agency-Managed Portfolio
When one team manages tracking across many client accounts or brands, the setup that scales looks less like a single install and more like a system. A well-run portfolio uses a standardized GA4 and GTM naming convention across every property — consistent event names, consistent conversion definitions, a shared custom-dimension schema — so a strategist can move between accounts without relearning the logic each time. This is the discipline we apply across Salterra’s own managed accounts, and it’s the difference between tracking that scales cleanly to dozens of sites and tracking rebuilt from scratch under every new client.
The reporting layer reflects that same standardization: a single Looker Studio template, built once with a data-source parameter for client selection, gets cloned per account rather than hand-built each time. That template consistency is what makes it possible to spot, at a glance, which accounts in a portfolio are underperforming their own historical baseline without opening ten different dashboards that each define “conversion” slightly differently.
What Breaks Without a Standard
Portfolios without a shared architecture accumulate inconsistency fast — one account calls a phone click a “conversion,” another calls it an “engagement event,” and a third never defined it at all. That inconsistency is invisible on any single account and becomes a serious liability the moment leadership wants to compare performance or hand an account to a new team member.
What Separates These Examples From a Mediocre Setup
Across all five examples, the pattern isn’t a specific tool choice — it’s discipline applied consistently: conversions are defined narrowly around real business outcomes, data sources are cross-referenced against each other rather than read in isolation, and the reporting layer is built for whoever actually has to read it. A mediocre setup usually gets the installation right and stops there, leaving a GA4 property full of default events and a Search Console property nobody ever links to anything else.
The businesses that get the most value from their tracking treat it like any other piece of infrastructure — reviewed periodically, documented, and adjusted as the search landscape changes, including the growing slice of visibility now coming from AI-driven answer engines rather than traditional blue links alone.
Frequently Asked Questions
Do all businesses need the same GA4 events, or should tracking be customized per business type?
The measurement framework — GA4, GTM, Search Console — is the same across business types, but which events count as meaningful conversions should always be customized to the actual business model, since a phone call matters enormously to a local service business and barely at all to a content publisher.
Is it worth setting up ecommerce tracking for a site that only sells a handful of products?
Yes, because GA4's ecommerce reporting gives you funnel visibility — where shoppers drop off between viewing and buying — that generic event tracking can't replicate, and that visibility matters just as much for a small catalog as a large one.
How does a B2B site track leads that take months to close?
By passing source and campaign data into the CRM at the point of form submission and, where possible, importing closed-deal outcomes back into GA4 or a reporting dashboard, so long sales cycles can still be traced back to the marketing activity that started them.
What should a content or publisher site track besides pageviews?
Scroll depth, time-on-page thresholds, and outbound or ad-related clicks give a far more useful picture of engagement than raw pageviews alone, and segmenting those metrics by traffic source shows which channels bring genuinely engaged readers rather than just volume.
Why does naming convention matter so much for agencies managing multiple accounts?
Inconsistent naming across client accounts makes it impossible to compare performance at a glance or hand an account to a new team member without a lengthy explanation, while a standardized convention turns every new account into a twenty-minute clone rather than a rebuild.
How can a site tell if it's getting traffic or visibility from AI answer engines?
Check GA4's referral and channel reports for traffic attributed to AI platforms directly, but also watch branded search volume and direct traffic trends in Search Console and GA4, since AI answer engines often satisfy a query without generating a click at all.
Terry has 30+ years in software and SEO. He’s the founder of Salterra Digital Services and SEO Spring Training, host of the Roundtable SEO Mastermind, and lead instructor at SEO University — teaching the exact tactics his team uses on client work.
Continue learning
Ready to master this?
This guide is one lesson from the SEO Tracking & Analytics Setup course. Get every lesson, framework and checklist — plus the full 38-course catalog — inside SEO University.
Practitioner-focused training across the full digital marketing stack — from technical SEO to conversion optimization and the AI search era. By Salterra Digital Services, since 2011.