How to test your cookie banner (free test template)
Free scan: what loads on your site before consent?
Step one of the test: load your page like a first-time visitor and list every cookie and tracker that starts before anyone clicks. No sign-up.
Open your site as a first-time visitor and check four things: nothing optional loads before a choice, rejecting works as well as accepting, Google tags receive the right Consent Mode signals, and visitors can change their mind later. Start with the free scan above — it lists what loads before consent — then work through the steps and the template below.
Facts checked · Sources
Test it in 6 steps
- 1Run the pre-consent scanUse the free scan above on your homepage and on one page with embeds (video, maps, chat). Anything marked as loading before consent is your first fix.
- 2Look at cookies as a new visitorOpen a private window, then Chrome DevTools → Application → Storage → Cookies and select your site. Reload. Before you click anything, only strictly necessary cookies should be there.
- 3Reject, then reloadClick the reject button and reload. No analytics or marketing cookies should appear, and the Network panel should show no requests to ad or analytics tools (cookieless Google pings are expected in advanced Consent Mode).
- 4Check the Consent Mode signalsOpen Tag Assistant (or GTM's Preview) and select the Consent tab. On-page Default should show every type denied; after a click, On-page Update should show what the visitor chose.
- 5Accept, then confirm tags fireIn a fresh private window click accept: analytics and marketing tags should now fire, and their cookies appear in DevTools.
- 6Change your mindReopen the settings from the floating button or your footer link, switch a category off and save. Tag Assistant should show a new update to denied for it.
Cookie banner test template
Copy this into a spreadsheet and fill in pass or fail per page, device and language. The design checks follow the patterns the EDPB's cookie banner taskforce reviewed.
| Check | How to test | Pass when |
|---|---|---|
| Nothing optional before consent | Free scan + DevTools cookies on first load | Only strictly necessary cookies and no tracker requests |
| Reject on the first layer | Look at the banner without opening settings | A reject button sits next to accept |
| Equal design | Compare the accept and reject buttons | Same size, colour weight and readability |
| No pre-ticked boxes | Open the settings panel | Every optional category starts switched off |
| Reject actually rejects | Reject, reload, check cookies and Network | No analytics or marketing cookies or requests |
| Consent Mode default | Tag Assistant → Consent tab → On-page Default | ad_storage, analytics_storage, ad_user_data, ad_personalization denied |
| Consent Mode update | Click a choice, check On-page Update | The update matches the choice |
| Honest categories | Read each category's cookies | Nothing labelled necessary that only measures or advertises |
| No legitimate-interest tracking | Look for extra 'legitimate interest' toggles | Tracking only runs on consent |
| Withdrawal | Reopen settings, switch off, save | Easy to find, and tags stop |
| Every language and phone | Repeat on mobile and per language URL | Same results everywhere |
Basic or advanced Consent Mode: what you should see
In basic mode, Google tags don't load until the visitor chooses. In advanced mode, Google tags load straight away but send cookieless pings while consent is denied — so a request to Google before consent isn't a failure by itself in advanced mode, as long as no Google cookies are set.
Google tag requests carry gcs and gcd parameters with the consent state. Google documents the parameters but warns their format can change, so read the Consent tab in Tag Assistant instead of decoding them by hand.
Make it a habit
Retest after you add a plugin, a tag or a new embed — that's when trackers slip in before consent. PrivacyPill's Pro plan rescans your sites every month and flags new trackers (opens soon — join the waitlist); the free scan does the same check on demand.
Comparing cookie banner tools?
- PrivacyPill vs. CookiebotWhy people switch, six alternatives, a cost calculator and a 15-minute switch.Cookiebot alternative
- PrivacyPill vs. OneTrustPublic prices and self-serve checkout instead of a quote.OneTrust alternative
- PrivacyPill vs. CookieYesUnlimited pageviews on Pro, no overage fees.CookieYes alternative
- PrivacyPill vs. UsercentricsNo session tiers or automatic plan upgrades.Usercentrics alternative
Frequently asked questions
Sources
Facts on this page come from these pages, read on . Spotted something out of date? Write to kalmwerk@gmail.com and we'll correct it.
- EDPB cookie banner taskforce report (17 January 2023)
- Google: verify your consent mode implementation
- Google: consent mode overview (gcs and gcd parameters)
- Google Ads Help: basic vs. advanced consent mode
- Chrome DevTools: view, edit and delete cookies
- Chrome DevTools: cookies per network request
- Google Analytics Help: EU user consent and audiences (March 2024)
Using Google Ads or GA4? Check Consent Mode v2
See whether a consent default runs before your Google tags, what the four v2 signals start as, and how to fix it.
What PrivacyPill costs
The free plan works today. Pro and Lifetime open soon — join the waitlist and we'll email you once when they do.
FreeAvailable now
€0forever
- 1 domain, 5,000 pageviews a month
- Consent Mode v2, 6 languages, consent log
LifetimeOpens soon
€49once
- 1 domain, unlimited pageviews
- Every future update, no renewals
ProOpens soon
€9/month · or €79/year
- Unlimited domains and pageviews
- Monthly rescans, geo-targeting
Try it on your own site
Design your banner, preview it live, and paste one line. Free for one domain.