Critical Tracking & Analytics

Pixel initialised twice on the page

Severity

Critical

Impact

High

Effort to fix

Low

Issue code

track_duplicate_pixel

Why it matters

An ad pixel initialised twice sends duplicate events, which inflates conversions and misleads ad bidding.

How to fix it

Initialise the pixel once: remove the hard-coded copy or the plugin/app copy, keep 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 Pixel initialised 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_pixel. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.

Related Tracking & Analytics issues

• CriticalGA4 sent by page code and by GTM
• CriticalGTM container not published or wrong ID
• CriticalPage view sent twice on one page load
• CriticalPersonal data or tokens in URL
• CriticalTag loaded twice on the page
• CriticalTracking before consent
• WarningAnalytics tag missing on this page
• WarningDifferent GA4 ID than the rest of the site