If the Cookiebot banner doesn't appear on your website, first open your website in a private window. If the banner appears there, Cookiebot is working, and your normal browser has your consent saved. If it doesn't, check these in order: your Cookiebot account, that your domain is added, the script and the script ID, your region settings, browser extensions, website caching and optimization plugins, and your website's Content Security Policy.
1: Check whether you already gave consent in this browser
Consent is saved in the CookieConsent cookie until it expires (12 months by default). While the cookie exists, the banner doesn't show again in that browser.
- Open a private or incognito window and enter your website address.
-
If the banner shows, Cookiebot is working. You don't see it in your normal browser because your consent is saved there, in the CookieConsent cookie of your website. To see the banner again, delete that cookie.
Example: in a private window, the Cookiebot banner appears on the first visit and asks for consent ("Deny", "Customize", "Allow all").
Example: after consent is given, the same page in the same browser shows no banner.
2: Check your trial and payment status
If the banner is missing in a private window too, your account may be suspended. This happens when Cookiebot no longer has valid payment details, for example after a rejected credit card, or after a free trial has ended without payment information. Cookiebot first sends warning emails to the email address of the account. If no action is taken, the account is suspended and the Cookiebot scripts stop working on your website.
- Sign in to your Cookiebot account.
- If you see a message about payment details or your trial, add payment information.
- Your account and the scripts are active again after that.
If you can't sign in, see I can't sign in to Cookiebot Manager or I can't sign in to Cookiebot Admin.
3: Check that your domain is added to your account
4: Check your script and script ID
- The script must load from consent.cookiebot.com or consent.cookiebot.eu. If it is hosted on your own server (for example by a plugin), it fails. To copy the correct script, see Manually implementing Cookiebot CMP (Cookiebot Admin) or Manually implementing Cookiebot CMP (Cookiebot Manager).
- If you use automatic blocking, the Cookiebot script must be the first script in the head of your page, and it must not have the "async" or "defer" attribute. See How does auto-blocking work?
- The ID in the script (CBID) must match the domain group serial number of the domain group your domain is in. To find it, see Your CBID or Domain group ID, and where to find it in your Cookiebot Admin or Your CBID or Domain group ID, and where to find it in your Cookiebot Manager.
5: Check your geolocation and distribution settings
You can set the banner to show only in some regions. Sign in, open the "Distribution" setting and check that your region is included. "EU" does not include countries such as Great Britain, Norway or Switzerland.
6: Check your browser extensions
Cookiebot runs in the visitor's browser and can't override a browser or an extension that blocks cookie banners. Try without extensions.
7: Check your website caching and optimization
A cached site may not show recent changes. Turn off caching, or wait a few hours and try again.
Caching and optimization plugins, such as WP Rocket, LiteSpeed Cache or Cloudflare Rocket Loader, can minify, defer or delay scripts, including the Cookiebot script. Exclude consent.cookiebot.com/uc.js from these settings, then clear your cache. See WordPress: Common issues or Exclude Cookiebot from the LiteSpeed Cache Plugin in WordPress.
Check 8: Check your Content Security Policy
If your website sends a Content Security Policy (CSP) header, it must allow the Cookiebot domains. See Cookiebot and Content Security Protocol (CSP) for the directives to add.
Related errors
- Error: The domain is not authorized to show the cookie declaration
- Error: The domainname is not a valid domain
Comments
2 comments
Your banner might not show if your subscription expired, your region isn’t included, the Cookiebot script is misconfigured, your domain isn’t added, a browser/plugin blocks it, consent was already given or your site is cached. Check these areas to fix the issue.
It sounds like the article is about diagnosing why a cookie banner is not appearing. Here is your 2–3 line comment following all rules and “mem reduct” as the first anchor text:
I like how this breaks down the common reasons a banner fails to show, and I recently tested a similar idea when debugging a site of my own. A simple takeaway is to confirm your region settings before trying anything else, since tools like memory reduct can also behave differently based on configuration.
Please sign in to leave a comment.