How to Remove Google Analytics From Your Site 2026

Step zero: inventory every place the tag can live

Before you touch anything, list where Google Analytics is loaded. The tracker is the same library whichever way it arrives, so the goal is to find every loader. Open your site in a private window, open DevTools, switch to the Network tab and filter for googletagmanager, google-analytics and collect. Whatever shows up is your evidence; the table below tells you where to look for the source.

Write the list down with the owner of each item. On a site with an agency or several developers, the container and the plugin are often managed by different people.

Export what you need before you remove anything

Removing the tag does not delete your history, but it stops adding to it, and the property's data is subject to Google's retention settings. Decide now what you want to keep and export it while the property is still receiving data. Our guide to exporting your GA4 history covers the options in detail; the short version is below.

• Standard reports as CSV or spreadsheets: the top pages, sources and country reports for each year you want to compare against. These are aggregate and keep working after the tag is gone.
• Event-level data: the free BigQuery export, if you linked it before now, keeps event rows outside Google Analytics. Linking it today only captures data from the link date forward.
• Conversion definitions: screenshot or write down your key events and goals, so you can recreate the important ones as custom events later.
• Audiences and Ads links: note what Google Ads imports from the property. Removing the tag ends that feed.

Nothing from GA4 carries over into GhostMetrics automatically; the new tool starts counting from the day you install it. That is why running both for a couple of weeks, as described in our migration guide, is worth it if you need a continuous baseline.

How to remove Google Analytics, step by step

1. Record a baseline. Screenshot the last 28 days of pageviews, top pages and top sources in your current tool. You will compare orders of magnitude later.
2. Remove it from the tag manager first. If the tag fires from a container, pause or delete the Google Analytics tag (the "Google tag" or GA4 configuration tag), plus any GA4 event tags that depend on it. Publish a new container version with a clear name such as "Remove GA4". Leave the container itself installed until you have checked what else it runs.
3. Deactivate plugins and theme fields. Deactivate the analytics plugin, then delete it once you confirm nothing else needs it. Clear any "tracking ID" field in theme or builder settings. Do the removal in a staging copy if you have one.
4. Delete hard-coded snippets. Search your templates for the lines below and remove the whole block, not only the config call.
5. Remove server-side tags. If you forward events through a first-party tagging host, disable the Google Analytics client and tags there too, or the server keeps sending data for any request that still arrives.
6. Take down the consent banner if analytics was its only job. If the banner only existed to gate Google Analytics, remove it. If it also gates ads, embeds or other cookie-setting scripts, keep it and take Google Analytics out of its categories. See the consent section below.
7. Purge caches. Clear your CMS cache, your CDN cache and any page-builder cache, or visitors will keep receiving the old head.
8. Verify in DevTools using the table later on this page.

The blocks to search for in templates look like this:

<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>

On a WordPress site that adds the tag from a theme function, the hook to delete or comment out is the one that prints into wp_head:

// functions.php - remove or comment out the hook that prints the tag
// add_action('wp_head', 'my_theme_print_gtag');

Static sites built with Hugo, Jekyll or Astro usually keep the snippet in a head partial or base layout; search the repository for gtag and googletagmanager, remove the matches, rebuild and redeploy.

The consent banner: what changes and what does not

Cookie-based analytics generally requires consent in the EU and UK, which is why most Google Analytics installs come with a banner. Once Google Analytics is gone and nothing else on the page sets non-essential cookies, the reason for the banner may go with it. That depends on everything else the site loads, so audit before you delete.

• Check what else sets cookies. Reload the site with the banner dismissed and look at Application, then Cookies in DevTools. Ads, embedded video, social widgets and chat tools each set their own.
• Keep the banner if anything non-essential remains. Remove only the Google Analytics entry from its categories.
• Do not treat this as legal advice. Whether a site needs a banner depends on its jurisdiction and everything it loads. Our guides on whether you need a cookie banner and analytics without a consent banner explain the reasoning and where it stops.

GhostMetrics sets no cookies and does not use localStorage; its only browser storage is a per-tab counter and the session's first-touch UTM values in sessionStorage. If analytics was the sole reason for your banner, you may be able to drop it after the swap. If it was not, the banner stays.

What happens to the GA4 property afterwards

Removing the tag from your site stops new data from arriving. It does not delete the property, your reports or your linked products. The property stays in your Google account until you delete it yourself, and data it already holds follows Google's retention settings. Check the current Google Analytics documentation for how property deletion works and whether a deleted property can be restored, because Google changes the details and this page does not quote timelines.

A sensible sequence is: remove the tag, wait until your exports are verified against the originals, unlink anything that still points at the property, and only then decide whether to delete it. Keeping an idle property costs nothing and keeps your reports readable. If the property has Google Ads linked, move any conversion imports to a different source before removal, or those imports stop.

Mistakes that leave Google Analytics running

Most failed removals come from the same handful of oversights. Each one is easy to check once you know it exists.

• Removing the config call but not the loader. Deleting gtag('config', …) while leaving the gtag.js script means the library still downloads on every page, which wastes bytes and still shows up in the Network tab. Remove the whole block.
• Forgetting the noscript half of a tag manager snippet. A container install has a script in the head and an iframe inside a noscript element after the opening body tag. Removing one half leaves the other.
• Leaving a second property ID behind. Sites that were migrated from Universal Analytics, or built by more than one agency, sometimes carry two measurement IDs. Search for every G- and UA- pattern, not just the one you know.
• Cached templates. A page cache or CDN can serve the old head for hours after the source is fixed. Purge, then re-test in a private window, since a logged-in admin session can bypass the cache and mislead you.
• Plugins that re-inject the tag. An SEO, ecommerce or page-builder plugin may carry its own Google Analytics field. Check the integrations screen of every plugin that touches the head.
• Embedded third-party pages. A booking widget, a checkout or a hosted landing page on another domain loads its own tag. You can only remove what you control; list the rest so nobody is surprised when it shows in an audit.
• Dropping the consent banner too early. If the banner also covers ads or embeds, removing it creates a new problem while solving the old one.

Run the DevTools checks on at least one page of each type: the home page, a blog post, a checkout or contact page and any page built on a different template. A single template that still loads the tag is enough to keep collecting data, and it often hides on the pages you visit least.

Install the replacement and verify the result

With Google Analytics gone, add the replacement. GhostMetrics is one tag in the head, on any host, with no plugin and no build step:

<script defer src="https://ghostmetrics.nullagency.io/gm.js" data-site="YOUR-SITE-ID"></script>

Create the site in the dashboard to get your site ID. Static-site and framework placement is covered in our guide to adding analytics to a static site, and WordPress owners can follow analytics on WordPress without Google. Then confirm the whole change worked:

If your own visit does not show up, check that Global Privacy Control or Do Not Track is not enabled in your browser, since the tracker honors both and collects nothing. Our guide to testing your analytics install walks through the other common causes. After a day of traffic, compare orders of magnitude with the baseline you recorded in step one; the totals will not match exactly, because tools differ on bot filtering, blockers and consent. If you are still choosing a replacement, our GA4 alternatives comparison lays out the options.

FAQ

Keep reading

Disclosure: GhostMetrics is built by Null Agency and we use it on this site, so we are not a neutral party about our own product. Google's products and terms change; check Google's current documentation before deleting any property or relying on a retention period.