SiteAud!tLint Support

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.

What this means

The Meta (Facebook) Pixel with the same ID is initialised more than once on the page. The evidence shows the ID and the count, for example Meta Pixel 1234567890 initialised 2 times.

Why it matters

Each initialisation can send its own events, so page views, add-to-carts and purchases may be reported twice. Meta's Events Manager then shows inflated numbers, and campaigns optimise towards conversions that did not happen. Meta's Pixel Helper browser extension usually warns about this too.

Common causes

  • The pixel hard-coded in the theme and also added by a platform integration, such as the Shopify, WooCommerce or Wix Meta channel.
  • The pixel in GTM as well as on the page.
  • Two plugins or apps that each install it.
  • A partner or agency adding its own copy of the same pixel.

How to fix it

  1. Search the page source for the pixel ID and fbq('init', or run a custom source search for the ID across the site.
  2. Keep one installation. Platform integrations are usually the best choice, because they also handle the Conversions API and deduplication.
  3. Remove the other copies from the theme, GTM or plugins.

Verify the fix

Recrawl. With Render JavaScript on in Crawl settings, check that Page view sent twice on one page load does not appear for the pixel. Confirm in Meta Events Manager's Test events that each action arrives once.

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.