Cookie check · free · no sign-up

Check if your website
respects its cookie notice

Having the notice isn’t enough: cookies and trackers that aren’t essential have to wait until the visitor says yes. Enter your website’s address: we open your page without clicking anything and tell you what starts running before anyone decides.

Last updated: · By the Wakaris team

Possible results
  • Nothing starts before the decision

    The cookie notice appears and, while nobody answers it, no tracking tool starts running and no cookie that isn’t essential is saved.

  • Something starts before the decision, or there’s no notice

    Before the visitor answers, a tracking tool is already running or a non-essential cookie has already been saved; or the website uses cookies of that kind and no notice appears. The result tells you which of the three came up.

  • It couldn’t be determined

    For example, because the page only uses essential cookies (so there’s nothing to ask) or because it couldn’t be opened.

What it checks

It looks at three things: whether the cookie notice appears, which tracking tools are already running before anyone answers, and which cookies have already been saved.

Cookie notice

Looks for the notice that asks visitors whether they accept cookies. It’s only needed if the website uses non-essential cookies or tools; if it only uses essential ones (like the cart or language cookie), there’s nothing to ask and the result says so.

Trackers before consent

Opens the page like a first-time visitor who doesn’t click anything, and looks at whether any tracking tool from another company is already running: analytics, advertising or social media. If there’s even one, it shows up in the result.

Tracking cookies before consent

Notes the cookies the website saves in the browser before any click. If any of them isn’t essential (analytics or advertising cookies, for example), it shows up in the result.

What it doesn’t check: Whether the notice’s design nudges people to accept (colors, sizes, which button stands out): we look at what can be measured, not at whether the design is persuasive. Whether the wording of the notice or the cookie policy is legally correct: that’s a legal review, not a technical check.

Why it matters

The law doesn’t just ask you to have a cookie notice: it asks that nothing non-essential starts running before the visitor says yes. A flawless notice with analytics already running behind it is of little use: as far as the rules are concerned, it’s like having no notice.

There are also two very common findings that aren’t in the code but in the design: accepting takes one click and rejecting takes three, and options come pre-ticked. The rules require rejecting to be as easy as accepting and nothing to be ticked in advance. This check doesn’t measure those two (further down we tell you how to look at them yourself): it focuses on what is activated before the decision.

How to fix it, step by step

You don’t need to know anything about websites. The goal is simple: nothing that isn’t essential should start running until the visitor clicks “Accept”, and “Reject” should take the same effort.

  1. Look at what came up

    In the result you’ll see one line for each thing we look at: whether the cookie notice appears, whether a tracking tool from another company (analytics, advertising, social media) is already running, and whether non-essential cookies have already been saved.

    A ✓ means nothing was seen to point out on that visit; a ✕ or a ! means we did, with the details next to it when there are any; a – means it couldn’t be determined. Take a screenshot or copy what comes up: it’s what you’ll show whoever runs your website.

  2. If someone else or an agency runs your website

    You don’t have to touch anything: you just have to ask. Copy this message, paste what came up below it and send it to whoever built or maintains your website:

    Hi. I checked my website with Wakaris’s cookie checker (https://cookies.wakaris.com/en). When it’s opened without accepting or rejecting the cookie notice, it shows that either the notice doesn’t appear, or non-essential cookies or tracking tools are already loading (analytics, advertising, embedded videos or maps). Could you look into it so that:

    1. A cookie notice appears with “Accept” and “Reject” equally visible from the start.

    2. Nothing non-essential loads until the visitor accepts.

    3. No option comes pre-ticked.

    4. The choice can be changed later, for example from a link in the footer.

    Once it’s done, let me know and I’ll check it again on the same page. Thanks.

     

    What came up in the check:

     

    If they reply that “the notice already does that”, ask them to look without answering it: what matters is what happens before the visitor decides. If you run the website yourself, carry on with the next step.

  3. If you run it yourself, depending on your platform

    WordPress. The notice comes from a plugin, an add-on you install from the Plugins menu in the WordPress dashboard. If you don’t have a cookie plugin, install a well-known one, such as Complianz, CookieYes or Cookiebot. If you already have one, look in its settings for the option that blocks analytics, advertising, videos and maps until the visitor accepts (each plugin names it differently). Watch out for analytics added by another plugin or pasted into the theme: it has to wait too.

    Wix. Wix has its own cookie notice: turn it on in your website’s privacy and cookie settings. If someone added code by hand for analytics or advertising, check that it’s classed as analytics or advertising, not as essential, so it waits for the answer.

    Shopify. Shopify also has its own notice: turn it on in your store’s customer privacy settings, at least for the European Union. Apps you’ve installed (chats, reviews, advertising) can load their own tools: if one keeps showing up, ask its developer whether it respects the notice’s decision.

    Another platform. Look in your platform’s privacy or cookie settings: many have a built-in notice. If yours doesn’t, you can add one from a specialist service (they’re called consent management platforms, or CMPs).

    Custom-built website. This part is for whoever codes it: add a consent manager and make every analytics, advertising or social media tag load only if the visitor accepts, with everything denied by default. With Google Tag Manager, through Google’s Consent Mode. Embedded videos and maps, with a preview image that loads the real content when clicked.

  4. Check the notice yourself at a glance

    The check doesn’t measure this, but European data protection rules require it: the “Reject” button has to be visible from the start, just like “Accept”, without having to go into “Settings”; no box should come pre-ticked; and there has to be a way to change your mind later, for example a link in the website’s footer.

  5. Check it again here

    Once it’s done, type your website’s address again above. We keep each address’s result for 24 hours, so if you check right after the change you’ll see the old one: wait until they’ve passed and try again. If the same thing still comes up, forward the new result to whoever made the change.

Learn more

Frequently asked questions about cookie notices

What is a cookie and what is a tracker?

A cookie is a small file a website saves in your browser to remember something: that you’ve been there before, what’s in your cart or which language you use. A tracker is a tool, almost always from another company (Google Analytics, the Meta pixel, Google advertising), that records what you do on the website, often with its own cookies. If they aren’t essential for what you asked for, both need your permission before they start running.

Is having a cookie notice enough?

No. The notice only asks; what counts is what happens while nobody has answered. If analytics or advertising load at the same time as the notice, the cookies are already saved by the time the visitor reads the message. That’s exactly what this check looks at.

Can there be cookies before the notice is accepted?

Only the ones the website needs to work: the one that remembers your own cookie choice, the session one, the cart one or the language one. Everything else (analytics, advertising, maps, embedded videos, chats) has to wait until the visitor accepts. Loading Google Analytics before someone accepts is one of the most common findings.

Does the reject button have to be visible straight away?

Yes. European data protection authorities, including Spain’s (AEPD), require rejecting to take the same effort as accepting. A notice where accepting is one click and rejecting means going into “Settings” and unticking boxes is unlikely to collect valid permission.

Does continuing to browse count as accepting cookies?

No. The law requires the visitor to say yes with a clear action, such as clicking “Accept”. Scrolling, closing the notice with the X or moving to another page don’t count, and neither do silence or pre-ticked boxes. What this check does measure is whether anything is activated before the visitor decides.

Why have my analytics dropped after the change?

Because before, everyone was counted, with or without permission, and now only those who accept are. You haven’t lost visitors: what changes is how many you can measure. Google offers a measurement mode that, when the visitor rejects, sends data without cookies to narrow that gap.

This is one check. Wakaris runs 135.

The cookie notice is just one of the things the Legal specialty looks at. Wakaris analyzes your website across nine specialties (security, performance, accessibility, legal, SEO and more) and explains it clearly, without jargon. Free and without signing up.

No account, no card · Results in ~30 seconds