SiteAud!tLint Support

Critical Tracking & Analytics

Page view sent twice on one page load

Severity
Critical
Impact
High
Effort to fix
Medium
Issue code
track_double_fire

Why it matters

The browser sent the same page view event twice while loading this page, so traffic is double counted in reports.

How to fix it

Find the second source (hard-coded gtag plus GTM, or two GA4 config tags) with GTM Preview and remove one.

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 Page view sent twice on one page load. 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 (medium), and in the issues CSV under the code track_double_fire. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.

Guides that cover this issue