Critical Tracking & Analytics
Tag loaded twice on the page
- Severity
- Critical
- Impact
- High
- Effort to fix
- Low
- Issue code
track_duplicate_container
Why it matters
The same GTM container or gtag.js loaded twice usually sends every event twice: double page views, halved bounce rate and inflated conversions.
How to fix it
Keep one snippet. Check the theme or template, plugins and any app that also injects the tag.
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 Tag loaded twice on the page. 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_duplicate_container. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.
Guides that cover this issue
Related Tracking & Analytics issues
- CriticalGA4 sent by page code and by GTM
- CriticalGTM container not published or wrong ID
- CriticalPage view sent twice on one page load
- CriticalPersonal data or tokens in URL
- CriticalPixel initialised twice on the page
- CriticalTracking before consent
- WarningAnalytics tag missing on this page
- WarningDifferent GA4 ID than the rest of the site