Cookie consent bannerWhat it checks and how to fix it

What it checks

Uses an AI model to read the page's visible text and structure and decide whether it shows a cookie consent banner, in any language, and checks whether the page sets cookies. Passes when a banner is found or no cookies are set, warns only when cookies are set and the model is confident there is no banner, and skips when AI features are off for the project.

Why it matters

In the EU and the UK, and under several US state privacy laws, non-essential cookies such as analytics and advertising cookies need informed consent before they are set. A site that sets them without asking risks complaints and fines from data protection authorities. Strictly necessary cookies, like a login session, do not need consent.

How to fix it

Either stop setting non-essential cookies, or ask before you do.

• Avoid them: cookieless analytics (Plausible, Fathom, Simple Analytics) and self-hosted fonts and embeds often remove the need for a banner altogether.
• Ask first: add a consent management platform (Cookiebot, Usercentrics, OneTrust) or an open-source banner (Klaro, CookieConsent), and load analytics and ad tags only after the visitor accepts. Rejecting must be as easy as accepting.

With Google tags, set Consent Mode defaults before any tag loads, and update them from your banner:

<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){ dataLayer.push(arguments); }
  gtag("consent", "default", {
    ad_storage: "denied",
    ad_user_data: "denied",
    ad_personalization: "denied",
    analytics_storage: "denied"
  });
</script>

<!-- When the visitor accepts analytics: -->
<script>
  gtag("consent", "update", { analytics_storage: "granted" });
</script>

This is general guidance, not legal advice: which cookies need consent depends on the laws that apply to your visitors.