A cookie banner that blocks tracking, and an Impressum that holds up.
Most consent banners on European sites do not comply, because the tracking has already fired by the time the banner appears. That is the part regulators actually act on, and it is the part almost every plugin gets wrong by default.
Included in every rebuild. Standalone from 290 euro.
373 products migrated for a Dutch furniture and bedding retailer Off WooCommerce, same domain, search position held. Read the case study ➤Featured case study
34
findings fixed
- 3storefronts
- 20pages corrected
When this is worth doing properly
The rules that get enforced are narrower than the panic suggests, and most sites fail on the same handful of them.
Your analytics loads before anyone consents
This is the common failure. The banner appears, the visitor has not chosen anything, and the tracking request has already gone. Consent given afterwards does not fix what already happened.
Rejecting is harder than accepting
One green button to accept and a link buried in a submenu to refuse. Regulators have been explicit that the two choices must be equally easy.
Your privacy policy describes a different website
Copied from a generator or from whoever built the site, listing tools you do not use and omitting the ones you do.
You sell into Germany with no Impressum
Germany, Austria and Switzerland require specific details in a specific place. It is one of the easiest things to get right and one of the most commonly missing.
Not sure whether your setup fires before consent? The free 15 point check tests exactly that. Get the site check
Seen enough? Send your web address and the written 15 point check comes back in two working days, free.
What gets set up
Implementation, tested rather than assumed.
Prior consent that actually blocks
No analytics, no pixel, no font call to a third party until the visitor says yes. Verified by watching the network, not by trusting the plugin's description of itself.
Consent Mode configured properly
Google's consent signals set to denied by default and updated on the choice, so your tags behave correctly instead of ignoring the banner they sit behind.
Reject as easy as accept
Two buttons, same weight, same screen. No dark patterns, no pre-ticked boxes, no scroll to consent.
A policy that matches reality
Written from what your site actually loads, listing the real tools, the real purposes and the real retention periods.
Impressum where you trade
The specific fields required for the German speaking markets, in a place a visitor can reach from every page.
A record of the choice
Consent stored so a returning visitor is not asked again, and so you can say what was agreed and when.
Rather just ask? One question by email or WhatsApp is fine.
What I will not do
Four things this is not.
Not legal advice
I implement, I do not advise. Where a question is genuinely legal I will say so rather than guess in a way that sounds confident.
No dark patterns
They are the thing regulators are actually enforcing against, and they lose you the trust of the people who notice.
No cookie wall
Blocking the site until someone accepts is not valid consent under the rules you are trying to satisfy.
No plugin left on defaults
Almost every consent plugin ships in a configuration that does not comply. Installing one is the start of the work, not the end.
A furniture retailer: three storefronts, three ad accounts and a CRM
A Dutch store taken through the Thuiswinkel Waarborg review: 34 findings fixed and verified on the live store, including cookie banner position, the withdrawal form and payment methods listed that were not actually accepted.
Ready when you are. No form to fill in, and no call required to get started.
Fair questions about consent and compliance
Do I really need a cookie banner?
If you load anything that sets a cookie or sends data to a third party, and you have visitors in the EU or UK, yes. If your site loads nothing of the sort, you may not, and that is a better outcome than a banner.
Do I need an Impressum?
If you trade into Germany, Austria or Switzerland, yes, with specific fields. There is a guide on the resources page covering exactly what it must contain.
Will this break my analytics?
It will reduce the numbers, because you will stop counting people who never agreed to be counted. That is the correct number and it was always the correct number.
Can you use Google Analytics compliantly in the EU?
With consent, Consent Mode configured properly, IP handling set correctly and the transfer disclosed, it is what most sites do. Some organisations choose an EU hosted alternative instead and I will set that up if you prefer.
Is this really 290 euro?
On a normal business site, yes. A store with many third party scripts takes longer and I will quote it in writing before starting, not after.
What proof do I get that it works?
A recording of the network requests before consent, showing nothing fires. This site's own consent gate is tested the same way on every deploy, 15 checks, and it has to pass before anything ships.
Built for these kinds of company
The same service, written for what each of them has to prove.
Find out what your site is loading before consent.
The free 15 point check tests whether anything fires before a visitor agrees, which is the part that actually gets enforced. Two working days, no call required.