How to Check if Google Analytics is Installed on a Website
Before you can trust your traffic data, you need to confirm your tracking code is actually working. Knowing how to check if Google Analytics is installed on a website is a foundational skill for any marketer, developer, or business owner. Whether you just launched a site, took over a client account, or suspect your analytics have gone dark, verification is the first step. Missing or broken tracking leads to blind spots in your data, wasted ad spend, and decisions based on incomplete information.
According to W3Techs (2024), Google Analytics is used by over 55% of all websites whose analytics tool is known, making it the most widely deployed web analytics platform on the internet. Yet a surprising number of installations are broken, duplicated, or misconfigured. This guide walks you through seven practical, proven methods to verify your setup.
There are seven reliable ways to check if Google Analytics is installed on a website, ranging from manual source code inspection to browser extensions and real-time reports inside GA4. Each method has different strengths depending on your technical access level and the complexity of the site. Use at least two methods together for confident verification.
⚡ Key Takeaways
- Always verify Google Analytics installation after any major site update or CMS migration.
- Browser extensions like GA Debugger give you real-time confirmation without touching code.
- Real-time reports inside GA4 are the fastest human-readable verification method available.
- Page source inspection works on any site without any tools, but has limitations on tag manager setups.
- Google Tag Assistant is a free, reliable Chrome extension that checks for correct tag firing.
- Third-party audit tools like BuiltWith can confirm GA presence even when you lack site access.
- Duplicate tracking tags inflate your session counts and distort all downstream reporting.
Why Verifying Your Google Analytics Installation Matters
A broken analytics setup is not just an inconvenience. It directly affects every data-driven decision your team makes. According to a Gartner report (2023), poor data quality costs organizations an average of $12.9 million per year. While that figure covers enterprise data broadly, the principle applies at every scale. If your GA tag is misfiring, you are optimizing campaigns based on fiction.
This is especially relevant if you are running professional SEO services or managing paid campaigns for clients. You need to know that conversions, bounce rates, and traffic sources are being recorded accurately before drawing any conclusions. Similarly, if you are working through our full-stack digital marketing services, verified analytics tracking is the foundation everything else is built on.
Let us go through each verification method step by step.
7 Ways to Check if Google Analytics is Installed on a Website
1. Inspect the Page Source Code Manually
The most direct way to check if Google Analytics is installed on a website is to look at the raw HTML source code of the page. This method requires no tools, no browser extensions, and no account access. It works on any website you can visit in a browser.
To do this, open the website in your browser and press Ctrl+U on Windows or Cmd+Option+U on Mac. This opens the page source in a new tab. Once there, press Ctrl+F (or Cmd+F) to open the find function and search for terms like gtag.js, UA-, G-, or analytics.js. If any of these strings appear in the source, Google Analytics is present on the page.
The older Universal Analytics format uses a tracking ID starting with UA-, while the newer GA4 format uses an ID starting with G-. If you are looking at a modern site, you are almost certainly looking for the G- prefix. The gtag.js script is the current standard implementation.
One important trade-off: this method does not tell you whether the tag is firing correctly. The code might be present but blocked by a script error, a Content Security Policy header, or a conditional load rule. It also will not reveal tags loaded through Google Tag Manager, since GTM loads tags dynamically after the initial HTML is parsed. If the site uses GTM, you will see a GTM container snippet but not the individual GA tag inside it.
Use this method as a first pass. If you find the tracking ID, proceed to a behavioral test like the Real-Time report to confirm it is actually sending data.
💡 Pro Tip: If you are checking a client site and find multiple GA tracking IDs in the source, that is a red flag. Duplicate tags inflate session counts and make all your metrics unreliable. Remove duplicates before analyzing any historical data.
2. Use Google Tag Assistant (Chrome Extension)
Google Tag Assistant is a free Chrome browser extension developed by Google. It is one of the most trusted tools to check if Google Analytics is installed on a website because it not only detects the presence of tags but also evaluates whether they are firing correctly and flags common configuration errors.
To use it, install the extension from the Chrome Web Store, then navigate to the website you want to check. Click the Tag Assistant icon in your toolbar and select “Enable” followed by refreshing the page. The extension will then display a list of all Google tags detected on the page, including Google Analytics (both UA and GA4), Google Ads, Google Tag Manager, and others.
Each tag gets a color-coded status: green means everything is working correctly, blue means the tag fired but with minor suggestions, yellow indicates non-critical issues worth reviewing, and red flags critical problems that are likely breaking your data collection. This layered feedback makes it far more informative than a raw source code check.
Tag Assistant also shows you the specific GA measurement ID being used, which is valuable when auditing client sites where you need to confirm the correct property is connected. This is particularly useful when you have recently migrated from Universal Analytics to GA4, as some sites end up with both old and new tags running simultaneously.
One limitation: Tag Assistant works on pages your browser can render normally. Password-protected pages, sites behind authentication walls, or pages that block crawlers may not return accurate results. For those situations, you will need a method that uses authenticated access to GA directly.
3. Check the Real-Time Report Inside GA4
If you have access to the Google Analytics property, the Real-Time report is the fastest and most definitive way to confirm the tag is collecting live data. This method tells you not just that the code is present, but that it is actively communicating with Google’s servers.
Log into your GA4 account at analytics.google.com and select the property you want to verify. In the left navigation, click Reports, then choose Real-time. Open the website in a separate browser tab and navigate to a few pages. Return to the Real-Time report and look for your session to appear. If you see active users, page views, or events appearing within a few seconds, your installation is working.
This method is especially useful after making changes to a site. For example, if you recently migrated to a new CMS or updated your theme, the Real-Time report gives you immediate confirmation that tracking survived the change. According to Statista (2023), 38% of websites were rebuilt or significantly updated within a two-year period, meaning periodic verification is not optional, it is routine maintenance.
The trade-off is that you need editor or viewer access to the GA property. If you are checking a competitor’s site or a site where you have no account access, this method is not available. You will also want to make sure you are not triggering your own data in a way that skews reports, which is why using an incognito window or filtering your IP address in GA settings is good practice during testing.
For teams managing SEO and content performance, checking on how page content analysis connects to SEO efforts becomes much easier once you have confirmed your analytics tracking is reliable.
4. Use the BuiltWith Technology Profiler
BuiltWith is a web technology lookup service that scans websites and reports the tools and scripts they use, including analytics platforms. It is particularly useful when you need to check if Google Analytics is installed on a website without having direct access to the site’s code or GA account.
To use it, visit builtwith.com and enter the URL of the site you want to check. BuiltWith will return a detailed technology report that includes the analytics section. If Google Analytics is installed, it will appear there along with the version (UA or GA4) and sometimes the measurement ID.
This method is excellent for competitive research. If you want to understand what analytics stack a competitor or a site in your niche is running, BuiltWith gives you that visibility without any access credentials. It is also useful for agency audits when a new client is not sure what tools are installed on their own site.
The trade-off is that BuiltWith relies on crawl data, which may not be perfectly current. There can be a lag between when a tag is added or removed and when BuiltWith reflects that change. For active verification where you need real-time confirmation, pair this method with the Real-Time report or Tag Assistant. BuiltWith is best used for discovery, not definitive confirmation.
Similar tools include Wappalyzer (available as a browser extension and a standalone tool) and SimilarTech. Both work on comparable principles and can serve as cross-references when BuiltWith results are ambiguous.
💡 Pro Tip: BuiltWith is also a useful tool before you start a new website project. Seeing what your competitors use for analytics, tag management, and conversion tracking can inform your own tech stack decisions from day one.
5. Use Google Tag Manager’s Preview Mode
If the website uses Google Tag Manager (GTM) to deploy its Google Analytics tag, inspecting the page source will only reveal the GTM container snippet, not the GA tag itself. In this case, GTM’s built-in Preview Mode is the right tool to verify that the GA4 configuration tag is firing as expected.
To access Preview Mode, log into your Google Tag Manager account at tagmanager.google.com and select the correct container. Click the Preview button in the top right corner. A new tab will open where you enter the URL of the site you want to debug. GTM will then launch the site with a debug panel visible at the bottom of the screen.
The debug panel shows every tag that fired on each page, the triggers that activated them, and the variables that were passed. If your GA4 Configuration tag appears in the “Tags Fired” section, your analytics tracking is working through GTM. If it shows up under “Tags Not Fired,” there is likely a trigger configuration issue that needs to be resolved.
This is the most technically thorough method available for GTM-based deployments. It shows you exactly when and why each tag fires, which makes it invaluable for troubleshooting. For example, if your GA4 tag is only supposed to fire on specific pages or after specific user actions, Preview Mode lets you walk through those scenarios and confirm the behavior is correct.
The main limitation is that you need GTM editor access. This method is not available for external audits or competitor research. It is, however, the gold standard for internal QA before any major site launch or campaign activation. If you are working on a WordPress-based web project, GTM Preview Mode should be part of your pre-launch checklist.
6. Check Using Browser Developer Tools (Network Tab)
The browser developer tools, available in Chrome, Firefox, and Edge, give you a live view of every network request a webpage makes. This is one of the most technically reliable ways to check if Google Analytics is installed on a website because it confirms whether the browser is actually sending data to Google’s collection servers, not just that the script is present in the HTML.
To use this method, open the website and press F12 to open developer tools. Click the Network tab and then reload the page. In the filter bar, type collect or gtag or analytics. If GA4 is properly installed and firing, you should see network requests going out to endpoints like https://www.google-analytics.com/g/collect. For Universal Analytics, the endpoint was www.google-analytics.com/collect.
When you click on one of these requests, you can inspect the payload and headers. This shows you the measurement ID, the event type being sent, and various parameters like page title and session data. This level of detail is particularly useful for debugging custom events or verifying that ecommerce purchase events are passing the correct revenue values.
The trade-off is that this method requires a basic understanding of browser network requests. For non-technical marketers, interpreting what they see can be confusing. However, even a basic check, specifically looking for the collect endpoint appearing in the network log, is enough to confirm GA is sending data. If you see those requests, the tag is working. If the network log is empty of any analytics-related requests, the tag is either missing or blocked.
This method pairs naturally with understanding broader tracking and indexing issues. If you are curious about why certain pages may not be receiving traffic or data, our deep dive on why Google might not be indexing your pages offers context on related tracking and visibility challenges.
7. Run an Audit with a Third-Party SEO Tool
Several professional SEO and site audit platforms include checks for Google Analytics installation as part of their standard technical audit modules. Tools like Screaming Frog, SEMrush Site Audit, Ahrefs Site Audit, and Sitebulb will crawl your website and flag pages where the GA tag is missing, mismatched, or duplicated.
To use this method in Screaming Frog, configure a custom extraction rule to search for your GA measurement ID across all crawled pages. In SEMrush and Ahrefs, the site audit will automatically flag pages that are missing analytics tags as part of their technical health score. These tools are especially useful for large sites where manually checking individual pages is not practical.
According to HubSpot’s State of Marketing Report (2024), 61% of marketers say improving SEO and growing their organic presence is their top inbound marketing priority. That priority depends entirely on having accurate data, which means a thorough analytics audit is not optional for serious SEO work. Running a crawl-based audit catches issues that single-page checks miss, such as a GA tag that is present on the homepage but missing from blog posts, product pages, or landing pages.
These tools also help you identify if you have the wrong tracking ID on certain sections of the site, which can happen after migrations or when different teams manage different parts of the site. For ecommerce sites especially, this kind of comprehensive coverage is critical. You need conversion tracking to fire on every relevant page, not just the homepage.
If you are managing SEO for a business and want a reliable analytics foundation alongside your optimization work, pairing a tool-based audit with our local SEO packages ensures your data and your rankings strategy are both working from solid ground. Understanding what your analytics tell you about user behavior also connects directly to strategies you can explore in boosting SEO through page content analysis.
💡 Pro Tip: Run a full site crawl audit every time you push a major update, change themes, or switch tag management platforms. A tag that was working last month may be silently broken today.
Comparison of All 7 Verification Methods
| Method | Requires Site Access | Requires GA Account | Detects GTM Tags | Best For |
|---|---|---|---|---|
| 1. Page Source Inspection | No | No | No | Quick first check |
| 2. Google Tag Assistant | No | No | Yes | Tag health check |
| 3. GA4 Real-Time Report | No | Yes | Yes | Live data confirmation |
| 4. BuiltWith | No | No | Partial | External/competitive audit |
| 5. GTM Preview Mode | Yes (GTM) | No | Yes | GTM-based tag debugging |
| 6. Browser Dev Tools | No | No | Yes | Network-level confirmation |
| 7. SEO Audit Tools | No (crawl-based) | No | Partial | Site-wide coverage |
Practical Action Plan
- Do This Now: Open your site and run a page source check combined with the GA4 Real-Time report. These two methods together give you fast, reliable confirmation that your tracking is live. If either check fails, move immediately to GTM Preview Mode or Browser Dev Tools to find the problem.
- Worth Doing: Install Google Tag Assistant in your browser and run it on your key landing pages, especially any pages tied to paid campaigns or conversion goals. Also run BuiltWith on your own domain to see what an external observer would find.
- Low Priority: Set up a scheduled crawl with an SEO audit tool to scan for missing GA tags across your entire site. This is valuable but less urgent than confirming your primary pages are tracked. Schedule it monthly or after any major site update.
How This Connects to Broader SEO and Marketing Performance
Verifying your analytics is not just a technical checkbox. It is the foundation of every marketing decision you make. When your GA4 data is accurate, you can track which content drives conversions, which channels bring qualified traffic, and where users drop off in your funnel. Without that data, your entire strategy runs on guesswork.
If you are building organic traffic and want to understand what content performance looks like in practice, reading about key SEO strategies for Google News ranking gives useful context on how content and analytics interact. Similarly, if you are curious about how AI is changing the way search data is gathered and interpreted, our breakdown of Google AI Mode versus AI Overviews is worth reading alongside your analytics audit work.
For ecommerce sites especially, accurate analytics is non-negotiable. If you are comparing platform options, our WooCommerce vs Shopify comparison includes notes on how each platform handles analytics integration, which directly affects how easy it is to verify your setup. And if you are thinking about how local search visibility ties into your data strategy, our guide on local AEO best practices for small businesses is a natural companion read.
Conclusion
Knowing how to check if Google Analytics is installed on a website is a skill that pays dividends every time you make a data-driven decision. Whether you use page source inspection, Google Tag Assistant, the GA4 Real-Time report, BuiltWith, GTM Preview Mode, browser developer tools, or a full SEO audit tool, each method has a specific role. The best approach is to use two or three together, especially after site changes or campaign launches, to be confident your data is complete and accurate.
Do not let unverified tracking undermine months of optimization work. Spend ten minutes confirming your setup today and save yourself from chasing insights that were never real to begin with.
Frequently Asked Questions
Can I check if Google Analytics is installed on a competitor’s website?
Yes. Methods that do not require account access, such as BuiltWith, Wappalyzer, page source inspection, and Google Tag Assistant, all work on any publicly accessible website. You will be able to see whether GA is present and often which property ID is being used, though you cannot access their actual data or reports.
What is the difference between a UA tracking ID and a G- measurement ID?
UA- IDs belong to Universal Analytics, the legacy version of Google Analytics that was sunset in July 2023. G- IDs belong to GA4, the current standard. If you still see UA- tags firing on a site, they are no longer sending data to Google’s active servers and need to be replaced with GA4 tags immediately.
Why does my GA tag appear in the source code but no data shows in the Real-Time report?
Several reasons can cause this. The script may be blocked by a browser extension like an ad blocker on your test device, there may be a JavaScript error preventing the tag from executing, a Content Security Policy header may be blocking the outbound request, or your IP address may be filtered in the GA property settings. Use browser developer tools to check the network tab for blocked or failed requests.
Can I have Google Analytics installed through both GTM and a hardcoded script at the same time?
Yes, and it is a common mistake. When this happens, every pageview and event is counted twice, inflating all your metrics. If you migrate to GTM, remove the hardcoded GA script from your site’s theme or template. Use Google Tag Assistant to check for duplicate tags before relying on any data.
How often should I verify that my Google Analytics installation is working correctly?
At minimum, verify after any CMS update, theme change, plugin update, tag manager container publish, or major content migration. For high-traffic or ecommerce sites, a monthly audit using an SEO crawl tool is a reasonable baseline. For critical conversion pages, a weekly Real-Time check takes less than two minutes and catches problems before they distort your reporting for an entire month.
