Your blog may not need a banner at all.
On many blogs, the banner is there for a few YouTube embeds, fonts from Google and an analytics tag. Gatelamp finds them, shows how to fix each one, and keeps the cookie page current.
Where it gets hard
Videos that set cookies before play
An embedded YouTube video can set cookies before anyone presses play. One video in an old post can be the only reason a site needs a banner.
Fonts and analytics from elsewhere
The theme loads its fonts from Google’s servers, and Google Analytics sets cookies on every page. Both happen before a reader has chosen anything.
A cookie page from years ago
The cookie page was written when the site launched. Since then plugins, embeds and scripts have come and gone, and the page still lists what was there at the start.
How it goes with Gatelamp
See what your pages load
A real browser opens your pages like a reader and writes down every cookie, bit of storage and request to another domain, with the script that caused it.
Site scanner →Fix what you can
Each finding comes with a way out, such as self-hosting Google Fonts or counting visitors without cookies. A site with nothing left that needs consent shows no banner.
No-banner advice →Videos load on a click
Each YouTube or Vimeo embed becomes a placeholder in your style that names the company behind it. The video loads after a click, YouTube from youtube-nocookie.com.
Click to load →A cookie page that stays current
Built from what the scanner finds, per language, as plain HTML on your own site. Search engines can read it, it works without JavaScript, and sites without a banner get one too.
Cookie declaration →
Say you run a cooking blog with a YouTube video in most recipes, fonts from Google and Google Analytics. The first scan lists all three. You self-host the fonts, switch to analytics without cookies and put the videos behind click to load. The next scan finds nothing that needs consent before a click, so the lamp stays off, and the cookie page lists what’s left.
Gatelamp for blogs and content sites: common questions
- Will my site still need a banner after the fixes?
- That depends on what it loads. If the scan finds nothing that needs consent, the site shows no banner and still gets weekly scans and a current cookie page. If something new turns up later, you get an email and can switch the banner on.
- Does Gatelamp work with AdSense or Ad Manager?
- Not for personalised ads at launch. IAB TCF and Google’s certified CMP list matter for sites that sell personalised ads through AdSense or Ad Manager, and Gatelamp doesn’t support them yet. For those sites, a tool on Google’s list is the better fit for now.
- Does it work with WordPress?
- A WordPress plugin is planned, without a date yet. Until then, the plain script tag works on WordPress, as on any other site. Astro sites get a component that renders the cookie page as static HTML on every build.
Gatelamp is in development, so plans, features and prices can still change. It helps you follow the published rules on cookies and consent; it isn’t legal advice.
Also for
Switch on early.
Join the waitlist for Gatelamp. We invite people in small groups, and waitlist members get the early price.
The form didn’t load. You can also join on our waitlist page.