Automatic cookie scanner
Find out what cookies your website uses
Don't know what Cookies your website creates? Our scanner recognises cookies from known services within a minute and sorts them into categories. Regular updates according to your plan.
How the scanner works
A quick overview of First-party cookies and Third-party cookies on your website.
Scanning without installation
Loads your homepage, reads the cookies set by the server and recognises scripts of known third-party services.
Automatic categorisation
Recognised cookies are placed into categories by purpose.
Known cookie database
We recognise hundreds of cookies from GA, Meta, Sklik, Smartsupp, Hotjar, Clarity and more.
Regular updates
Automatic repeated scanning according to your plan.
New cookies straight into your inventory
A scheduled scan adds newly recognised cookies to your inventory and policy by itself. After a manual scan you click Import.
Detailed report
Clear output with the name, purpose and lifetime of each cookie.
What the scanner detects
Automatic categorisation into 4 groups: Essential cookies, Analytics cookies, Marketing cookies a Functional cookies.
Necessary
Cookies essential for website operation (session, cart, login)
Analytical
Cookies for measuring traffic and user behaviour
Marketing
Cookies for advertising, remarketing and personalisation
Preference
Cookies for storing user preferences
How to get started
Run your first scan in less than a minute.
Add your website
Enter your website URL into the Consentio dashboard.
Run the scan
Click the Scan button. The scan runs in the background.
Review the results
Within seconds you see the report with the recognised cookies. Click Import to add them to your inventory; anything the scanner does not know, you add by hand.
Automatic updates
From then on the scanner re-checks your homepage by itself: every 30 days on Free, every 7 on Solo, daily on Pro and Agency.
Why regular scanning matters
Cookies on a website change much more often than people realise. Add a new WordPress plugin, install a chat widget, swap analytics providers or turn on a retargeting campaign: and suddenly trackers are running that visitors know nothing about and that your cookie policy fails to mention. GDPR Article 13(3) requires the controller to re-inform data subjects whenever such changes occur.
European supervisory authorities have made this a clear enforcement priority since 2022. The CNIL fined Google EUR 150 million and Meta EUR 60 million for cookie-refusal failures, while the ICO has issued multiple six-figure UK enforcement notices for cookie policies that no longer matched the cookies actually being set. The most common failure mode is a privacy policy written two years ago while the site has since picked up Hotjar, Microsoft Clarity or TikTok Pixel. Automated rescans prevent that drift by adding newly recognised cookies straight into your inventory and policy.
Continuous scanning also has practical impact on Google Consent Mode v2. If the scanner recognises Google Ads or Google Analytics 4 on your site, it files their cookies under the categories that the banner maps to Google Consent Mode v2 signals, so remarketing and conversion measurement keep working under EEA law. Without correctly wired cookies and consent signals, Google has restricted reports and audiences for European traffic since March 2024.
The scanner also documents the state of your site over time. If you ever face an ICO audit or a data subject access request under GDPR Article 15, you have the recent scans as evidence that you were actively tracking cookies and responding to changes. The 10 most recent scans of each site stay in the dashboard and consent records can be exported to CSV at any time.
How Consentio scanner compares
Side-by-side feature comparison against the leading cookie consent platforms and a manual DevTools audit. Enforcement under GDPR Article 7 and the ePrivacy Directive applies to every site that uses non-essential cookies, regardless of which platform you choose.
| Capability | Consentio | CookieBot | CookieYes | OneTrust | Manual (DevTools) |
|---|---|---|---|---|---|
| Headless browser crawl | No (HTTP + service database) | Yes | Yes | Yes | No |
| Third-party cookie detection | Known services only | Yes | Yes | Yes | Limited |
| Auto-categorisation (4 groups) | Yes | Yes | Yes | Yes | No |
| Known-cookies database | Hundreds | Large | Medium | Large | None |
| Scan frequency (Pro plan) | Daily | Monthly | Monthly | Configurable | None |
| New-cookie alerts | In inventory after scan | Yes | Yes | Yes | No |
| Page-count limits | Homepage | 100 / subdomain | 500 / site | Unlimited | 1 page at a time |
Frequently asked questions
How does the automatic cookie scanner work?
The scanner loads your homepage, reads the cookies set by the server and recognises scripts of known services in the page code (Google Analytics, Meta Pixel, Sklik, Smartsupp, Hotjar and more). For every recognised service it fills in its cookies, purpose and lifetime from our database. It does not run a browser or crawl subpages, so cookies that are only set after visitor interaction are added to the inventory by hand.
How often is scanning performed?
Frequency depends on your plan: Free every 30 days, Solo every 7 days, Pro and Agency daily. You start the first scan yourself in the dashboard; after that it repeats automatically.
How are cookies categorised?
The scanner automatically categorises cookies into 4 groups: Necessary (website functionality), Analytical (traffic measurement), Marketing (advertising and remarketing) and Preference (user settings).
Does the scanner detect third-party cookies too?
First-party cookies set by the server are read directly from the website response. Third-party cookies are recognised from the scripts of known services loaded on the page (Google Analytics, Meta Pixel, Sklik, Hotjar etc.). Services missing from our database are not recognised.
Is a scanner enough to be GDPR-compliant on its own?
No. The scanner solves cookie discovery, but GDPR requires more: a banner that captures freely-given, specific, informed and unambiguous consent (Article 7), a cookie policy describing the purpose of each cookie (Article 13) and an easy way to withdraw consent. The ICO has been explicit on this in its cookie guidance, and the EDPB Guidelines 05/2020 confirm consent must be as easy to refuse as to give. Consentio has scanner, banner and policy generator (Pro plan) in one tool, so the cookies in your inventory show up in both the banner and the policy.
How does the scanner know what each cookie does?
We maintain a database of hundreds of known cookies from Google Analytics, Google Ads, Meta Pixel, Hotjar, Microsoft Clarity, LinkedIn Insight Tag, TikTok Pixel and similar services. When a cookie matches a known signature, the scanner auto-fills purpose, lifetime, provider and category. Cookies it does not recognise are flagged for review and are not published until you classify them: both the ICO and CNIL recommend a conservative approach (treat unknown cookies as non-essential by default).
Does the scanner work on pages behind a login?
No. The scanner only loads the public homepage. Cookies set after login (client areas, admin panels) should be added to the inventory by hand; these are typically necessary session cookies that do not require consent.
Does it scan the mobile version of my site as well?
No. The scanner loads the site as a single client without device emulation. If your mobile version loads different scripts than desktop (AMP pages, mobile-only chat widgets), add their cookies to the inventory by hand. This matters because the EDPB Guidelines 03/2022 on dark patterns explicitly note that consent must reflect what is actually happening: if your mobile site loads more trackers than the desktop one, users must be informed.
Aligned with European data protection authorities
The Consentio cookie scanner is built to help meet the requirements of the following legal frameworks and supervisory authority guidance:
- GDPR (Regulation (EU) 2016/679)
- ePrivacy Directive (2002/58/EC), Article 5(3)
- ICO: UK Information Commissioner guidance on cookies
- CNIL: French data protection authority
- EDPB: Guidelines 05/2020 on consent
Last updated:
Solve cookies today.
Sleep peacefully tomorrow.
Try for free - No card required
- 5 minutes to implementation
- Made in EU