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.

What this means

When SiteAud!tLint loaded the page in a browser, the same tool sent its page view more than once in a single page load. The evidence shows which one, for example GA4 G-ABC123 sent page_view 2 times on one page load.

This check needs Render JavaScript on in Crawl settings, because it watches the requests the page actually sends.

Why it matters

Every visit to this page is counted twice. Page views double, engagement and bounce metrics are skewed, and if conversion events fire the same way, ad platforms receive inflated results.

Common causes

  • The tag installed twice, such as hard-coded and in GTM. See GA4 sent by page code and by GTM and Tag loaded twice on the page.
  • A GA4 configuration tag plus a separate page_view event tag in GTM, both sending a page view.
  • Enhanced measurement history changes in GA4, combined with a single-page app that also sends page views on route changes.
  • A tag with two triggers that both fire on page load, such as "All Pages" and "DOM Ready".

How to fix it

  1. In GTM's Preview mode, load the page and see which tags send a page view and on which trigger.
  2. Keep one page view per page load: usually the Google tag's automatic page view, with no extra page_view event tag.
  3. For single-page apps, choose either GA4's history-change page views or your own route-change events, not both.

Verify the fix

Recrawl with rendering on, and check GA4's DebugView shows one page_view per page load.

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