Too few cookies were found with Cookie Scanner

Is it ok if too few cookies were found with Cookie Scanner?

Written by NelsonLast update 1 month ago

Cookie Scanner is a tool that is designed to scan a website generate a report with all cookies used on that website. 

We constantly update and improve the Cookie Scanner, however, there might be cases when Cookie Scanner might fail to scan the website properly. This might result in fewer cookies found on the website, or no cookies found at all.

This guide will help you to troubleshoot the problem and find out why Cookie Scanner fails to find the cookies. So, let's take it to step by step.

Check the report and see how many pages were found. If more than one page was found, go straight to the next chapter.

Zero or one page scanned

1. Proper domain? 

Check the domain you are scanning. Is it actually the same that your browser address bar shows when you enter the website. In case there are redirects from one page to another, Cookie Scanner might fail to follow those properly. You should always scan the final URL that is shown in the address bar when you visit the website. 

2. Scan with HTTP/HTTPS

Try scanning the domain name with HTTP/HTTPS: protocol and www/no-www. Check the exact URL of your website in your browser address bar. Cookie Scanner is smart enough to detect if your website uses HTTP or HTTPS, but it's always better to indicate this yourself. You can test scanning as many times as you need on the front page of Cookie-Script.

3. Check the firewall

Make sure your website or hosting provider does not block Cookie Scanner. If that's the case, go to your banner settings > Scans > check the "ALWAYS SCAN FROM SAME IP ADDRESS" checkbox. You can now whitelist this IP address in your server settings: All scanner requests are coming from this IP address.

4. Geolocation

Make sure your website is shown properly for Cookie Scanner geolocation. All requests from Cookie Scanner are coming from the Netherlands (Amsterdam).

All pages scanned, but missing some cookies

1. Validate with "fresh" browser

Make sure you are checking cookies in a "fresh" browser. That can be a new incognito browser instance or you have cleared all cookies in your browser before checking. This is important since your browser shows all cookies coming from a related website. For example, you have used different Google services and then visited your own website which only has Google Analytics installed. You will see all cookies related to the domain, even if they were not placed by your website, but by a previous session in some Google service itself. 

How to check cookies in Chrome and Firefox.

2. Disable other cookie banners

Check if you are currently using any other cookie consent solutions. While Cookie Scanner works perfectly with installed Cookie-Script Banner, it might have trouble with other cookie banners that can block cookies. Disable any other cookie banners before scanning the website.

3. Interactive cookies

Cookie Scanner does not perform any interactive actions, like adding products to the basket or submitting forms. If those actions result in some new cookies being added, Cookie Scanner cannot pick them up during the scanning process. You should add those cookies to the cookie report manually. 

In case you are still facing problems with finding all cookies on the website, contact our support team and we will investigate the issue. 

Note: It can take up to 24 hours from creating the banner for your site to be scanned and the results to show up in your cookie banner. If you don't want to wait for 24 hours, you can request po rescan your website via chat.

Scanning of logged in pages

If some web pages are behind a login screen and a user needs to be logged in to view the site content, CookieScript Cookie Scanner can't find cookies. In this case, scan your website initially and then add cookies that are hidden under the login page manually.

See the guide about how to add cookies manually.

Did this answer your question?