Google Analytics 4 Detector
Paste any URL and instantly see whether the site is built with Google Analytics 4 — with the matched evidence.
We do not store the URL you audit. Want the full audit (performance / images / SEO / accessibility + real-browser speed test)? → run the full audit
Why check this
Confirm the platform first: Third-party scripts decides what can be changed and whether it is worth it.
What this is
Google Analytics 4 is an event analytics platform loaded via googletagmanager.com/gtag/js or gtag/js?id=G- measurement IDs. Marketing and growth teams rely on it for channel attribution, while the script weight shows up in mobile TBT and consent-banner flows. Confirming GA4 clarifies whether collection is direct gtag, GTM-mediated, or only mentioned in a privacy policy. Measurement IDs starting with G- are easy to verify once you know which loader pattern the site uses.
How to tell from a public page
- [Google Analytics 4] Google Analytics 4 HTML/source match on `gtag/jsid=G-` (evidence shows hit count).
- [Google Analytics 4] Google Analytics 4 HTML/source match on `googletagmanager.com/gtag/js` (evidence shows hit count).
- [Google Analytics 4] Secondary Google Analytics 4 clue (ga4): leftover hosts still spelling Google Analytics 4.
- [Google Analytics 4] Policy-only Google Analytics 4 mentions (ga4) without a structural Google Analytics 4 host stay unconfirmed.
How to read the result
Conclude confirmed Google Analytics 4 only after hosts, headers or attributes prove the runtime is present. Consent mode or server-side collection can omit browser gtag on the first HTML response. Common false positives: Privacy policies listing GA4 without a front-end embed. After a hit: Map duplicate tags, consent firing, and whether GA4 arrives through a bloated GTM container.
What to do next
Map duplicate tags, consent firing, and whether GA4 arrives through a bloated GTM container. Container tooling often follows — see Google Tag Manager detector. Quantify script weight from run the full performance / images / SEO / accessibility audit on the home page.
Related detectors
FAQ
How is Google Analytics 4 detected?
From structural signatures in the public HTML and response headers (domains, paths, attributes, scripts). Every verdict lists how many times each pattern matched — nothing is guessed.
Can the result be wrong?
If only a bare brand keyword matches without structural evidence, we label it \u201clikely\u201d instead of \u201cconfirmed\u201d — we would rather under-report than cry wolf.
Do you save the URLs I check?
No. The audit runs inside the request and the URL you paste is not written to storage. There are no third-party tracking scripts on the page either, so no log of who checked what exists. Copy the result yourself if you want a record.
Can a website hide what it is built with?
Partly, but rarely completely. The HTML sent to your browser, the response headers, script paths and asset structure have to be exposed to work, so there is always something readable. Server-side code, build config and private APIs stay invisible. That is why this tool reports the evidence it found rather than claiming a full picture. No match does not mean the technology is absent.
Optimization help is available
Tell me your URL and what you want fixed — you get a clear scope, price and timeline.
To:[email protected] | Cc:[email protected]