Most cookie banners on small business websites are copied from somewhere else and are wrong in one of two directions: asking for consent that is not needed, or setting trackers before anyone agrees. Both are worth fixing, and the fix usually makes the site nicer to use.
What needs consent
Under UK and EU rules, you need consent before storing or reading anything on someone’s device that is not strictly necessary for the service they asked for.
Does not need consent: a session cookie that keeps someone logged in, a basket, a load balancer cookie, a cookie remembering that they already dismissed a banner, a CSRF token.
Does need consent: analytics, advertising pixels, heatmaps and session recorders, embedded video that sets tracking cookies, anything that follows someone across sites.
The common mistake is assuming analytics is exempt because it is “just statistics”. In the UK and EU it is not.
What a compliant banner looks like
- Reject is as easy as Accept. Same prominence, same number of clicks. A greyed out “Manage preferences” link next to a large Accept button does not qualify.
- Nothing non-essential fires before a choice is made. Plenty of banners ask politely while the pixel has already loaded.
- The choice is recorded and respected on later visits.
- There is a way to change your mind afterwards.
- No pre-ticked boxes.
The option most small sites should take
Use analytics that does not need consent at all.
Tools like Plausible, Fathom and Cloudflare Web Analytics do not set cookies, do not store personal data and do not follow people between sites. Under the current guidance that means no banner is required for analytics purposes. You lose cross session identity and some demographic reporting. For a business that wants to know which pages bring enquiries, that loss is small.
The gain is real: no banner, no consent rate to worry about, and every visitor counted rather than only those who agreed.
If you need Google Analytics
Some businesses do, usually because of advertising. Then you need a consent tool, Consent Mode configured properly, and the understanding that your numbers will undercount by however many people decline. Compare year on year rather than against pre banner figures, or you will think traffic collapsed.
Embeds are the usual leak
A YouTube embed sets tracking cookies on load. So do most map embeds, chat widgets, font services loaded from a third party, and social feeds. A banner that blocks your own analytics but leaves four embeds running is not doing its job, and the embeds are also slowing the page down.
Use youtube-nocookie.com, host your fonts yourself, and load chat widgets on click.
Write the policy in English
The cookie policy should list what is set, by whom, for how long and why, in a table a human could read. The generated twelve page document nobody reads is not protection; it is the thing an investigator will compare against what the site actually does.