SiteAud!tLint Support

Critical Tracking & Analytics

GTM container not published or wrong ID

Severity
Critical
Impact
High
Effort to fix
Low
Issue code
track_gtm_unpublished

Why it matters

The page loads a GTM container that Google does not serve, so none of its tags (GA4, pixels, conversions) fire.

How to fix it

Check the GTM-... ID in the snippet matches your container, and publish a version in Tag Manager.

What this means

The site loads a Google Tag Manager container, but Google returned an error for it, such as a 404. The evidence shows the container ID and the status, for example GTM-ABC123 returned HTTP 404: no tags in it fire.

Why it matters

Nothing in the container runs: no analytics, no ad conversions, no pixels. Every page that relies on this container is effectively untracked, while the snippet on the page makes it look like tracking is installed.

Common causes

  • The container was never published. A new container returns 404 until the first version is published.
  • A typo in the container ID in the snippet or plugin settings.
  • The container was deleted in the GTM account, or the account was closed after an agency change.
  • The wrong environment snippet, such as a staging environment's parameters left in the live code.

How to fix it

  1. In Google Tag Manager, open the account and check the container ID exactly matches the one in the evidence.
  2. If it has never been published, click Submit and publish a version.
  3. If the ID is wrong, correct it in the page snippet or the plugin settings.
  4. If the container no longer exists, remove the snippet and install the container you actually use.

Verify the fix

Recrawl. Improve > Tracking & Pixels shows each container's contents once it loads. See Google Tag Manager audit.

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 GTM container not published or wrong ID. 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_gtm_unpublished. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.

Guides that cover this issue