Fix guides

Each of these pages walks through one common cookie-banner failure — what the law requires, why it matters, and how to fix it. Pages are linked automatically from the failing checks on every banner report.

• Your site has no cookie banner ePrivacy requires informed consent before any non-essential cookie. No banner means no consent, which means every analytics or marketing cookie on the site is unlawful from the first page view.
• Your banner has no "Reject all" button The Irish DPC is explicit: refusing consent must be as easy as giving it. A banner with only "Accept" (or with Reject hidden behind "Manage options") is a dark pattern — the consent it collects is invalid.
• Non-essential cookies are being set before consent ePrivacy Article 5(3) makes it unlawful to store or read information on a visitor's device without prior consent — with narrow exceptions for strictly necessary cookies. A non-essential cookie existing before the banner is clicked is already a breach.
• Analytics or marketing scripts fire before consent Loading Google Analytics, Meta Pixel, or any other tracker before consent sends visitor data to third parties without a legal basis. The DPC treats the request itself as the breach — whether or not it also sets a cookie.
• Your "Reject all" button doesn't actually reject If Reject leaves tracking cookies in place — or adds new ones — the consent flow is misleading, and the legal exposure is the same as having no reject button at all. This often happens when third-party scripts ignore the CMP signal or when tag managers fire before the consent state propagates.

Not sure which applies to you? Run your site through the checker — the report will link directly to the fixes you need.