How to Do SEO Tracking & Analytics Setup: A Step-by-Step Workflow
Setting up SEO tracking correctly follows a specific order: verify the domain, deploy the tag manager, connect analytics, link Search Console, define conversions, then layer in rank tracking and reporting. Do the steps out of order and you’ll end up rebuilding filters or re-tagging events later — we’ve cleaned up enough backwards setups to know the sequence matters as much as the tools themselves.
- Step 1: Establish Domain Ownership First
- Step 2: Deploy Google Tag Manager First, Not Last
- Step 3: Connect GA4 Through the Tag Manager
- Step 4: Link Search Console to GA4
- Step 5: Define and Build Conversion Events Before You Need Them
- Step 6: Set Up Filters and Exclusions
- Step 7: Layer In Rank Tracking
- Step 8: Build the Reporting Layer
This is the workflow we run at Salterra for every new client, adjusted slightly for platform. It assumes you have admin access to the domain (DNS or file upload) and a Google account you control — not a shared or agency-owned one.
Step 1: Establish Domain Ownership First
Before installing anything, verify domain ownership in Google Search Console. Use the DNS TXT record method rather than the HTML file upload method if you can — it verifies the whole domain (including subdomains and http/https variants) in one shot instead of a single URL prefix. This matters because most sites have www and non-www versions, and sometimes a staging subdomain, all of which need to funnel into one clean view.
Add the TXT record through your domain registrar or DNS host, confirm verification in Search Console, and don’t move to the next step until that’s done. Everything downstream — Tag Manager, GA4 linking — assumes a verified, unambiguous domain.
Step 2: Deploy Google Tag Manager First, Not Last
A common mistake is installing GA4’s tracking snippet directly in the site header, then adding Tag Manager later for everything else. Reverse that. Install the GTM container code first — the script goes in the page’s head section and a noscript fallback right after the opening body tag — and route every other tag, including GA4, through it. This gives you one place to manage, debug, and eventually remove or swap tracking scripts without touching site code again.
- Create the GTM container under the client’s own Google account, not an agency account.
- Use GTM’s built-in Preview mode immediately after install to confirm the container is firing on every page template — home, blog post, product, contact.
- Publish only after preview confirms clean firing; an unpublished container captures nothing.
Step 3: Connect GA4 Through the Tag Manager
Inside GTM, create a GA4 Configuration tag using your GA4 Measurement ID, set it to fire on All Pages, and publish. Then verify data is flowing using GA4’s Realtime report — load the site in an incognito window and confirm your own session shows up within a minute or two.
At this stage, also set the data retention window in GA4’s admin settings to the maximum available (currently 14 months) rather than the default shorter window — this is a one-time setting that’s easy to forget and impossible to retroactively fix once data has aged out.
Step 4: Link Search Console to GA4
Inside GA4’s Admin panel, under Product Links, connect the Search Console property you verified in Step 1. This pulls query-level and landing-page-level search data directly into GA4’s Acquisition reports, letting you see organic queries alongside on-site behavior in one place instead of switching between two platforms constantly.
This link only works one direction — it enriches GA4 with GSC data, it doesn’t feed GA4 conversion data back into GSC. Keep that in mind when you’re deciding where to build your primary reporting dashboard later.
Step 5: Define and Build Conversion Events Before You Need Them
This is the step most setups skip, and it’s the one that costs the most later. Before you consider tracking “done,” sit down and define, in plain language, what a conversion actually is for this specific business: a form submission, a phone click, an add-to-cart, a newsletter signup, a booking confirmation.
- Build each event as a GTM tag triggered by the relevant interaction (click, form submit, page view of a thank-you page).
- Mark the corresponding event as a “key event” (GA4’s current term for a conversion) inside GA4’s admin settings.
- Test each one with GTM Preview and GA4 DebugView before publishing — a form event that silently fails to fire is worse than no tracking at all, because it creates false confidence.
For phone-driven local businesses, this step should include dynamic number insertion or call tracking if budget allows, since organic phone calls are otherwise invisible to GA4 entirely.
Step 6: Set Up Filters and Exclusions
Raw analytics data is noisy by default. Exclude internal traffic (office IP addresses, or better, a browser-based debug parameter), filter out known bot traffic, and if the business has an internal team frequently visiting the site, build an internal traffic exclusion in GA4’s Admin > Data Settings > Data Filters. Skipping this step is how businesses end up believing their content is performing better than it actually is.
Step 7: Layer In Rank Tracking
With behavior and visibility data flowing, add a dedicated rank tracker — Semrush’s Position Tracking, Ahrefs’ Rank Tracker, or a standalone tool like AccuRanker — and load it with the actual keyword list the content strategy targets, not a generic head-term list. Set the tracking location and device (desktop and mobile separately, since rankings diverge) to match where your actual customers are searching.
Rank tracking should run on a consistent schedule — daily for competitive or fast-moving niches, weekly is sufficient for most local and mid-competition terms. Daily tracking on every keyword for every site burns tool credits fast without adding much decision-quality; reserve it for terms you’re actively working to move.
Step 8: Build the Reporting Layer
The final step is pulling GA4, Search Console, and rank tracking data into a single dashboard — Looker Studio is the standard free option and connects natively to both Google products, plus most rank trackers offer a connector or CSV export. Build the dashboard around the questions the business actually asks, not every metric available: organic sessions and key events by landing page, ranking trend for priority keywords, and impressions/CTR trend from Search Console.
Resist the urge to build a 20-tab dashboard nobody opens. One page that answers “is SEO working” in under thirty seconds gets checked monthly; a sprawling report gets checked once and ignored.
Frequently Asked Questions
What order should GA4, GTM, and GSC be set up in?
Verify the domain in Search Console first, deploy Tag Manager second, connect GA4 through Tag Manager third, then link GSC to GA4 last. Setting up GA4 before Tag Manager usually means redoing the install once you need custom event tracking.
How long does a proper tracking setup take?
For a straightforward business site, budget half a day for the technical install and verification, plus a follow-up session a week later once real traffic has flowed through to confirm events and filters are working as intended. Ecommerce or multi-location setups take longer due to enhanced ecommerce event mapping.
Can I set this up without a developer?
Yes, for most CMS platforms. WordPress, Shopify, and Squarespace all support GTM installation through a plugin or built-in field, no code editing required. Custom-built sites or complex ecommerce event tracking (like enhanced ecommerce with product-level data) benefit from developer involvement.
Should I migrate historical Universal Analytics data into GA4?
Universal Analytics data can't be migrated into GA4's data model directly — the two use fundamentally different measurement approaches. Export your historical UA data to a spreadsheet or a business intelligence tool for archival reference, but treat GA4 as a fresh start with its own trend line going forward.
What's the fastest way to check my setup is working correctly?
Use GTM's Preview mode alongside GA4's DebugView simultaneously. Click through your site's key actions — form submits, add to cart, phone number clicks — and confirm each event appears in DebugView in real time before you consider the setup complete.
Do I need a separate GA4 property for each location or brand?
Generally no — use one GA4 property with data streams or custom dimensions to separate locations, unless the businesses have entirely independent stakeholders, budgets, or reporting needs. Separate properties fragment your data and make cross-location comparison harder than it needs to be.
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.