How we monitor
Every site in the subimpact fleet is checked by the same monitor, running on a server every 6 hours. This page lists the checks and the live result for each site. Traffic numbers stay private.
Check 01
The monitor runs every 6 hours on a server. It loads each site’s live homepage and checks it answers.
Why it matters: If a redeploy or a DNS change leaves a homepage down, we know the same day rather than finding out from a customer.
Check 02
It checks that the expected Google Tag Manager container appears in the live HTML of the site.
Why it matters: Rebuilds recreate pages from source and snippets get left out. This catches a missing container per run. Sites that add the tag with JavaScript after the page loads are checked in a real headless browser instead, so they are held to the same standard.
Check 03
It checks that a Google Analytics 4 tag is present, directly in the page or through Tag Manager.
Why it matters: With no GA4 tag a site records nothing. Empty reports are easy to miss, so the monitor looks at this every run.
Check 04
It checks that the site’s property is verified in Google Search Console.
Why it matters: Verification is what makes search clicks available to compare with what GA4 records.
Check 05
It pulls GA4 sessions and Google Search Console clicks for the last 30 days and compares them. When search clicks are high but GA4 records far fewer sessions (under 15% when there are 50 or more clicks in 30 days) the run flags a tracking undercount. Common causes: consent mode set to block by default, a tag missing after a redeploy, or bot filtering.
Why it matters: An undercount makes funnel and performance reports look smaller than reality, which leads to wrong decisions.
Check 06
It flags any site with zero traffic and zero search clicks over 30 days for review.
Why it matters: Both zeros together usually mean either nobody can find the site or the measurement setup is broken, and both are worth a look.
Check 07
It checks that domains we have retired redirect cleanly to their new home.
Why it matters: Old links, print material and bookmarks keep working after a domain is retired, and visitors land where they should.
Check 08
The monitor keeps a history of past runs, and alerts go to the owner’s private dashboard.
Why it matters: When a check fails we can date the break precisely, see what changed, and confirm when it recovered.
Sites we are not allowed to name are listed as “Client site” with a number; that is deliberate. This page shows whether tracking is working, not traffic numbers.
Sites
Why
Sites get rebuilt and redeployed, and every rebuild is a chance for a tag snippet to go missing. Tracking fails without any visible change to the page itself.
If consent is set to block by default, GA4 can record a fraction of the real sessions. The site works fine; the measurement does not.
Search Console can show clicks that GA4 never records as sessions. Comparing the two sources is how we catch the gap instead of trusting one side of it.
Next step
We build the site, the tracking and the checks together, and then keep them running.
Start a Project