The best cookie banner is the one you do not need

What actually triggers one

Not cookies in general. The ones that matter are those used to track behavior, build a profile, or feed an advertising network.

A cookie that keeps somebody logged in, or remembers what is in a basket, is treated differently because the visitor asked for that function.

So the question is never do I have cookies. It is what did I load onto my own page, and what does it do.

The distinction that matters is purpose rather than technology. A cookie remembering a language choice the visitor made is not the same thing as one building a profile across sites, and the rules treat them differently.

Where they come from on a small site

Almost always from something added for a good reason. An analytics tag. An embedded video. A map. A chat widget. A social feed.

Each of those loads from another company, and several of them set a tracking cookie the moment the page opens.

Owners are often surprised, because they never chose a cookie. They chose a video, and the cookie came with it.

• An analytics tag added once and never reviewed
• An embedded video, which usually sets a cookie on page load
• A live map rather than a static image and a link
• A chat widget keeping the conversation between pages
• A social feed or a follow button
• A review badge or trust seal loaded from the issuer
• An advertising pixel left over from a campaign that ended

The cleanest answer

Do not set them. Count visits on the server instead of in the browser. Link to a video rather than embedding one. Show an address and a link rather than a live map.

You lose a little convenience and you gain a page that loads faster, needs no banner, and has nothing to explain.

The default here is to add nothing to a visitor's browser, so a site can genuinely ship with no banner at all.

It is also the fastest page. Every embed removed is a connection the browser does not open, which is the point made from the speed side in page speed and search.

If you do need one

Ask before loading, not after. A banner that appears while the tracker has already run is asking permission for something that happened.

Make refusing as easy as accepting. One click each, same size, same prominence. A large accept button beside a faint link is the pattern regulators single out.

Say plainly what each choice does, and let somebody change their mind later from a link in the footer.

What a banner does not do

It does not replace a privacy policy. It covers one narrow decision at one moment.

It also does not make tracking invisible to the reader. Many people now decline by habit, which means analytics on a consent banner shows a partial picture.

If your numbers matter to you, that is another argument for server side counting that needs no consent at all.

The accessibility trap

Banners are a common keyboard trap. Focus moves into the box and cannot get out, so the whole site is unreachable for anybody not using a mouse.

Test yours. Load the page, press tab, and try to accept, decline and escape using only the keyboard.

Every page written by Website Builder Studio passes a check that runs before anything publishes, validated against Google Search Essentials and modern web standards, and a third party banner script sits outside that check.

Test yours with the keyboard alone: load the page, press tab, and try to accept, decline and escape. A banner that traps focus makes the whole site unusable for anybody not using a mouse.

How to decide

List every third party thing your pages load. For each one ask whether it earns the banner it brings with it.

Usually two or three do the work and the rest were added once and forgotten. Removing those is faster than configuring consent for them.

Nothing here is legal advice, and rules differ by where your visitors are. The general principle holds: collect less and you have less to explain.

Work from a list rather than from memory. Open the developer tools, look at what the page actually requests, and decide each one on its merits — the method set out in third party scripts.