Tag Coverage and Tag Diagnostics: Finding the Pages You Are Not Measuring

A container snippet that fires on most pages reads like a working setup. It usually is not. Untagged pages are rarely the ones you visit. They come from a CMS template for a section nobody checks, a landing page built for one campaign, or a thank-you page a visitor only sees after paying.

Google keeps two tools for exactly this problem. The Tag coverage summary lists the pages Google has detected and reports whether your Google tag or Tag Manager container loaded on them. Tag Diagnostics scores the quality of that tag and lists the issues attached to it, including the ones that only affect part of the site. Both sit inside the Google tag settings, the same panel GA4 and Google Ads now send you to for consent and collection changes.

Neither tool is new, which is why so many accounts still carry an unread "Some of your pages are not tagged" warning.

Where both tools live

Four entry points reach the same panel. Google documents all of them:

• Google Ads: the Tools icon, then Data manager, then Manage under the "Google tag" heading.
• Google Analytics: Admin, then Data streams, then select the stream and click Configure tag settings. You need Editor or above at property level.
• Campaign Manager 360: Data manager under Floodlight, then Manage under the Google tag section.
• Google Tag Manager: the "Google tags" tab, select the Google tag, then Admin at the top, then Tag coverage under Tools.

Tag Diagnostics opens from the same panel: under "Your Google tag", in the "Tag quality" section, select View diagnostics. From there you choose which domains receive alerts, and you can stop monitoring a domain and turn it back on later.

What tag coverage measures, and what it does not

Google states the definition plainly, and it is the sentence to show a client who assumes a green tick means complete reporting: "The Google tag refers to the gtag.js snippet or GTM container that is installed on a page and not the individual tags that are part of a container's configuration."

Coverage answers one question only. Did the site load the snippet or the container on this URL? A page can be marked Tagged while your GA4 configuration tag, your Ads conversion linker or a custom event never fires on it. It is not a QA report, and tag-level checks still need Tag Assistant or a debug session.

The mechanics matter before you read the table:

• The summary holds up to 10,000 pages, in a Page details table with two columns, URL and Tag status.
• The URL column shows the domain and path only. Query parameters are not included.
• Three statuses. Not tagged means the page has never loaded your Google tag. No recent activity means it has not loaded the tag in the last 30 days but did before that. Tagged means it loaded the tag within the last 30 days.
• Cards above the table count the pages in each state, and clicking a card filters the list to that status.
• Pages with no tagging signals for 60 days are removed automatically, so the summary follows the live site.
• Where other tags were detected, the row shows the Google tag IDs found and whether the tag you have open is installed on the page.
• Status depends on enough traffic to produce a signal. A page you tag today can take up to 24 hours to update, and Tag Assistant gives you the real-time answer instead.

Working the list properly

The summary is only useful if the list reflects your site. Three controls do that work.

Add URLs. If the summary misses pages, add them by pasting a list or uploading a CSV formatted as URL and Included status, with entries such as example.com/2,no or example.com/3,yes. A header row is optional, each URL should be percent encoded, and the upload either overwrites the current list or merges into it. You can also download the summary as CSV and upload an edited version.

Ignore. Hover a row and click Ignore for pages that are not relevant to your site. Ignored pages drop out of the Tag Diagnostics view as well, and you can add them back later.

Filter. The filter menu covers Show all, Included, Suggestions, Added by you and Ignored. Search runs after the filter, so search inside a filtered view rather than against the whole list.

Treat the summary as a managed list. A staging domain or legacy subdomain left in it distorts the counts and buries the real gaps.

Tag Diagnostics: five statuses, one of them urgent

Tag Diagnostics monitors tag activity in real time across the top domain and any subdomains where the Google tag or GTM snippet is installed.

• Excellent: no issues detected and nothing outstanding to recommend.
• Good: no issues detected, but at least one recommendation that would improve tag quality.
• Needs attention: an issue that should be fixed, but not a critical one.
• Urgent: a critical issue requiring immediate attention. Google's example is a tag that was previously detected and has not been seen for 48 hours, which typically means data has already dropped to zero.
• No recent data: the Google tag has never been detected from your website.

The gap between the last two matters in a client conversation. Urgent on a tag that used to work is a deployment incident. No recent data on a tag that never worked is an unfinished implementation.

The diagnostics that matter most

The list is long. Grouped by what you actually do about them, it reads like this.

Coverage. "Some of your pages are not tagged" points at untagged pages on the site. "Some of your landing pages are not tagged" covers landing pages for ad creatives and Performance Max campaigns, which Google adds to the tag coverage report of the corresponding Google tag. Both send you to the coverage summary to find the URLs.

Placement and configuration. "Missing gtag config command" means the tag code is not configured correctly, and the fix is to place the configuration code immediately after the opening head tag on every page. "Config command out of order" covers event commands arriving before the config command, which changes how events are routed. "Missing Google tags" appears when event tags in GTM have no matching Google tag, and the fix is one Google tag for each measurement product. "Tag found too low on page" flags tags positioned far enough down the document to lose signals.

Consent, where UK accounts should look first. "Consent missing for EEA users", "Some pages missing consent for EEA users", "Consent mode installation out of order", "Website/App missing EEA consent for ads personalization", plus two 0% consent rate variants. The pattern is a consent setup that works on the main domain and fails on one template, subdomain or landing page builder. For a UK site serving EEA visitors that is a compliance finding, not only a data quality note.

The rest of the operational set. "Missing conversion linker" when a Floodlight or Google Ads tag has no conversion linker tag in the container. "Using legacy universal analytics tags" when pages still load GA4 through connected site tags, which blocks Google tag features such as enhanced measurement. "Content Security Policy blocks some resources" when a CSP does not allowlist Google's measurement endpoints. "Google tag is missing transaction ID" and "Your conversions may be overcounted" on multi-source conversion setups. "Only one administrator detected" and "Additional domains detected for configuration" round out the set, and Google notes that some of these roll out gradually.

Dismiss is a decision, not a fix

Some alerts do not apply to your implementation, and Google lets you clear them. Open the Diagnostics tab in the Google tag settings, use the three-dot menu on the action item, click Dismiss and pick a reason. Dismissed issues stop counting against the overall tag quality score and move below the active items. You can recover one from the bottom of the Tag quality section at any time.

Two details keep dismissal honest. Not every alert can be dismissed, and a dismissed item can resurface if conditions change, for example when more pages or users are affected. Dismissed items stay visible for 90 days. Record what you dismissed and why, because that note explains the gap when an alert returns six months later.

When "not tagged" is wrong

Google's documentation lists the false positives, and they are common enough to check before raising an alarm with a client:

• Low traffic: thank-you pages and other rarely visited URLs can be read as untagged because there is not enough volume to confirm the tag.
• Redirects: an http to www redirect can be flagged as its own untagged page.
• Trailing slashes: example.com/ and example.com can both appear, with one of them flagged.
• Capitalisation: example.com/ABC and example.com/abc can be counted as separate pages.

A fifth case comes from the field. Analytics Mania has reported that server-side setups serving gtm.js from a proxied domain instead of googletagmanager.com can be marked not tagged, because the scanner looks for standard Google endpoints. If you run a first-party proxy, check that before rebuilding a working implementation.

The response is the same in every case. Confirm the tag fires with Tag Assistant. If it does, the alert should clear within 24 hours. If the page genuinely should not be in the list, ignore it.

A coverage routine that holds up

1. Treat the coverage summary as part of every account review rather than a one-off exercise. Export the CSV for each Google tag you manage.
2. Filter to Not tagged first, then triage the list against redirects, trailing slashes and capitalisation variants.
3. Separate real gaps from reporting gaps. No snippet means a technical fix. Tags that never fire need a debug session.
4. Fix at the template level. Patching pages one by one guarantees the next CMS release reopens the same gap.
5. Re-check after 24 hours in the summary, or immediately in Tag Assistant if you need proof for a client.
6. Work Tag Diagnostics by severity, then treat the consent diagnostics as compliance items with a written decision attached.
7. Add coverage to the release checklist for the site. New templates and new landing page builders are where gaps appear.

Pair it with hostname filters

Coverage and diagnostics answer what is missing. They do not answer what is unwanted. Since September 2026 GA4 hostname data filters support an Include mode, so you can allowlist the domains you approve and drop everything else. Coverage tells you a legitimate page is invisible. A hostname filter tells you a staging domain or a spam referrer is talking to your property. Run both checks in the same session and the measurement picture closes.

The short version

Two tools inside the Google tag settings decide whether your reporting describes the site you think you have. Tag coverage lists the pages Google has detected, up to 10,000 of them, with three statuses and a 60-day expiry for silence. Tag Diagnostics scores quality across the domain and its subdomains, with five statuses and a list of issues that includes consent failures, misplacement and missing tags.

The trap is treating coverage as proof that your tagging is verified. It confirms the snippet or the container loaded, nothing more. Use it to find missing pages, Tag Assistant to confirm what fires on them, and the consent diagnostics to check those gaps are not compliance gaps.