Can your analytics tags cover the pages you need?
It separates missing analytics, consent-gated tags, opaque containers and measured coverage gaps.
What Check Engine measures
The check uses trackers found in server responses and available browser output. Tag-manager-only setups, tags waiting for consent and recognised built-in analytics receive their own explanations. Comparable readable pages are checked for a tagged share below 0.85. Uneven browser coverage can prevent a fair comparison. Retired Universal Analytics tags are checked separately, with different wording when another analytics tool is present. For example, comparable tagged coverage of exactly 0.85 does not fall below the gap threshold.
The check uses detected tags, code waiting to load, platform clues and measured browser coverage. It cannot access an analytics account. Check visits and conversions inside the intended service.
How to read the result
Several missing-tag or coverage findings are high severity. Unclear containers or platform limits can produce notices. A retired tag can be low when another tool is present. Read which tag was found and where it was found.
Why it matters
Finding a tag in HTML shows that it was installed. Event delivery and data quality need their own checks inside the analytics service. Use the named tag to decide what to test next.
How to fix it
Confirm the analytics tool the business intends to use. Review the named tag and affected templates, checking consent and rendering before adding scripts. Use the tool's own live or debug view to verify events. Remove obsolete tags carefully and retest representative page types after changing shared code.
'You have no analytics' is a claim about a list
What we found in field audits
Problems in Tracking & campaign readiness were found on 14 of the 14 sites we audited. These are area totals. Read the field-audit method.
Method note
backend/seo_engine/checks/martech.py, analytics, revision 0bb8e8d3.
Common questions
What analytics coverage avoids the missing-tag share finding?
Comparable tagged coverage at 0.85 passes. Browser coverage must be fair enough for the comparison to be made.
Can uneven browser coverage stop an analytics comparison?
Yes. Uneven browser coverage can make pages incomparable. The audit should not infer missing tags from unequal observations.
Are retired analytics tags always a high-severity problem?
No. When another tool is present, a retired tag can receive low severity. Review the named tracker and where it appeared.