SiteAud!tLint Support

Opportunity Tracking & Analytics

GTM tag without a trigger

Severity
Opportunity
Impact
Low
Effort to fix
Low
Issue code
track_gtm_tag_no_trigger

Why it matters

A tag in the published container has no firing trigger, so it never runs. It may be a leftover or a tag whose trigger was deleted.

How to fix it

In Tag Manager, add the intended trigger to the tag or delete the tag, then publish.

What this means

A Google Tag Manager container the site loads contains a tag with no trigger, so it may never fire. The evidence shows the container and the tag, for example GTM-ABC123: Meta Pixel ViewContent. Paused tags are not reported.

Why it matters

A tag without a trigger usually means something someone expected to track is not being tracked: a conversion, an event, or a pixel. It can also be leftover clutter that makes the container harder to understand.

Common causes

  • A tag created and saved before its trigger was added.
  • A trigger deleted while still attached to tags.
  • Tags meant to be fired by another tag through Tag Sequencing. These are legitimate and can be ignored.
  • Old tags kept "just in case".

How to fix it

  1. Open the container in GTM and find the tag by name.
  2. If it should run, add the right trigger, then test it in Preview mode.
  3. If it fires through tag sequencing, leave it.
  4. If it is no longer needed, delete it.
  5. Publish the container.

Verify the fix

Recrawl. SiteAud!tLint reads the published container, so the issue clears after the new version is published. 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. A smaller improvement with a modest effect on its own.

Find the affected URLs

Open Crawl > Issues and pick GTM tag without a trigger. 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 (low) and effort (low), and in the issues CSV under the code track_gtm_tag_no_trigger. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.

Guides that cover this issue