The Real Cost of "Free"
"Free" is the most expensive word in web development. WordPress is free to download. That's true, and it's one of the reasons it powers such a large share of th...
Cookie Consent Is Not an Afterthought
Almost every website brief we see mentions analytics. Google Analytics 4, Google Tag Manager, conversion tracking, maybe a Facebook Pixel. All reasonable things for a business website to have.
Almost none of those same briefs mention cookie consent.
That's a problem, because under UK law, one requires the other. If your site sets non-essential cookies (and GA4 does), you need informed consent from the visitor before those cookies are set. Not after. Not alongside. Before.
The rules come from the UK GDPR and the Privacy and Electronic Communications Regulations (PECR). In plain English, here's what they mean for your website.
If your site uses cookies that aren't strictly necessary for the site to function (analytics cookies, advertising cookies, tracking pixels), you need to tell the visitor what those cookies do, give them a genuine choice to accept or reject them, and not set any of those cookies until they've made that choice.
The key word is "genuine." A banner that says "We use cookies" with only an "OK" button doesn't meet the standard. The ICO (the UK's data protection regulator) has been clear on this: accept and reject options need to be given equal prominence. No dark patterns, no pre-ticked boxes, no burying the reject option three clicks deep.
This isn't new law. It's been in force for years. But enforcement has tightened, and the ICO has been actively reviewing websites since 2024.
There are two sensible ways to handle cookie consent on a business website. Both are compliant when implemented properly.
Strict gating. Nothing fires until the visitor consents. No analytics, no tracking pixels, no third-party scripts that set cookies. This is the safest approach legally, but it means you lose data on every visitor who doesn't interact with the banner (and that's a lot of them).
Google Consent Mode v2. GA4 loads immediately in a cookieless mode. It collects basic, anonymised data without setting any cookies. When the visitor consents, it switches to full tracking with cookies enabled. When they reject, it stays in cookieless mode. This gives you some analytics data from every visit while respecting the consent choice. It's Google's own solution and it's been widely adopted since becoming a requirement for using certain Google advertising features.
Which one you choose depends on your business. If you run paid ads and need conversion data, Consent Mode v2 is probably the better fit. If you just need basic site analytics and want the simplest compliant setup, strict gating works fine.
Most SME owners don't know cookie consent is their problem. They assume the developer handles it, or that it's included in Google Analytics, or that the small banner at the bottom of the page is enough.
Developers and agencies don't always raise it either, especially if the client hasn't asked. It adds complexity to the project, it's another thing to configure and test, and explaining the legal requirements to a client who just wants their site launched isn't always an easy conversation.
The result is that a lot of business websites in the UK are running analytics without proper consent. Some don't have a banner at all. Some have a banner that doesn't actually block cookies before consent. Some have a banner with no reject option, or one that's deliberately harder to find than the accept button.
All of these are non-compliant, and all of them are fixable.
On WordPress, cookie consent means another plugin. CookieYes, Complianz, or similar. Each one needs installing, configuring, and testing. Each one loads additional JavaScript on every page. Each one needs maintaining as regulations and browser standards change.
On the CMS we've built and maintain, cookie consent is part of the platform. The banner supports both strict gating and Consent Mode v2. GA4, GTM, and Facebook Pixel integration are all consent-aware. The banner offers accept and reject at equal prominence with four layout options. A /cookie-policy page is auto-created and auto-populated. And the banner doesn't appear at all until a tracker is actually configured, so there's no unnecessary prompt on sites that don't need one.
You can see how this works on our CMS demo at ilovemotley.co.uk/cms. The whole thing takes about fifteen minutes to set up and ten more to test.
If you're not sure whether your site handles this properly, here's a quick check. Open your site in a private browser window. Look at the cookie consent banner. Does it have both accept and reject options? Are they equally visible? Now reject the cookies and check whether Google Analytics still loads (your developer can help you check this, or you can look in your browser's developer tools under the Network tab).
If analytics loads before you've consented, or if there's no reject option, that's a compliance gap worth fixing.
If you're not sure whether your site handles cookie consent properly, or if your next brief mentions analytics but not consent, get in touch. It's a quick thing to check and an important one to get right. You can also see how we approach web projects.
Choose the emails that suit you:
Choose one or both. You’ll receive no more than three emails in a month, and can change your choice or unsubscribe at any time.