Check your website for GDPR and cookie problems

Free scan, results in about ten seconds. We look at what your page loads before a visitor has agreed to anything, and tell you what to fix first.

Free, no sign-up. We don’t store your IP address.

What the scan checks

  • Cookie consent bannerWhich consent tool you use, if any
  • Tracking before consentAnalytics and ad scripts that run before a visitor agrees
  • Cookies before consentCookies your server sets on the very first visit
  • Embeds and fontsGoogle Fonts, YouTube, Maps and other third parties
  • Privacy policyA link visitors can actually find
  • FormsPersonal data sent securely, with a privacy notice
  • Contact details and HTTPSA way to reach you, a valid certificate and HSTS

The problems we find most often

Most sites don’t fail because they ignore the GDPR. They fail on a handful of technical details that are easy to miss and quick to fix.

Google Analytics or Tag Manager is added straight into the theme, so it runs on page load, before the banner is even answered. Under the ePrivacy rules, analytics cookies need an opt-in first.

Privacy-friendly analytics options

Google Fonts loaded from Google

Every page view sends the visitor’s IP address to Google. A Munich court awarded damages over exactly this in 2022. Hosting the font files yourself removes the problem and often speeds up the site.

How to host Google Fonts locally

A banner without a real “Reject” option

Regulators expect refusing to be as easy as accepting. A banner with only “Accept” and a hidden settings link is one of the most common reasons for complaints and fines.

Cookie consent rules in 2026

YouTube videos and maps that load straight away

A standard YouTube or Google Maps embed sets cookies as soon as the page opens. Use YouTube’s privacy-enhanced mode, or show a placeholder that loads the embed after a click.

Other common WordPress mistakes

A privacy policy that is missing pieces

Article 13 lists what visitors must be told: who you are, why you collect data, the legal basis, how long you keep it, who receives it and how to complain. Generic templates often skip half of it.

Write a complete privacy policy

Data requests nobody knows how to answer

Anyone can ask what data you hold about them, and you have one month to reply. Without a contact address and a simple process, that deadline is easy to miss.

Handle a data access request

How the score works

Each check carries points according to how much it matters. A pass earns all of them, a warning half, a problem none. Your score is the share of points earned, shown as stars out of twelve.

Consent carries the most weight, because that is where regulators look first. Forms only count when the page has a form.

  • Cookie consent banner20 pts
  • Tracking before consent20 pts
  • Cookies before consent20 pts
  • Privacy policy15 pts
  • HTTPS15 pts
  • Embeds and fonts10 pts
  • Forms10 pts
  • Contact details5 pts

ConsentTransparencySecurity

More free tools and guides

  • GDPR fine calculator

    Tool

    See the maximum fine under Article 83 for your company’s turnover, next to real fines for similar violations.

    Calculate a fine
  • Guide

    What a compliant banner needs today, and what the EU Digital Omnibus will change.

    Read the guide
  • GDPR for WordPress sites

    Guide

    Plugins, hosting, forms and analytics: a practical overview for site owners.

    Read the guide

Latest guides and news

Practical articles on cookie consent, privacy policies, plugins and new EU rules, written for people who run websites.

Questions about the scan

Something not covered here? Send us a message.

Does a good score mean my website is GDPR compliant?

No. The scan checks the technical side of one page: what loads, which cookies are set and whether key links are there. GDPR compliance also covers things no scanner can see, such as how you store customer data, who can access it and whether your privacy policy is accurate. Treat the score as a checklist of quick wins.

What can’t the scan see?

We read the page the way your server sends it, without running its JavaScript. Cookies created later by scripts, content behind a login and other pages of your site are not included. Some sites also block automated visitors, in which case the scan stops with an explanation.

For the full picture, open your site in a private browser window, don’t touch the banner, and check the Network and Cookies panels in the developer tools.

Does every website need a cookie banner?

Only if it uses cookies or similar technology that is not strictly necessary, such as analytics, advertising, social media widgets or most video embeds. A site with only session and security cookies, or with cookieless analytics like Plausible, usually doesn’t need one. It still needs a privacy policy.

Is Google Analytics allowed under the GDPR?

Yes, if it only starts after the visitor has agreed, and your privacy policy explains the data transfer to Google in the US. Google Consent Mode v2 helps with the first part. If you want to avoid consent entirely, a cookieless, EU-hosted analytics tool is the simpler route.

Are Google Fonts really a GDPR problem?

Loading fonts from Google’s servers sends each visitor’s IP address to Google without a legal basis. In January 2022 a Munich court ordered a website owner to pay damages for this. Hosting the font files on your own server solves it completely.

What happens to the addresses I scan?

We keep the result for 30 minutes so repeated scans are fast, and we record the scanned domain, its score and the consent tool we found, for statistics. We don’t store your IP address: rate limiting uses a one-way hash that changes daily and is deleted within an hour.

This tool gives general guidance, not legal advice. Results are produced automatically from a single page and can be incomplete or wrong. GDPR obligations depend on your business, the data you process and where you operate. For a full assessment, talk to a qualified data protection professional.

Scroll to Top