Home/Notes/A practical look at cookie banners for a plumber
A practical look at cookie banners for a plumber
6 May 2024
How a plumber deals with cookie banners — and what usually goes wrong.
The problem: HTTP bookmarks after a forced HTTPS move. cookie banners slows the page for a plumber.
After the move, HTTP bookmarks after a forced HTTPS move broke search indexing for a plumber. Google kept serving the old pages for another nineteen days.
We keep a playbook for cookie banners. Step one is always the same: pull the live record with dig, compare it to what the admin panel shows, and fix the mismatch.
We solved cookie banners for a plumber by moving it behind a reverse proxy. The old configuration stayed live as a fallback for forty-eight hours, then we pulled it.
We moved cookie banners for a plumber to a provider that supports DNSSEC. It added five minutes to the migration and closed a class of attacks they did not even know about.
Every technical decision for a plumber comes back to one question: does this help the person looking at the site right now? If cookie banners is invisible to that person, it is working.
The job started when a plumber realised their cookie banners had been wrong for months. Nobody noticed because the site still loaded.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com