SiteAud!tLint Support

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.

What this means

The same tag is loaded more than once on the page: either a Google Tag Manager container, or a GA4 tag set up twice. The evidence shows which one and how many times, for example GTM-ABC123 loaded 2 times.

Why it matters

When a container or GA4 tag loads twice, every event it sends can be counted twice: page views, sessions and conversions. Bounce and engagement rates become wrong, and conversion numbers look better than they are. Ad platforms receiving those conversions optimise on bad data.

Common causes

  • The snippet in two places: hard-coded in the theme and also added by a plugin or app.
  • Two plugins that each install the same GTM container or GA4 tag.
  • A layout and a page template that both include the head snippet.
  • Single-page apps that inject the tag again on every route change.

How to fix it

  1. Search the page source for the ID, or use a custom source search for it across the site, to see every place it is added.
  2. Keep one installation, preferably in the main layout or one plugin, and remove the rest.
  3. In single-page apps, load the tag once at start-up and send page views on route changes instead.

Verify the fix

Recrawl. With Render JavaScript on in Crawl settings, check Page view sent twice on one page load too, which shows whether duplicate hits actually fire.

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