Google officially deprecated Universal Analytics on July 1, 2023. Though the platform stopped processing data altogether a year later, we’re still finding dead UA tracking code on a good chunk of the WordPress sites we’ve audited in 2026.
Some sites have UA running alongside GA4 without realizing it. Others never got around to or never knew they were supposed to make the switch at all. I’ll walk through what you need to know.
Where Most WordPress Sites Stand on Analytics
If you are a marketing manager who inherited your company’s analytics setup (or even if you manage SEO yourself), there is a real chance you are in one of three situations right now:
- You have UA code and no GA4, which means you have been flying blind for years.
- You have both UA and GA4 firing, your site is slower than it needs to be, and you may be double-counting events in downstream tools.
- You think you have GA4, but what is deployed is a half-finished migration someone started and abandoned.
One of these scenarios shows up in about half the sites we touch. The good news is they are easy enough to check on your own in about five minutes. And you don’t need to touch any code.
Why Dead Tracking Codes Cause Problems
Leaving old UA tags in place has real consequences that go beyond cluttered code. The most immediate one is page speed. Every legacy script is a network request your browser has to work on before the page finishes loading. Google’s Core Web Vitals are a direct ranking factor for SEO, and removing unused tracking pixels is one of the easiest Lighthouse score improvements most sites ignore. Cleaning them up costs nothing and typically moves the needle pretty quickly.
Data integrity is another issue. If you migrated to GA4 but left UA events firing inside a tag manager container, your conversion counts, audience definitions, and attribution reports can all drift in ways that are hard to debug later. Mismatched numbers between GA4 and downstream tools like HubSpot are one of the most common symptoms we see, and tracking hygiene is almost always the culprit. The problem is you are flying blind if you can’t trust this data.
Then there is compliance. Unmaintained third-party scripts are a GDPR and CCPA liability. Your consent management platform may still be gating UA tags that no longer collect anything, which means your cookie banner is asking users to opt into nothing. That is a conversation you do not want to have with your legal team after the fact. If WordPress security best practices are on your radar, keeping dead third-party scripts off your site belongs in the same category.
Key Risks of Dead Tracking Codes:
- Slower page loads from scripts that collect nothing
- Conversion data that drifts and cannot be trusted
- Cookie banners that gate tags no longer doing anything
- GDPR and CCPA exposure from unmaintained third-party scripts
How To Check if Universal Analytics Is Still on Your Site
You do not need a developer to run this check. Right-click your homepage, select “View Page Source,” and use Ctrl+F (Cmd+F on Mac) to search for the following strings. Finding any of them means you have dead code running on your site:
- UA- followed by numbers – the legacy Universal Analytics property ID prefix
- ga(‘send’ – the classic analytics.js send command, no longer functional
- gtag(‘config’, ‘UA- – a UA tag being fired through gtag.js, also collecting nothing
What you want to see is G- followed by letters and numbers, which is a valid GA4 measurement ID. If you find a UA ID and no G- ID anywhere, your site has not been migrated at all.
If you use Google Tag Manager, open your container and filter tags by type. Any tag listed as “Universal Analytics” can be paused and archived. If you see both a UA tag and a GA4 tag firing on the same trigger, your events are potentially being double-counted in any tool pulling from that data layer, which creates the attribution confusion mentioned above.
Checking plugins is a good place to start. Tools like MonsterInsights, Site Kit by Google, and ExactMetrics all have their own analytics setup, and they might be pointing to a dead UA property ID even if your tag manager looks clean. Custom theme files edited by previous developers are worth a look too. You can open each one, confirm only a GA4 property ID is configured, and remove the UA property from the settings before you deactivate anything.
Confirming GA4 Is Working Properly
Finding and removing dead UA code is only half the job. The other half is making sure GA4 is collecting data correctly, because a broken GA4 install is the single most common finding in our audits. Log into your GA4 property and open the Realtime report while browsing your own site. If you see yourself as an active user, the collection is working. If you do not, something in the setup is broken, and your analytics have been dark since whenever the issue started.
Install the Google Tag Assistant Chrome extension and use it to run a check on your site. The extension will flag any legacy UA tags as deprecated and show you whether GA4 is firing correctly. Five minutes of checking here can save hours of debugging later.
Beyond confirming GA4 fires at all, you want to verify that the right events are being recorded. Conversion events do not port over automatically from UA, and GA4’s event model is structured differently than UA’s goal-based system. If you migrated and just installed the GA4 tag without rebuilding your conversions, GA4 may be collecting sessions but missing the events your team actually cares about for reporting.
What a Proper Migration Covers
If your check turns up a UA property ID anywhere on your site, the cleanup involves more than deleting a plugin. A proper migration means removing every UA reference from your theme, plugins, and tag manager. Google provides both manual and automated paths for switching conversion bidding from UA to GA4 in Google Ads if you have those connected.
On the GA4 side, conversion events, audience definitions, and remarketing lists all need to be rebuilt from scratch. Any custom dimensions your team relied on for reporting have to be set up fresh. Enhanced measurement, cross-domain tracking if your site spans multiple domains, and reconnecting GA4 to Google Ads and Search Console all need attention. Skipping any of these steps is how you end up with the half-migrated setups we see regularly, where GA4 is installed but the data structure looks nothing like what teams expect when they go to build reports.
One more thing before Google deletes UA data forever: export your historical Universal Analytics reports. Depending on how long your site ran on UA, that historical data may be the only record of multi-year performance trends. Once access is gone, recovery is not possible.
What Broken Analytics Does To Your SEO Strategy
Your marketing reports are only as trustworthy as the tracking underneath them. Dead or broken analytics feeds into your broader SEO health where GA4 conversion data drives Google Ads bidding, Search Console integrations, and audience targeting. If data coming into those systems is incomplete or citing a dead property, everything you do is working from a flawed foundation.
Legacy scripts also crush page speed that affect Core Web Vitals scores. Those requests still slow your page down even when they collect nothing. Keeping your tag environment clean is part of the same effort as performance optimization broadly, not a separate project.
If you want to know what is running on your site and whether your GA4 setup is reliable, our free SEO audit covers tracking health alongside your broader search visibility. We handle cleanup and rebuild projects regularly and can tell you quickly what your situation would take to fix.
