A cookie consent banner needs to do more than just appear — it has to actually block non-essential cookies and scripts until a visitor consents, offer a genuine way to decline, and record that choice, or it’s a banner in name only that doesn’t meet what most current privacy regulations actually require.
Cookie consent banner implementation
A cookie banner that actually blocks scripts until consent, not just one that appears.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of which regions’ regulations apply to your visitors (GDPR, CCPA, or both)
- A list or access to identify every cookie and tracking script currently in use
- Your branding preferences for how the banner should look and read
This or something else?
| You want a compliant cookie consent banner implemented for the first time | This fix covers it |
| You want scripts actually blocked until consent is given, beyond just a visible banner | Consent-gated script blocking configuration, the enforcement layer this banner needs |
| You want to know exactly what cookies and trackers you’re currently using first | Cookie audit & categorisation report, worth doing before or alongside this |
| You already have a banner but it’s not recording consent correctly | Consent record storage configuration |
What we do
- Confirm which regulations apply based on your visitor regions
- Select and configure a consent banner solution matching your compliance needs
- Style the banner to match your site’s branding
- Configure a genuine decline option, not just an implied acceptance
- Connect the banner to actually gate relevant scripts, not just display
- Test the full consent flow, including both accept and decline paths
What is included
- A configured, branded cookie consent banner
- A genuine, functional decline option
- Verified connection to actually gate relevant scripts
- Testing of both accept and decline paths
Not included
- A full cookie audit identifying every tracker in use, a separate, related fix
- Consent record storage and retrieval, a separate, related fix
- Legal advice on which regulations specifically apply to your business
- Ongoing updates as you add new trackers or scripts later
Questions about this fix
Does just having a banner make me compliant?
Not on its own — a banner that doesn't actually block scripts until consent, or doesn't offer a genuine decline option, doesn't meet what most current regulations require, which is why we connect it to actual script gating rather than treating it as decorative.
Will this block things like Google Analytics until visitors consent?
Yes, if configured to, which is the correct approach for genuine compliance — analytics and marketing scripts should generally wait for consent rather than running by default.
What if a visitor declines — does the site still work normally for them?
Yes, core site functionality shouldn't depend on non-essential cookies, so a visitor who declines should still be able to browse and use the site normally, just without the tracking-dependent extras.
Do I need a different banner for visitors in different regions?
Not necessarily a different banner, but the specific behaviour (like defaulting to opt-out versus opt-in) can reasonably differ by region depending on which regulation applies to that visitor.
How do I know which cookies and scripts actually need to be gated?
A cookie audit identifies this comprehensively — we can do that as a preceding or parallel step if you're not already confident in your full current inventory.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.