The free tags behind Google Ads and SEO performance
TL;DR
GA4, GTM, Meta Pixel, Merchant Center, and Search Console each answer a different part of the performance picture: how Google sees the site, what visitors do, what conversion signals reach ads platforms, what products surface in shopping. Verifying each is firing is the half most accounts skip.
Most growing businesses ask the same question eventually. Which tracking tags should I actually have on my site, and what does each one do?
Behind that question is the more useful one. What would each tag let me see, and what decisions could I make from what it shows? Different platforms answer different parts of the performance picture. GA4 reads what visitors do once they arrive. Google Tag Manager is the layer that wires the rest together cleanly. The Meta Pixel feeds Meta with the conversion signals it needs to optimise ads and build retargeting pools. Merchant Center puts the product catalogue on organic shopping surfaces. Search Console reads how Google sees the site. All are free.
Installing the tags is the easy half. The half that gets skipped, and the half that decides whether the rest of the marketing data is usable, is verifying each one is actually firing correctly. A tag in the page source isn't the same as a tag in working order, and the verification step is what tells you which.
Here are the foundational ones, with the verification habit alongside each.
Google Analytics 4 (GA4)
GA4 answers the post-arrival question. Once a visitor lands on the site, what do they look at, what triggers a conversion, how often do they come back, which channel brought them? It feeds Google Ads with audience and conversion data, surfaces Search Console queries alongside session behaviour when the two are linked, and exports cleanly to most third-party reporting platforms. It replaced Universal Analytics in July 2023 and is the foundation most other reporting reads from.
The setup is a measurement ID (starts with G-) installed in the <head> of every page. Most platforms expose a native integration: Shopify, WordPress, Wix, Squarespace, and Webflow all have a one-field input. On framework-driven sites (Next.js, Astro, SvelteKit), the Google tag goes in a head component that ships through the build.
For EU and EEA traffic, Consent Mode v2 is required. Without it, GA4 stops feeding ad measurement data and your Google Ads audiences shrink. Google added a dedicated consent settings section to GA4 in early 2024 to surface the configuration (Search Engine Land coverage, 14 February 2024). Tag Manager has the same EEA requirement.
For the wider context underneath Consent Mode (what cookies do, the first-party vs third-party distinction, why the consent gate exists at all), Hannah's HGDR Consulting piece on how cookies work and why site owners use them is the conceptual primer. Detailed Consent Mode setup walkthroughs will follow in their own posts.
The verification step. Open GA4 (Reports > Realtime), visit your site in another tab, and confirm your visit shows up within seconds. If it doesn't, the tag isn't firing. For Next.js sites specifically, Hannah's writeup at HGDR Consulting walks through the install via `@next/third-parties` with verification in the same flow.
Google Tag Manager (GTM)
GTM is the orchestration layer. Instead of pasting individual tags (GA4, Google Ads, Meta Pixel, schema markup, custom conversions) directly into the site, one GTM snippet loads the rest through a single interface. Marketing changes such as adding a new conversion event, pausing a tag during a campaign launch, or swapping providers happen without redeploying the site or filing engineering tickets.
For most sites, the client-side container is enough. Server-side GTM is a separate product that runs on hosting you provide (Google Cloud Run, AWS, or a Cloudflare Tag Gateway integration). Server-side adds first-party data control and partial recovery of iOS measurement, but introduces hosting cost of around $45 per month on Cloud Run per Google's setup docs. Early-stage sites do fine on the client-side container.
The dataLayer is the lever most beginners skip. It's a JavaScript array on the page that other tools (GA4, Meta Pixel, Google Ads conversion) can read. Pushing structured events (purchase, add_to_cart, lead_submit) to the dataLayer once means every tag downstream picks them up without separate code per platform. Single source of truth for events.
The verification step. Use GTM's Preview mode. It loads your site in a debug overlay listing every tag fired, the dataLayer state, and which triggers matched. If a tag should have fired but didn't, Preview tells you why.
Meta Pixel and Conversions API
The Meta Pixel and Conversions API together collect the audience and event data Facebook and Instagram need to optimise ads and build retargeting pools. Installing the Pixel before running paid social means the data is collected from day one, and a warm Pixel performs better at ad launch than a cold one. A single Pixel can feed multiple campaigns and ad accounts later, so this is one of the tags worth installing even when paid social isn't on the immediate roadmap.
The current setup is Pixel plus Conversions API together. The Pixel captures what the browser can see; the Conversions API captures server-side events the browser can't, and works around iOS 14.5 Tracking Transparency limits that block the Pixel on a large share of Apple traffic.
In April 2026, Meta released an official Pixel template inside Google Tag Manager that maps GA4 dataLayer events to Meta events automatically. For sites already running GTM with GA4, the template is the fastest setup path and replaces every previous community workaround.
The verification step. Install the Meta Pixel Helper Chrome extension and load your site. It lists every event firing on the page with parameters and any errors. For the Conversions API side, the Events Manager in Meta Business Manager has a Test Events tab that shows server-side events arriving in near-real time.
Google Merchant Center
For sites selling physical or downloadable products, Google Merchant Center puts the product catalogue in front of shoppers on Google's organic surfaces: Search, Images, Lens, YouTube, Gemini, the Shopping tab, and the products module on Google Business Profile. New accounts are opted into free listings by default. Visibility is conditional on feed quality: products without complete attributes (title, description, image, price, availability, GTIN where available) don't surface even when the account is active.
Shopify, WooCommerce, Wix, and Squarespace each offer a native integration that pushes the catalogue to Merchant Center automatically. Custom-built sites submit the feed as a TSV, XML, or Content API push.
Merchant Center is also a prerequisite for Performance Max shopping ads. The same feed quality decides whether products are eligible to be advertised, so the free-listings setup is what gates paid shopping later.
The verification step. Open the Diagnostics page in Merchant Center. It lists every product disapproval, validation warning, and feed error, ordered by severity. Resolve high-severity items first. A "Not yet indexed" status on free listings in the first week is normal; persistent indexing failure beyond that is almost always a feed validation issue rather than an organic visibility problem.
Google Search Console
Search Console is how Google tells you what it sees of the site. It reports which pages are indexed, which queries the site ranks for, real-user Core Web Vitals data, and any security or manual action flags. The Performance report is the closest the platforms come to a free organic-search analytics product, and the data feeds GA4 reporting once the two properties are linked.
Setup is property creation plus ownership verification. We covered the verification flow per platform in a separate post. The short version is a URL prefix property with the HTML tag method on most managed platforms, or DNS verification if you have registrar access for a Domain property.
The verification step. Once verified, submit your XML sitemap under Indexing > Sitemaps and check that the status returns "Success" within a few days. The Performance report starts populating within a week. If Search Console reports "Not started" on a submitted sitemap a week later, the sitemap URL usually isn't returning the file at the address you submitted, so view it in a browser and check.
Stack-specific conflicts and data hygiene
Once the foundational tags are in, the next layer of issues is the tech stack itself causing tags to duplicate, miss events, or break across domain handoffs. None of these show up in a Realtime or Preview check; they surface in the data weeks later as a baffling drop, a strange referral pattern, or session counts that look too high.
Duplicate installations. A Shopify store with GA4 installed via the native integration and again through GTM sends every event twice. WordPress sites running two SEO plugins that each inject the Google tag (Yoast and Rank Math is the common pair) hit the same problem. Pick one installation path per tag and remove the others.
Single Page Apps and client-side routing. React, Next.js, Vue, Svelte, and similar frameworks don't trigger a full page load on client-side route changes, so GA4's default page_view event misses every navigation after the first one. The fix on Next.js App Router is the @next/third-parties approach; custom React stacks push a page_view to the dataLayer on every route change.
Iframes and checkout handoffs. Calendly, Stripe Checkout, embedded booking widgets, payment redirects, and most third-party widgets break session continuity. Cross-domain measurement in GA4 (Admin > Data Streams > Configure your domains) lists every domain that should be treated as one session. Shopify's hosted checkout in particular runs on a separate domain and client-side pixels don't fire there for most plans, so Customer Events, server-side GTM, or the Conversions API are what survive the handoff.
Internal traffic. Without an IP filter, team members and developers loading the site inflate session counts and conversion rates. GA4 doesn't filter internal traffic by default; an IP-based filter under Admin > Data Filters fixes it. The same logic applies to staging and preview deployments hitting production tags.
Each of the above usually needs investigation rather than a one-shot fix. The pattern is to spot the symptom in the data (referral self-spam, session duplication, missing route navigation), trace it back to the layer that's interfering, and remove or reconfigure it. Worth auditing every few months and after any platform change.
After installing
Together the tags above answer the questions most accounts can't yet. Who's visiting, what they do, which channels drive conversions, what products surface in organic shopping, which queries the site ranks for. None of those questions can be answered well by the tag sitting in the page source alone. The data the tag should be sending is the answer.
That's the reason most accounts have at least one tag broken without anyone noticing. The tag is in the page source, the consultant signed off, and nobody opens Realtime, Preview, the Pixel Helper, or the data itself a few weeks later. Some breaks surface in the first check; others only in the trend lines. Either way, looking afterwards is the work that produces the result.
These foundational items sit on the free SEO checklist alongside the rest of the technical setup most sites need.