GA4 & Google Tag Manager Code Checker
Detect tracking code in public HTML; this does not measure bot traffic or verify event delivery.
Working...
What can this checker actually detect?
Google Analytics 4 automatically excludes known bots and spiders using Google research and the IAB list. Unrecognized bots may still appear. This checker only looks for GA4, GTM and other tracker signals in public HTML; it does not access the website analytics data.
Missing code does not prove analytics is absent: it may load after consent or be injected by JavaScript. Finding code does not prove events are delivered correctly. Verify with Tag Assistant and GA4 reports. When comparing server logs, CDN requests and SearchBastion risk scores, use the same time period and account for the different populations each source measures. A risk score is not proof that a visitor is human or a bot.
- Find GA4 IDs and GTM containers present in HTML
- List signals for common trackers detected on the page
- Understand detection limits and compare data sources
Example: interpret a finding and fix it
Illustration only, not a check of your website.
The HTML scan finds no GA4 code, but Tag Assistant sees an event after cookie consent. That may be an intentional consent flow; adding another tag based only on this scan could duplicate collection.
Align the date range and timezone before comparing sources. Label CDN requests, GA4 sessions and internal clicks separately. One page view can generate many requests, so subtracting these populations does not produce a bot percentage.
A measurement ID establishes a code trace. Verify actual delivery with Tag Assistant, DebugView and reports you are authorized to access.
How to use in 3 steps
- 1Enter the homepage or landing page URL to check.
- 2Click "Analyze now" to read public HTML and look for tracking code signals.
- 3Compare detected IDs with your configuration; verify actual events with Tag Assistant and GA4.