A cookie banner is a statement. It tells each visitor what your website stores on their device, and asks what they agree to. Like anything else your business says in public, it should be true.
It is easy for a banner to stop being true, and usually nobody decided that it should. The banner was written once. The website moved on.
Two ways a banner goes wrong
It declares cookies the site does not set
A banner copied from a template, or left over from an earlier version of the site, lists tools you stopped using long ago: an old statistics service, a chat window that was removed two redesigns back. Your visitors are asked to decide about things that do not happen. Your website looks as if it follows people more than it does. And a long list teaches people to click whatever makes the banner go away.
It misses cookies the site does set
This is the more serious one. Someone embeds a video in an article. Someone adds a map to the contact page, or a booking tool to the services page. Each of these outside services can set its own cookies in your visitor's browser.
The person who added the video was thinking about the video. Nobody told the banner. Now your website stores something on your visitors' devices that your banner does not mention.
What the rules broadly ask
In the European Union the rule, in broad terms, is this. Storing information on a visitor's device, or reading it from there, needs the visitor's consent, unless it is strictly necessary for the service the visitor asked for. And consent has to be informed: the visitor must be told what they are agreeing to.
Countries apply this in their own ways. What it means for your website is a question for a lawyer or for your data protection authority, and nothing here is legal advice. One thing follows without any legal training, though. You cannot inform visitors about cookies you do not know you set.
Categories and consent, in plain words
A banner sorts cookies into groups, because nobody will decide on a long list one cookie at a time. The example on the Consent page shows three:
- Needed for the site to work. Always on. Think of the cookie that remembers what is in a basket, or that keeps someone logged in.
- Statistics. The visitor chooses.
- Outside services. The visitor chooses. These are the videos, maps and other things your pages embed from elsewhere.
Consent is the visitor's answer for each group that is a choice. The answer only means something if the list behind each group is right. A visitor who says no to outside services has decided nothing about a video cookie that the banner never listed.
How a scan finds what a site really stores
The reliable way to write the list is to look. A scanner opens your pages and records every cookie they set, including the ones that arrive with embedded videos, maps and other outside services. The list then comes from the website itself, and no longer from somebody's memory of what was installed.
This is what the scanner in Consent does. The free plan scans 5 pages every month and shows you what it found. Paid plans scan from 50 pages up and include a consent banner for your website. The banner lists the cookies the scanner found, so what you tell your visitors is what your site really does.
The number of pages matters because cookies arrive with content. A video embedded in one article sets its cookies on that article. A scan of the home page alone would never meet it.
What the scan leaves to you
A scan tells you what your website stores. It does not tell you whether you still want it to.
A first scan is a good moment for a clear-out. For every cookie on the list, ask who added the thing that sets it and whether anyone still uses it. Often the best repair for a cookie is to remove the tool behind it. A shorter true list is better for your visitors than a longer true one.
What your privacy pages say about each cookie, and how the rules of your country apply, also stay with you and your adviser.
Keeping the banner matched
A banner that is true today can be wrong next month. A new video, map or tool can bring new cookies. This is why Consent scans again: every month on most plans, every week on the plans for 5,000 pages and more. The next scan finds what was added.
The example report on the Consent page has a line worth copying into your own routine: new since last scan. In the example it reads 3 cookies, set by an embedded video. Each new cookie is a question for your team. Did we mean to add this? Does anyone still need it?
Two habits keep the gap small:
- Ask before you embed. When someone wants to add a video, a map or a new tool, ask what it stores on the visitor's device. Make that question part of the request. If your requests are kept in one place, it is easy to add.
- Read what is new after every scan. A cookie you did not expect is the scan doing its job.
You can also shorten the list from the other end. The statistics group is often there only because of a visitor counter. Counting visits does not have to involve cookies, and we cover what you still learn in Visitor numbers without cookies.
What the scanner and the banner do, and the plans by number of pages, are on the Consent page.
