The cookie banner you copied describes somebody else's tracking
What actually sets a cookie on a plain brochure site
A visitor emailed to say your cookie banner was sitting on top of your phone number on her screen. She couldn't tap either one. You realized you couldn't remember why the banner was there in the first place.
A basic hosting setup and a plain contact form might set no cookies at all beyond what the page needs to function. Cookies that are strictly functional don't need the same consent treatment as tracking ones.
The banner your site is running may be answering a question your site doesn't actually raise. It's worth finding out before touching the wording at all.
A quick way to check: open the site in a fresh private browser window and watch what loads before you click anything at all on the banner itself.
Banners asking consent for tracking the site does not run
Plenty of cookie banners were copied from a template along with the rest of the site. They list categories of tracking — advertising, analytics, personalization — that were never actually installed anywhere on the pages.
A banner asking permission for something the site doesn't do is not just pointless. It actively misleads a visitor about what's happening to their data, even if nothing is actually happening at all.
A visitor who reads that list and declines analytics tracking the site never ran has been handed a false sense of control over nothing.
Cross the categories off one by one against what the site actually does. Whatever's left over on the banner after that is the part worth deleting.
Banners that ask and then load the tracker regardless
The worse version of the same problem is a banner that presents a real-looking choice, paired with a tracking script that loads before anyone clicks anything. Sometimes it loads exactly the same whether the visitor accepts or declines.
That setup gives a visitor the appearance of control while removing the substance of it. It's arguably worse than skipping the banner altogether.
A banner that lies about the choice it's offering tells the visitor something false about their own data. That's a bigger problem than having no banner at all.
Checking whether this is happening on your own site takes ten minutes: decline everything on the banner, then look at what still loads afterward.
If a tracking script fires anyway, that's not a wording problem the banner copy can fix. It's a build problem that needs an actual change to the code behind it.
The embeds you forgot: maps, video, chat, hosted fonts
An embedded map. A video hosted somewhere else. A live chat widget. Even a font loaded from an external service.
Every one of these can quietly bring its own cookie along, set by a domain other than the one the visitor is looking at. Sites accumulate these piece by piece over months and years, added for one feature at a time.
Nobody keeps a running list of what each embed actually does in the background. That's exactly how a banner ends up describing tracking nobody remembers adding.
A site redesign is usually when this gets noticed, when someone finally opens the page source and finds a chat script from a vendor the business stopped using years ago.
A short list, kept anywhere convenient, of every embed added and why, saves that discovery moment from happening again next time.
Even a single spreadsheet row per embed helps: what it is, who added it, and roughly when. Future you will be grateful the next time a banner needs updating, or the next time somebody asks what the site actually tracks.
What a banner has to let a visitor do to be worth having
A banner worth having gives a visitor a real choice. Not a single "accept" button with "reject" buried three clicks deep in a settings menu.
It has to be just as easy to decline as to accept. And declining actually needs to stop the tracking, rather than just hiding the banner from view.
Anything less is a banner in appearance only. It looks like consent. It isn't.
A well-built banner also remembers the visitor's answer, so it doesn't ask again on every single page. Asking repeatedly wears out the goodwill a banner is supposed to be earning.
A returning visitor who already answered shouldn't have to answer again a week later. That memory is part of what makes the choice feel real rather than performative.
Deciding whether this site needs one at all
If an honest inventory turns up no tracking beyond what the site needs to function, a banner may not be doing anything except covering your phone number on somebody's screen.
If the inventory turns up an analytics script, a chat widget, or an embedded video, a banner earns its place. Built around what the site actually does. Not copied from whatever template it started from.
Worth revisiting the inventory once a year, since embeds get added quietly and a banner written for last year's site can go stale fast.
The banner usually links out to a policy explaining what it's asking about, and whether a small brochure site needs a privacy policy at all is worth answering before writing the banner copy. This sits inside the wider accessibility and legal-adjacent picture too — the build questions that come before any of this cover the rest of it.
An embedded video can be the exact culprit bringing in a tracking cookie, and the autoplay and captioning problems that same video causes are worth checking at the same visit. And once the site is live, scripts get added after launch more often than anyone plans for, which is exactly how banners go stale in the first place.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go