A GDPR compliance checker is a tool that tests your website for privacy and consent problems, such as cookies that load before a visitor agrees, missing policies and unexpected third-party trackers. It shows what your site actually does, rather than what you assume it does.
People searching for a “GDPR checker” find very different things: automated scanners, browser-based audits and short questionnaires. They answer different questions. This guide explains what each type tests, compares widely used tools, and shows how to run a scan and act on the results.
It covers the EU GDPR and the ePrivacy rules on cookies. The UK GDPR is a separate framework with similar requirements. If you are new to the regulation, start with our GDPR compliance guide. Checkers highlight issues; they do not provide legal advice.
What Is a GDPR Compliance Checker?
A GDPR compliance checker scans or audits a website and reports issues linked to GDPR and cookie rules. Typical findings include tracking that starts before consent, consent banners that do not work as described, and cookies or third parties missing from your policies.
Vendors use several names for similar tools: GDPR checker, GDPR scanner, cookie scanner, cookie audit tool. The labels overlap, but the methods differ. Some tools only list the cookies they find. Others run your site like a real visitor and record what happens after each consent choice.
A checker finds problems. It does not write your privacy policy, display a banner or fix your scripts. You implement the changes and test again.
What Does a GDPR Checker Test on a Website?
The exact checks depend on the tool, but most cover some of the following:
Cookies and trackers before consent: Whether non-essential technologies load before the visitor makes a choice.
Banner behaviour: Whether Accept, Reject and preference settings change what the site does.
Cookie inventory: The cookies found, with their names, domains, purposes, durations and categories.
Policy presence: Whether a privacy policy and cookie policy exist and are easy to find.
Third-party requests: Which external services receive data when a page loads, including possible international transfers.
Security basics: HTTPS configuration and secure cookie settings.
Consent signals: Whether frameworks such as IAB TCF or Google Consent Mode are detected.
No single free tool covers every item. Decide which risks matter most for your site before you choose.
Types of GDPR Compliance Checkers
Type | What it checks | Best for | Main limitation |
Cookie scanner | Cookies and trackers found on scanned pages, with categories and descriptions | Building a cookie inventory | May not show whether consent is actually enforced |
Runtime consent audit | Loads the site in a real browser and records what fires before consent and after Reject | Verifying banner behaviour | Requires a tool that supports browser-based testing |
Questionnaire-based checker | Your answers about rights, notices, security and breaches | Reviewing internal processes | Depends on your answers and does not test the website itself |
Security and privacy test | Site security configuration plus privacy-related signals | Spotting technical weaknesses | A GDPR score is only a partial indicator |
Best GDPR Checker Tools for Your Website
The tools below are widely used starting points. Features, limits and pricing change, so confirm the current scope on each provider’s page before relying on a result.
Okito Cookie Checker
Okito’s free Cookie Checker helps you see which cookies your website sets. That is a practical first step, because you cannot manage cookies you have not identified. Use the result as an inventory, then test how those cookies behave before and after consent.
Compliance Checker (ScanMySite)
Compliance Checker is a free scanner, listed as beta at the time of writing, aimed at small and medium businesses. You choose which checks to run instead of receiving one generic score. The checks span consent and transparency, tracking and storage, and data flow and security, including cookies set before consent, policy presence, cross-border transfer risks and HTTPS configuration.
SecureSpells Cookie Audit
SecureSpells offers a free cookie audit built around runtime testing. It runs the site in a browser and reports what fires before consent, whether Reject blocks tags and which third parties receive requests. This makes it useful for checking banner enforcement rather than just cookie lists.
CookieYes Cookie Checker
CookieYes’s Cookie Checker scans a URL and presents cookies in a table with name, domain, description, duration and category. It is a good fit when your priority is a categorised cookie list for your cookie policy.
ImmuniWeb Website Security Test
ImmuniWeb is a website security test that includes a GDPR-related score. It provides a detailed report you can download as a PDF, which helps when you need to share technical findings with developers or management.
Sovy GDPR Scan
Sovy is a GDPR and privacy policy scanner. It looks at the type of data your website collects, your policy and personal data security, then summarises requirements with a compliance percentage.
2GDPR
2GDPR is a simple scanner covering personal data collection, cookie compliance, data transfers and breach risks. It does not scan every page of a site, so treat its result as a sample rather than a full audit.
Blackkite GDPR Checker
Blackkite’s checker is a ten-question assessment on core GDPR requirements. It suits a quick awareness check, but because it relies on your answers it does not test how the website behaves.
ICO Data Protection Self-Assessment Checklists
The UK Information Commissioner’s Office publishes self-assessment checklists for controllers and processors. They cover areas such as individual rights, data processing, breaches and impact assessments. They are written for the UK regime, but the structure is useful for any organisation reviewing its processes.
Runtime vs Static GDPR Checkers: Which Is More Reliable?
The most important difference between GDPR checkers is how they gather evidence.
Approach | How it works | Strength | Weakness |
Static | Reads page source, cookie lists or a single snapshot | Fast and simple for inventories | Can miss trackers that load later or depend on interaction |
Runtime | Runs the site in a real browser, tests consent choices and records requests, cookies and scripts | Shows what actually fires and when | Needs a tool built for browser-based testing |
A static scan can tell you that a cookie exists. A runtime test can tell you whether it still fires after a visitor clicks Reject. For consent compliance, the second answer matters more. Many site owners use both: a scanner for the inventory and a runtime test for enforcement.
How to Choose a GDPR Compliance Checker
Match the tool to the question you need answered:
Check behaviour, not just lists. If your concern is consent, choose a checker that tests what happens before consent and after rejection.
Look at coverage. Find out whether the tool scans one page, a sample or the whole site, and whether it handles dynamic content.
Prefer actionable reports. Useful reports name the cookie, script or URL involved and point to a fix.
Consider repeat scanning. If your site changes often, a tool that supports scheduled scans helps you catch new problems.
Match your market. Make sure the checks reflect the EU rules that apply to you, and confirm requirements from other regions separately.
Understand the scope. A questionnaire, a cookie scanner and a security test are not interchangeable.
If you use Google advertising or analytics products, our Google Consent Mode Checker covers that part of your setup.
How to Use a GDPR Checker Step by Step
Run the scan. Enter your domain or key page URL. Include pages with forms, embedded media, checkout and marketing tags.
Test as a new visitor. Use a clean browser session so earlier choices do not affect the result.
Review pre-consent activity. Note cookies, scripts and requests that appear before any choice is made.
Test Reject and withdrawal. Confirm that rejected categories stay inactive and that visitors can change their mind as easily as they agreed.
Check third parties. Identify every external domain that receives data and confirm you know why it is there.
Fix and re-scan. Correct the issues, then run the checker again to confirm the changes worked.
Repeat the process after adding a plugin, changing your tag manager setup or launching a new campaign. New scripts are a common source of new findings.
What a GDPR Compliance Checker Cannot Do
A GDPR compliance checker only sees what is visible from outside your website. It cannot judge whether:
You chose the right lawful basis for each purpose.
Your privacy notice matches your internal processing.
Your retention rules are applied in your databases.
You can handle access and deletion requests on time.
Your supplier contracts and international transfer safeguards are adequate.
A clean scan is therefore not proof of compliance. Treat it as one piece of evidence alongside your records, contracts and procedures. Our GDPR compliance checklist covers the wider review, and our GDPR compliance services guide explains when specialist support is worth considering.
What to Do After a GDPR Check
Most findings follow familiar patterns:
Finding | Common cause | What to do |
Analytics or advertising cookies set before consent | Scripts added directly to pages or fired by a tag manager with no consent condition | Make those tags wait for consent, then re-test |
Reject does not stop tracking | Banner not connected to every tag and script | Link preferences to all scripts and test the Reject path |
Cookies missing from your cookie policy | A plugin or tag added after the last review | Update the inventory and policy, and schedule recurring scans |
Requests to unfamiliar third-party domains | Embedded widgets, pixels or plugins | Identify the vendor, decide whether it is needed, and review contracts and transfers |
Policy missing or out of date | Policy written once and not maintained | Update it to reflect actual processing |
Okito supports this work through cookie discovery, preference controls, configured tracking controls and consent records. See how it works on our cookie consent page. If you need policy documents, our privacy policy generator and cookie policy generator can help you start. Your organisation remains responsible for its wider data practices.
Frequently Asked Questions
There is no single best option, because tools test different things. A cookie scanner suits inventory work, a runtime audit suits consent enforcement and a questionnaire suits process reviews. Combining two types gives a more reliable picture than relying on one score.
No. A GDPR checker reviews what it can observe from outside your site. It cannot assess lawful bases, internal retention, supplier contracts or how you handle individual rights requests.
A cookie scanner mainly lists and categorises cookies. A GDPR checker has a wider aim and may also test consent behaviour, policy presence, third-party requests and security settings. Some tools combine both functions.
Run one after any change to scripts, plugins, your tag manager or your consent banner. Beyond that, schedule recurring scans at an interval that suits how often your site changes.
Yes. A banner that appears is not proof that it works. A checker can show whether non-essential cookies still load before consent or after a visitor rejects them.
It can. The GDPR may apply when you offer goods or services to people in the EU or monitor their behaviour there. Simply being accessible from Europe does not decide the question. Our GDPR compliance guide explains when the GDPR applies.
They can be useful, but accuracy depends on method and coverage. Some scan only a sample of pages, and static tools can miss scripts that load later. Use free tools to find issues, then verify important findings manually.
Türkçe
English