SEO Tracking Checklist: The Essential Best Practices
A reliable SEO tracking checklist covers four areas: account structure, data accuracy, conversion mapping, and ongoing maintenance. Miss any one of these and you end up with numbers that look plausible but lead you to the wrong decisions — which is worse than having no data at all.
This is the checklist we run through on every account audit at Salterra, whether we built the setup ourselves or inherited it from a previous agency. Treat it as a standard to hold your own setup against, not a one-time task.
Account Structure Fundamentals
Get the foundation right before worrying about anything else. A messy account structure creates problems that compound every month it goes unfixed.
- GA4 property, Search Console property, and Tag Manager container all live under the client’s own Google account — never an agency-owned one.
- Domain is verified in Search Console via DNS, covering all subdomains and both http/https and www/non-www variants.
- GA4 data retention is set to the maximum window (currently 14 months), not the default.
- Only one GA4 data stream per actual property unless there’s a documented reason for more.
- User access is reviewed periodically — remove former employees and agencies who no longer need it.
Tag Deployment Checks
Tags that don’t fire, or fire twice, are the single most common source of bad SEO data. Before trusting any report, confirm the plumbing is clean.
- GTM container fires on every page template — homepage, category, product/service, blog, contact — verified with Preview mode, not assumed.
- Only one instance of the GA4 base tag fires per page (duplicate installs are common after platform migrations or plugin conflicts).
- No tags fire on staging or development environments feeding into the production GA4 property.
- Consent mode is configured correctly if the site operates in a region requiring cookie consent, so tracking respects opt-in/opt-out choices.
Conversion and Event Accuracy
Traffic numbers are interesting; conversion numbers are what the business actually cares about. This section deserves the most scrutiny, because a broken conversion event can silently distort strategy for months.
- Every meaningful action — form submit, phone click, add to cart, purchase, booking, download — has a corresponding GA4 event, tested in DebugView before launch.
- Key events (GA4’s conversions) are marked deliberately, not left as GA4’s automatic defaults, which can overcount things like generic page_view or session_start.
- Thank-you page or confirmation-based events can’t be reached by directly typing the URL, which would inflate conversions with non-genuine completions.
- Ecommerce sites use GA4’s enhanced ecommerce event structure (view_item, add_to_cart, purchase) rather than generic custom events, to unlock revenue and product-level reporting.
Data Hygiene and Filtering
This is the layer most setups skip entirely, and it’s where inflated, misleading numbers come from.
- Internal traffic exclusion is configured for office IPs or via a debug parameter, and reviewed if the team works remotely from changing locations.
- Known bot and spam traffic is filtered — check Search Console and GA4 for suspicious referral sources or crawler-pattern sessions.
- Referral exclusion list includes any payment processors or booking widgets that redirect users off-domain and back, which otherwise break session attribution.
- Currency and timezone settings in GA4 match the business’s actual operating location.
Search Console-Specific Checks
Search Console has its own maintenance needs separate from GA4, and it’s the tool most likely to get ignored once initial setup is done.
- XML sitemap is submitted and shows as successfully processed, not just “discovered.”
- Coverage report is checked monthly for a spike in excluded or error pages, which often signals a technical issue before rankings drop.
- Core Web Vitals report is reviewed for pages flagged as “poor,” since this can quietly cap ranking potential.
- Manual actions and security issues panels are checked — these are easy to forget because they’re rarely triggered, but catastrophic when they are.
Rank Tracking Hygiene
A rank tracker is only useful if it’s tracking the right things, in the right way, consistently.
- Keyword list reflects actual target terms from the content and SEO strategy — not a generic auto-generated list from the tool.
- Desktop and mobile rankings are tracked separately, since local and mobile-first queries frequently diverge from desktop results.
- Tracking location matches where actual customers search, down to the city level for local businesses.
- Competitor set in the rank tracker is reviewed periodically — competitors change, and a stale competitor list makes the comparison data useless.
Reporting and Review Cadence
Tracking without a review habit is just data collection for its own sake. Build the review into a recurring calendar habit, not something that happens only when someone asks.
- A single dashboard (Looker Studio or equivalent) pulls GA4, GSC, and rank data into one view, reviewed on a set monthly cadence.
- Year-over-year comparison is available and used, not just month-over-month, since SEO has seasonal patterns that short windows hide.
- Anomalies — sudden traffic drops, ranking drops, indexing errors — trigger an actual investigation within days, not at the next scheduled review.
Documentation and Handoff Readiness
A tracking setup that only exists in one person’s head is a liability, not an asset. This is the section most businesses skip entirely, and it’s the one that causes the most pain when a marketing hire leaves, an agency relationship ends, or a new team member has to pick up the account cold.
- A written record exists of what counts as a key event for this specific business, and why — not just what’s configured, but the reasoning behind it.
- Login credentials and account access are documented somewhere the business controls, not solely in an outgoing employee’s or vendor’s personal notes.
- GTM container changes are named and dated in version history well enough that someone unfamiliar with the account could reconstruct what changed and when.
- A one-page summary of the tracking architecture — what tools are connected, how, and what each dashboard tab shows — exists somewhere accessible to whoever inherits the account next.
None of this is glamorous work, and it’s easy to deprioritize when the tracking is already running fine. But the value of documentation is almost entirely realized later, at the moment of a handoff or a diagnosis under pressure — exactly when you don’t want to be reverse-engineering your own setup from scratch.
Ongoing Maintenance Triggers
Certain events should automatically trigger a checklist review, rather than waiting for the next scheduled quarterly audit. Treat these as tripwires, not optional follow-ups.
- Any site redesign or platform migration — these break tags, filters, and event tracking more often than any other single event.
- A new product line, service area, or major URL structure change, which usually means new conversion events and rank tracking keywords need to be added.
- A sudden, unexplained shift in any core metric — traffic, conversions, or rankings — that can’t be immediately attributed to a known cause.
- A change in who owns or manages the marketing function internally, which is the moment documentation gaps become most visible and most costly.
Frequently Asked Questions
How often should this checklist be run?
A full pass at initial setup, then a lighter audit quarterly, and always immediately after a site redesign, platform migration, or any major URL structure change — these are the events most likely to quietly break tracking.
What's the most commonly failed item on this checklist?
Internal traffic exclusion. It's easy to skip during setup because the site "seems to be tracking fine," but it inflates engagement metrics and skews conversion rate calculations in ways that only become obvious once someone compares GA4 numbers against actual sales or lead data.
Do small local businesses need the full checklist, or just parts of it?
Even a single-location business benefits from the full account structure and conversion sections — those prevent bad data. The rank tracking section can be lighter, focused on a shorter list of high-value local terms rather than broad competitive tracking.
How do I know if my current setup has hidden problems?
Cross-check numbers across tools. If GA4 shows organic sessions but Search Console shows far fewer clicks for the same period, or if reported conversions don't roughly match actual sales/leads reported by the business, something in the setup needs auditing.
Should this checklist be different for ecommerce versus lead-gen businesses?
The account structure and hygiene sections apply equally. The conversion section differs significantly — ecommerce needs full enhanced ecommerce event tracking with revenue data, while lead-gen businesses need tighter form and call tracking instead.
Is it worth paying a specialist to audit an existing setup?
If the business is making decisions based on the data — budget allocation, content strategy, hiring — yes. The cost of a bad decision made on broken data almost always exceeds the cost of an audit.
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.