GA4 sent by page code and by GTM

Severity: Critical
Impact: High
Effort to fix: Low
Issue code: track_ga4_double

Why it matters

The same GA4 ID is hard-coded in the page and also sent by the GTM container, so page views and events are usually counted twice.

How to fix it

Keep GA4 in one place, ideally GTM: remove the hard-coded gtag.js config for that ID.

How it affects your score

Tracking issues have their own Tracking score and never lower the SEO site health score. They still appear in the Action Plan, the issues CSV, Slack messages and Linear tickets. Blocks indexing, breaks pages or loses traffic. Fix these first.

Find the affected URLs

Open Crawl > Issues and pick GA4 sent by page code and by GTM. Each affected URL is listed with its evidence, and Copy URLs or Export URLs hands the list to a developer. The issue also appears in the Action Plan, ranked by impact (high) and effort (low), and in the issues CSV under the code track_ga4_double. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.

Guides that cover this issue

Tracking and pixels audit