How to Add Google Analytics to Website: GA4 Guide

What it means to add Google Analytics to a website

Three separate pieces make up a working setup: a Google Analytics account that holds a GA4 property, a web data stream inside it that represents your domain, and the Google tag running on your pages. Visitors' browsers only ever see the last piece.

Keep the three ID formats apart, because people mix them up. The G- ID is the GA4 Measurement ID, and it is the one you paste into the tag or into a builder field. A GTM- ID belongs to a Google Tag Manager container, which is a different product. A UA- ID belonged to Universal Analytics, whose standard properties stopped processing hits on July 1, 2023, so an old UA snippet on a standard property collects nothing today.

You can paste the Google tag (gtag.js) yourself, or install a Tag Manager container once and manage every tag from its web interface.

In the browser, two inline lines create window.dataLayer and window.gtag, the library loaded from googletagmanager.com reads that queue, and each page view is sent to Google. By default GA4 also sets a first party _ga cookie that lasts two years.

Why add Google Analytics (and what it will not do for rankings)

Analytics shows which pages draw visits, which channels send them and where people leave. Before you rewrite titles or change content, you need a baseline to compare against, and the cheapest way to start collecting one is to install Google Analytics now, before anything else changes.

It will not move your rankings. Google publishes a ranking systems guide that lists the systems it uses to order results, such as link analysis and RankBrain, and analytics data is not among them. The tag changes what you can measure, not where you appear.

The standard version is free, and the one real cost is a little extra JavaScript on each page, which is why the steps below keep the async loader exactly as Google ships it.

How SEO Site Checker tests for Google Analytics

This is not an HTML scan. Our audit opens your URL again in headless Chromium, waits only until the DOMContentLoaded event and then asks the page one question. If that navigation fails, it retries once with the full load event, allowing 15 seconds per attempt.

The exact rule: after navigation, the report evaluates whether any of window.ga, window.gtag or window.dataLayer is set. It does not read your HTML source, watch network requests, inspect cookies or check the ID.

A normal GA4 tag passes, and so does a Tag Manager container with no Analytics tag inside, an old analytics.js stub with a UA ID, or an empty dataLayer array made by an unrelated script. Timing is where the check turns strict. In our fixture tests a tag defined in the head or on DOMContentLoaded passed, while one added by a two second timer failed, so a consent tool, delay JavaScript plugin or late Tag Manager trigger can fail a site that does track visitors.

Matomo and Plausible failed because they define none of the three globals. A page with only the async gtag.js script tag and no inline lines also failed, because the library was still loading when DOMContentLoaded fired. That setup is a race, not a sure fail.

A failed row counts against the score, which is the share of passed checks among all counted checks, and the status is never a warning. A page that does not finish loading within 15 seconds on either attempt fails too. A login wall, geo block or bot challenge fails because the checker sees that other page, which has no tag.

• Pass: one of the three globals exists when the check runs.
• Fail: none exists, or no usable page loaded.
• Not tested: the ID itself, whether hits reach your property, and duplicate tags.

Why a pass is not proof that data arrives

A typo in the ID, or a tag that belongs to the wrong property, still turns the row green. Only the Realtime report shows whether hits really arrive.

Run the free SEO report

How to add Google Analytics to your website step by step

These steps show how to add Google Analytics to website pages the way Google documents it, so you can set up Google Analytics cleanly. If a screen in your account looks slightly different, trust Google's own wording, because the interface changes more often than the underlying tag.

1. Create the property. Open analytics.google.com, create an account if you have none, then add a GA4 property with a name, time zone and currency. Choose Web as the platform and enter your domain, which creates the data stream.
2. Copy your ID and snippet. In Admin, open Data streams and select your web stream. The Measurement ID sits in the stream details, and under Google tag, View tag instructions, then Install manually, Google shows the full snippet.
3. Paste it into the head. Place the snippet, which is your tracking code, immediately after the opening head tag on every page. A shared header template is the safest single location, because you edit one file instead of fifty.
4. Publish and clear caches. Purge the cache plugin, the CDN and any server cache so visitors and our test receive the new HTML.
5. Confirm the data. Visit the site in another tab and look for yourself in the Realtime report, as described below. If your visit appears in Realtime, the tag works and every page that shares the template is covered. If it does not, check the cache step and the ID before touching anything else.

Google's GA4 setup guide covers the property and data stream screens and the Install manually path.

Option A: paste the Google tag yourself

This route needs access to your HTML or theme files, and the inline script is what makes the globals exist early. On a static HTML site, put the snippet in the shared include or layout. On PHP or template driven sites, add it to the header partial that every page uses, so a single edit covers the whole site.

Keep exactly one copy of the Google tag per page, with the async attribute on the loader line, because two GA4 copies count every page view twice. Delete any old UA analytics.js block instead of leaving it beside the new tag. It collects nothing today, it adds weight, and it keeps our check green even if the new tag is broken. On a single page app, put the snippet in the root index or layout, then check in the web stream that the Enhanced measurement toggle is on and that page changes based on browser history events are enabled. Click through two routes and watch Realtime.

Option B: use Google Tag Manager

Create a web container (the GTM container) and paste its snippet as high in the head as you can, with the noscript part right after the opening body tag. Container IDs start with GTM-, which is not your G- Measurement ID. Inside the container, add a Google tag that carries your G- ID and fire it on the Initialization All Pages trigger, which runs earlier than the plain All Pages trigger (All Pages also works). Test in Preview mode, then publish.

Our check passes the moment the container loads, even before the Google tag inside it is published, so confirm in Realtime too.

The GA4 snippet explained line by line

This is the standard structure of the Google tag, with a placeholder where your own ID goes. Copy the current version from your own install page rather than from this article, because Google may change it.

<!-- 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>

The async script loader fetches the library from googletagmanager.com without blocking the page. The dataLayer array is the queue, and the gtag function pushes whatever you give it into that queue. The config call starts measurement for your ID and records the page_view event.

Notice why our check passes. The inline lines define window.dataLayer and window.gtag while the HTML is still being parsed, before DOMContentLoaded and before the remote library finishes downloading. That is also why a partial paste is dangerous: copy only the first line and nothing defines the globals early. Google describes the placement on its Google tag install guide.

Add Google Analytics to WordPress, Shopify, Wix and other platforms

Most site owners who add Google Analytics to website builders never touch code, so the route depends on the platform. Google lists the steps for each content management system on its own setup page, which beats any menu path quoted here, because those labels change. Whatever the route, the goal is the same: the Google Analytics 4 tag must load on every page.

On WordPress the simplest path is the official Site Kit by Google plugin, which connects your Google account through a guided setup with no code edit. If you prefer to edit the theme, find out which one you run first with the WordPress theme detector, and use a child theme so an update does not erase your change. Without a plugin, hook a small function onto wp_head in that child theme, so the snippet prints in the head of every page. Pasting it into a parent theme file is the mistake to avoid, because the next update overwrites it.

Hosted builders usually ask for the G- ID alone, so copy it from the data stream details first. Shopify normally connects through its Google sales channel app instead, so follow the prompts there rather than hunting for a paste box.

How to check that Google Analytics is working

• Look at the source or the Console. Use view page source and search for your G- ID, or run !!(window.ga || window.gtag || window.dataLayer) in the browser Console, which is the same expression our report evaluates and prints true when any of the three exists. A Console run happens after loading finishes, so a late tag can read true there and still fail in the report.
• Watch Realtime. Open your site in another tab and look for yourself in the Realtime report. Realtime normally shows hits within a few minutes.
• Use Tag Assistant or the Network tab. Connect your URL in Tag Assistant and look for your ID under Google tags found. In Chrome DevTools, filter the Network tab for collect and look for a g/collect request that carries your ID.
• Be patient with reports. Standard reports lag behind Realtime, roughly 2 to 6 hours for intraday and about 12 hours for daily data in a typical standard property, so judge only after a day or two. An ad blocker hides your own visits, so test in a clean profile.
• Finish with the report. Run our free report and look for the green row. It confirms that the globals exist at the moment of the check; it does not confirm the ID, so keep the Realtime result as your proof.

Why Google Analytics is not detected on your site

If the report says Google Analytics was not detected, work down this list. Start with the quickest checks and work toward the slower ones.

• The tag is on the wrong template. The home page has it, but the URL you tested is a landing page builder page, a subdomain or a checkout with another template, and the check tests exactly the URL you enter.
• The tag loads too late. Consent tools, delay JavaScript plugins and late Tag Manager triggers push the globals past the check (see the timing note above). Keep the two small inline lines for dataLayer and gtag in the head. If your rules require the library itself to wait for consent, delay only the async loader line until consent is given; the globals still exist, so the check passes, and nothing is sent early.
• The paste was partial. The async script tag is there but the inline lines after it are missing (see the snippet section).
• An old UA snippet is installed. It still passes our check but has collected nothing on a standard property since July 1, 2023. Replace it with the Google tag.
• Cached HTML is being served. A page cache or CDN still delivers the version without the tag. Purge everything and test again.
• The page sits behind a gate. A login, geo block or bot challenge means the headless browser sees a different page, which has no tag, or never finishes loading within 15 seconds.
• It passes here but shows no data. If you see Google Analytics not working or no data in Realtime despite a green row, check the ID for typos and confirm you copied it from the right property. Also look for a duplicate tag, as covered under Option A.

Good habits after you add Google Analytics

• Keep it light. Use one copy and the async loader. If page load time or main thread work grows after the install, check JavaScript execution time and render blocking resources to find the cause.
• Respect consent. If visitors come from regions with consent rules such as GDPR and the ePrivacy Directive, use a cookie banner together with Google consent mode instead of removing the tag, and ask a qualified adviser about your own duties. This is not legal advice.
• Do the housekeeping. Add an internal traffic filter so your own visits stay out of the numbers, and link Google Search Console to see the queries behind organic visits. Mark actions that matter, such as a form submit, as key events. Keep a separate staging property so test traffic never pollutes production data.