How to test your cookie consent banner: a 10-minute manual check and an automated scan
A step-by-step test for any cookie banner: what loads before consent, whether Reject really stops tracking, and whether the choice survives a reload.
Lukas Kontur · · 5 min read
A cookie banner that looks right can still be wrong. The banner is one script; the trackers are other scripts, often added by other people, and nothing guarantees that they wait for the banner. The only way to know is to watch what the browser actually does. This guide gives you a manual test you can run in about ten minutes in any browser, and explains what an automated scan adds.
What you are testing
A working consent setup has to pass four checks:
- Before any click, no analytics, advertising or other non-essential cookies are set and no requests go to tracking services.
- After Reject, nothing non-essential starts, and anything that was set is removed or stops being used.
- After a reload and on other pages, the refusal still holds.
- After Accept, the tools you use do start. This proves the banner is connected to them at all.
Checks 2 and 3 are where most sites fail. In our study of reject flows, non-essential cookies were still present after Reject on 48.3% of the conclusive tests (the reject-button study).
Before you start
- Use Chrome, Edge or Firefox on a desktop. Open a new private window for every test, so no earlier consent is stored.
- Open the developer tools with F12 before you load the site.
- In the Network tab, tick Preserve log, so requests stay visible after a reload.
- Write down which tools your site should use: for example Google Analytics, Google Ads, the Meta Pixel, Hotjar. You will look for each of them.
Test 1: what loads before consent
- Load your home page in the private window. Do not touch the banner.
- In Application (Chrome) or Storage (Firefox), open Cookies for your domain. Typical non-essential cookies are
_gaand_ga_plus an ID (Google Analytics),_gcl_au(Google Ads),_fbp(Meta) and_hjSessionUser(Hotjar). - In Network, filter for
collect,facebook,doubleclick,hotjarandtiktok. Any request here before a click is a tracker running before consent. - For each finding, open the request and look at Initiator. It tells you which file started it: a plugin, a theme file, your tag manager or a hard-coded snippet.
A cookie the banner needs to remember the choice, and session cookies for a cart or login, are normally fine. Everything that measures, profiles or advertises is what you are looking for.
If Google requests appear but no _ga cookie, your site may use Google Consent Mode in its advanced form, where Google tags send cookieless pings before consent. That is a configuration choice, explained in Google Consent Mode v2 setup.
Test 2: Reject, then look again
- Clear the site's data (Application, Storage, Clear site data) and reload in the same private window.
- Check that the banner offers Reject (or Decline, Deny) on the first layer, as clearly as Accept. If you have to open settings first, note it.
- Click Reject.
- Check the cookies again. Non-essential cookies set before the click must be gone, and no new ones may appear.
- Check Network for new tracking requests after the click.
Test 3: reload and navigate
- Reload the page. The banner should not come back, and the cookies and requests from Test 1 must not return.
- Open two or three other pages, including one that matters commercially, such as a product page or the cart.
- If a tracking cookie reappears after the reload, the banner deleted it but did not stop the script that sets it. We call this consent respawn.
Test 4: Accept in a fresh window
Open a new private window, load the site and click Accept. Your analytics and advertising tools should now start. If nothing starts, your banner is not connected to them, and your tag setup needs work before you can trust any of the earlier results.
Test 5: change your mind
After accepting, look for a way to reopen the settings: a floating icon, a footer link such as "Cookie settings", or a link in the privacy policy. Withdrawing consent must be possible, and as easy as giving it. Reopen the settings, refuse, reload, and repeat Test 3.
Common causes when a test fails
- A tracking snippet is pasted directly into the theme or a page builder, outside the consent tool.
- A caching or optimisation plugin combines or delays scripts, and the consent tool no longer recognises them.
- Tags in Google Tag Manager fire on page view instead of waiting for consent. See Complianz with Google Tag Manager and Cookiebot auto-blocking misses GTM scripts.
- The server sets the cookie in a
Set-Cookieresponse header, which no browser-side blocking can stop. - A plugin update renamed a script the consent tool used to recognise.
For platform-specific fixes see CookieYes not blocking scripts, Complianz not blocking GA4 or Meta Pixel and Cookiebot Reject not stopping tracking.
What an automated scan adds
The manual test is reliable, but it is slow, depends on who runs it and has to be repeated after every change. An automated scan runs the same steps in a clean browser: it records cookies and requests before consent, clicks Reject, reloads, and compares the results. It also classifies each cookie and tracker, so you do not have to look up every name, and it keeps the evidence.
Run the manual test once to understand your setup, then use a scan to repeat it after plugin updates, theme changes and new marketing tags.
Check your site in 1 minute
Our free scan runs the tests above in a clean browser and shows what loaded before consent and after Reject, with the requests that caused each finding. No signup needed. Run a free scan.
Get alerted when it breaks
A passing test today says nothing about next month's plugin update. With monitoring, we re-scan your site on a schedule and email you when a tracker starts running before consent or after Reject. Create an account and add your site.
Last updated: