Analytics & Tracking

Duplicate Analytics Tracking

Also known as double tracking · duplicate tags · double counting

When GA4 loads more than once on a page—for example hard-coded with gtag.js and again through GTM—causing inflated, unreliable data.

What it is

Duplicate tracking happens when the same GA4 measurement ID fires from two delivery paths at once, typically a hard-coded gtag.js snippet plus a GA4 tag inside Google Tag Manager. The result is double-counted pageviews and events, deflated bounce rate, and inflated conversions.

Why it matters

Polluted analytics make it impossible to trust whether SEO, content, or AI search changes are working, because every metric is skewed. Clean, single-path measurement is the foundation for any data-driven decision about visibility and conversion.

How to verify

Open DevTools Network and filter for 'collect' requests; two requests with the same G- ID per pageview indicate double tracking. GA4 real-time inflation and Google's Tag Assistant showing the same tag twice are also clear signals.

How to fix

Choose one delivery method—usually GTM—and remove the other. If GTM fires GA4, delete the hard-coded gtag.js block from the page template, then re-check the Network panel to confirm only one collect request per pageview.

In the checklist

This concept maps to a check in the GEO Score checklist.

Use the checklist

Related terms

Official references

External, opens in a new tab.

Put this into practice.

Work through every check by hand and turn it into a shareable GEO Score report — or scan your site automatically in seconds.