Table of Contents
- 1 What Does the “Some of Your Pages Are Not Tagged” Warning Mean?
- 2 Does This Warning Mean You’re Losing GA4 Data?
- 3 What Should You Do About This Warning?
- 4 Scenario 1: The Page Should Be Tagged (But Isn’t)
- 5 Scenario 2: The Page Should Never Be Tagged
- 6 Scenario 3: False Positives (Extremely Common)
- 7 Wait 24 Hours After Fixing Anything
- 8 Final Thoughts from Incisive Ranking
If you’ve recently logged into Google Tag Manager and noticed a warning saying “Some of your pages are not tagged”, you’re not alone. This message has caused confusion for many marketers, analysts, and business owners — especially when everything seems to be tracking correctly.
At Incisive Ranking, we regularly audit GTM and GA4 setups for businesses, and this is one of the most common alerts we encounter. The good news? In most cases, it’s not as serious as it looks.
In this guide, we’ll explain what the warning really means, why it appears, and exactly what you should (and shouldn’t) do about it.
What Does the “Some of Your Pages Are Not Tagged” Warning Mean?
Inside the Google Tag Manager dashboard, there’s a section called Container Quality. If everything is fine, you’ll see a green status labeled Excellent. But if Google detects potential issues, it changes to Needs attention.
Clicking “View issue(s)” often reveals this message:
Some of your pages are not tagged
When you click “See untagged pages”, Google shows a Tag Coverage Summary, grouping URLs into four categories:
- Included pages – All pages Google has detected for your site
- Tagged pages – Pages where GTM or Google Tag loaded in the last 30 days
- Not tagged pages – Pages where Google believes no tag was detected
- No recent activity – Pages seen before, but not visited recently
If even one URL appears under Not tagged, the warning is triggered.
Where You’ll See This Warning in GA4
This isn’t limited to GTM.
You may also see similar diagnostics inside Google Analytics 4:
GA4 → Admin → Data Streams → Select Web Stream → Configure tag settings → Tag quality
The logic is the same — Google is checking whether your pages are consistently loading a tracking tag.




What Does “Google Tag” Mean Here?
This part is important and often misunderstood.
When Google refers to a Google Tag, it means either:
- A gtag.js snippet hardcoded directly into your website (commonly used for GA4 or Google Ads), or
- A Google Tag Manager container snippet installed on the page
👉 It does NOT evaluate individual GTM tags, triggers, or events.
Google is only checking whether some form of base tracking code exists on the page at all.
Does This Warning Mean You’re Losing GA4 Data?
In most real-world cases: No.
If your main landing pages, blog pages, and conversion pages are tracking properly, this warning often relates to:
- Old URLs
- Redirected links
- Low-traffic confirmation pages
- Non-HTML files (PDFs)
Think of this alert as a health check, not a live traffic report. It’s meant to highlight configuration gaps — not necessarily lost sessions.
What Should You Do About This Warning?
Based on our audits at Incisive Ranking, this warning usually falls into one of three scenarios.
Scenario 1: The Page Should Be Tagged (But Isn’t)
This is the only situation where action is required.
If You’re Using GA4 With Hardcoded gtag.js
- Copy one URL listed under Not tagged
- Visit tagassistant.google.com
- Click Add domain, paste the URL, and connect
- Open the site in the new tab and confirm Tag Assistant is connected
- In Tag Assistant, select your GA4 Measurement ID
- Check whether events like page_view are being sent
If events appear, GA4 is installed correctly and the warning is likely inaccurate.
If no events appear, the tracking code may genuinely be missing or blocked — this is where developer support may be needed.
If You’re Using Google Tag Manager
- Open your GTM container
- Click Preview
- Enter the affected page URL and connect
If preview mode connects successfully, GTM is installed and working.
At that point, you can safely mark the URL as Ignore inside the Tag Coverage report.
Scenario 2: The Page Should Never Be Tagged
Some URLs simply should not contain tracking scripts, such as:
- PDF or document files
- Admin panels (e.g., /wp-admin/, /login/)
- Internal tools or staging URLs
If you see these listed as Not tagged, there’s nothing to fix. Just mark them as Ignore.
Scenario 3: False Positives (Extremely Common)
This is where most of the confusion comes from.
Google’s scanner isn’t perfect, and several technical factors can cause tagged pages to be incorrectly flagged.
Common False Positive Triggers
| Scenario | Why It Happens | Recommended Action |
| Redirects | Google checks the original URL but sees the tag on the redirected version | Ignore |
| Trailing Slashes | /page and /page/ treated as different URLs | Ignore |
| Low Traffic Pages | Google hasn’t seen recent visits to confirm tagging | Verify & Ignore |
| Capital Letters | /Contact vs /contact duplication | Ignore |
| Backend URLs | Admin or login areas intentionally untagged | Ignore |
If the final URL loads GTM or GA4 correctly, the warning can be safely dismissed.




Wait 24 Hours After Fixing Anything
Google’s diagnostics do not update instantly.
If you:
- Add a missing GTM or GA4 snippet
- Fix a deployment issue
- Mark URLs as Ignore
You’ll need to wait up to 24 hours for the warning to refresh.
Once all legitimate pages are either tagged or ignored, the alert will disappear automatically.
Final Thoughts from Incisive Ranking
Google’s intention with this warning is good — it’s designed to prevent broken analytics setups. However, in practice, it often flags pages that don’t impact real-world tracking at all.
Our recommendation:
- Verify your core business pages
- Don’t panic over edge-case URLs
- Fix genuine deployment issues
- Ignore false positives confidently
If you’re unsure whether your Google Tag Manager or GA4 setup is truly correct, Incisive Ranking offers professional GTM & GA4 audits to ensure clean, reliable data you can trust.
👉 Clean data leads to better decisions. And better decisions drive growth.

