A compliant cookie banner in 2026: what regulators check and the most common mistakes

calendar_today September 5, 2026
A compliant cookie banner in 2026: what regulators check and the most common mistakes

The Italian data protection authority's guidelines on cookies date from 10 June 2021 and are still the reference text. What has changed in recent years is enforcement: the most recent decisions, such as the one of 27 February 2025 on a non-compliant banner, show precisely what gets contested, and in 2026 European authorities have declared the "educational" phase over. This article gathers the requirements, the mistakes we see most often and a checklist to use on your site.

The banner requirements according to the regulator

A compliant banner must meet all of these points, not some of them.

  • It must have a control to reject all non-technical cookies, with the same visual prominence as the one to accept: same size, same contrast, same position in the banner.
  • The X to close must count as a refusal: closing the banner without choosing cannot install any non-technical cookie.
  • It must allow a choice by category: statistics, marketing, functional, with the option to accept some and refuse others.
  • No pre-ticked boxes: consent must be a positive action by the user.
  • Scrolling the page is not consent, except in very specific cases the regulator has narrowed down.
  • The cookie wall, that is blocking access to the site for those who do not accept, is forbidden, with limited exceptions.
  • If the user refuses, the banner must not reappear on every page nor before six months, unless something substantial changes.
  • It must be possible to withdraw or change the choice easily, from every page, for example with a link in the footer.
  • It must link to an up-to-date cookie policy listing the cookies actually present.
  • Before consent no non-technical script must run: this is preventive blocking.

The seven mistakes we find most often

Konsento's free scanner analyses dozens of sites every day. These are the mistakes that come back most frequently.

The banner is there, but scripts run first. It is the most widespread mistake and the most serious: Google Analytics, the Meta pixel or a YouTube video write their cookies while the banner is still open. For the regulator this equals having no banner.

The hidden Reject button. A grey link, small text, a button that appears only on the second level: the regulator and the European task force on banners classify them as dark patterns.

No consent log. The banner collects the choice but does not keep it. When you need to prove consent, there is nothing to show.

Generic or outdated cookie policy. It lists cookies that are no longer there and does not list the ones added with the latest plugin. A policy that does not match the site's reality is not a notice.

Consent Mode v2 missing. Anyone using Google Ads without Consent Mode v2 loses data and, if Google tags run before consent, also breaches preventive blocking.

Unblocked iframes. YouTube videos, Google maps, embedded social posts: they load third-party cookies and must be blocked until consent like any script.

Banner in a single language on multilingual sites. A user reading the page in English who finds the banner in Italian is not informed in an understandable way.

The fines

The GDPR provides for fines of up to 20 million euros or 4 percent of worldwide annual turnover. For a small Italian company the regulator's decisions generally sit between a few thousand and a few tens of thousands of euros, with higher amounts in serious or repeated cases. On top of the fine come the order to comply by a deadline, the time spent handling the proceedings and the publication of the decision, which anyone can look up.

Ten-point checklist

Use this list on your site, in a private window.

  • The banner appears on the first visit and installs no non-technical cookies before a choice.
  • Accept all and Reject all have the same prominence.
  • The X closes without installing anything.
  • I can choose by category.
  • No box is pre-ticked.
  • Scrolling the page does not make the banner disappear as if I had accepted.
  • After refusing, the banner does not reappear on the next page.
  • The footer has a way to change the choice.
  • The cookie policy lists the cookies I actually see in the developer tools.
  • If I use Google Ads or Analytics, Consent Mode v2 is active and starts in the "denied" state.

If you cannot answer one of these points, the free scanner checks it for you in thirty seconds: konsento.cloud/en/verifica-conformita.

How Konsento solves it

Konsento was built to meet these requirements without you having to know them: the banner has equivalent Accept and Reject and a choice by category, blocks scripts and iframes until consent, logs every consent in a searchable and exportable archive, generates privacy and cookie policy from the cookies found by the scanner, sets Consent Mode v2 and speaks six languages. When the guidelines change, it updates itself. All for a one-time payment of 86 euros per domain, with no subscription. You can try it free for 15 days: konsento.cloud/en/register.

arrow_back Torna alle News