Skip to main content
All rules

SEO-012

No analytics detected

LowDefault severity · SEO / Quality · SEO, quality and performance

Last reviewed

What it checks

Script tags and inline code for common analytics tools.

Why it matters

Without analytics you cannot see which pages convert or notice when traffic suddenly drops after a deploy.

Recommended fix

Add a privacy-friendly analytics tool, and disclose it in your privacy policy.

How to verify

Visit the site and confirm the visit appears in the analytics dashboard.

Example fix prompt

Generic prompt (your report adds the evidence)
Please fix this production issue in my app.

Issue SEO-012: No analytics detected
Site: https://your-app.example

First confirm the issue in the code or live config. If it is not present, say so and change nothing.
Task: Add lightweight, privacy-friendly page analytics to the site (for example Plausible, Umami or the hosting provider’s built-in analytics), load it without blocking rendering, and mention it in the privacy policy.

Constraints: make the smallest change that fixes this, keep the current design and behaviour, never paste secret values into code or chat, and tell me which files you changed.
Done when: Visit the site and confirm the visit appears in the analytics dashboard.

References