Scanning a domain
Find out how a site scan works, what it requires and when it is worth running manually.
Scanning a domain is a key stage in configuring and maintaining CookieOfficer. There are two types of scan: automatic and manual.
The first scan is started automatically after successful registration. The scan results are used to create an inventory of cookies, the cookie declaration and a list of tracking scripts to be blocked.
Prerequisites
Your website must be publicly accessible. The scanner doesn't log in to closed systems, nor does it get past pages protected by a password or geo-blocking.
The scanning process
- Starting the scan: the first scan starts automatically once you have registered, and later scans run on a recurring basis. The schedule depends on your plan: every 30 days on Free, every 14 days on Basic, every 7 days on Pro and daily on Enterprise.
- Duration: depends on the size of the site and the number of subpages to be analysed.
- Scan results: just go to the Cookies section to see the full list of cookies along with their categorisation.
[Screenshot: the “Cookies” section with the result of the first scan and its status]
When is it worth running a scan manually?
- The scan ended with an error.
- You added a new tool to your site, for example a chat or an advertising pixel.
- You have just set up the CookieOfficer code and want to check the blocking.
To run a scan manually:
- Go to the Cookies section.
- Open the Scan history tab.
- Click Scan again.
Related articles
- How to analyse your scan results
- The scan found zero cookies
- The scan never finishes
- How we count subpages and domain size