Dieter
← All articlesData protection explained

GDPR-compliant website? The self-check

You can check most of whether your website is GDPR compliant yourself, without prior knowledge and without special tools. This self-check takes you through twelve points, from the legal notice and everything that loads before the first click to forms and service providers. For each point, you learn how to check it, what the law requires and how often it was missed in our measurement of 10,389 websites.

Sebastian SchenkLegally reviewed by Franziska Breidenbach
Last reviewed: Thursday, 29 October 2026
GDPR-compliant website? The self-check

Table of contents

  1. In brief
  2. What “GDPR compliant” means for a website
  3. The twelve checkpoints at a glance
  4. How to check the mandatory information (points 1 to 3)
  5. What happens before the first click (points 4 to 7)
  6. Banner and rejection (points 8 to 10)
  7. Technology and service providers (points 11 and 12)
  8. What an automated website check can and cannot do
  9. Website builder, agency, theme: who is responsible
  10. What goes beyond the website
  11. What happens if your website is not compliant?
  12. The most common mistakes
  13. Checking your website with Dieter
  14. Conclusion

In brief

  • “GDPR compliant” is not a state a website reaches once, but the result of twelve points: mandatory information, nothing that requires consent before the first click, a banner that works, secure technology and contracts with your service providers. You can check most of them yourself in an hour.
  • The most common shortcoming is invisible: 68% of German websites contact third-party servers before visitors can click anything. That is what our measurement of 10,389 websites for the Data Protection Report 2026 shows. Usually there is no tracking behind it, but fonts, maps or spam protection.
  • A cookie banner proves nothing: on 76% of websites with third-party services, a click on “Reject” changed nothing technically.
  • You are responsible, even if your agency, theme or website builder made the setting.
  • A scanner finds the technical findings in a minute, but it does not do the legal assessment for you. Only the two together make a reliable check.

What “GDPR compliant” means for a website

At its core, three laws apply to your website:

  • The GDPR governs every processing of personal data. This already includes the IP address, which is sent to your server and to every embedded third-party server with each page view. Every transfer needs a legal basis (Art. 6 GDPR), and you have to provide information about it (Art. 13 GDPR).
  • § 25 TDDDG (German Telecommunications Digital Services Data Protection Act) governs access to visitors’ devices, i.e. cookies, local storage and scripts that read something there. It is only permitted with consent, unless it is strictly necessary for a service the visitor has explicitly requested.
  • § 5 DDG (German Digital Services Act) requires the legal notice (Impressum). That is not data protection, but it belongs in every website check.

The controller is whoever decides on the purposes and means of the processing (Art. 4(7) GDPR). For your website, that is you, and you have to be able to demonstrate compliance (Art. 24 GDPR). If you embed a third-party service, such as a map or a share button, you are jointly responsible for collecting the data and transmitting it to the provider, but in principle not for the provider’s subsequent processing. The Court of Justice of the European Union decided this using the example of an embedded “Like” button of a social network (judgment of 29 July 2019, C-40/17, Fashion ID). And every check is a snapshot: a new plugin or a theme update can change the result the next day.

The twelve checkpoints at a glance

No.CheckpointPassed if …Legal basis
1Legal noticeit can be reached from every page with one click and is complete§ 5 DDG
2Privacy policy reachableit can be reached from every page with one click, also on smartphones and while the banner is openArt. 12, 13 GDPR
3Privacy policy fitsevery embedded service is listed in it and nothing outdated isArt. 13 GDPR
4Quiet before the clicknothing that is not strictly necessary loads from third-party servers before a decisionArt. 6 GDPR, § 25 TDDDG
5Fonts and iconsthey come from your own serverArt. 6 GDPR
6Maps, videos, spam protectionthey only load on click or without any third-party contact§ 25 TDDDG, Art. 6 GDPR
7Analytics and advertisingthey only start after consent§ 25 TDDDG, Art. 6, 7 GDPR
8Bannerit is only shown when needed, and rejecting is as easy as acceptingArt. 4(11), Art. 7 GDPR
9Rejecting worksnothing that requires consent loads after “Reject”§ 25 TDDDG
10No leftoversno remnants of deactivated tools are still running§ 25 TDDDG, Art. 5 GDPR
11Transmission and formsevery page runs over HTTPS and forms only ask for what is necessary§ 19 TDDDG, Art. 5, 25, 32 GDPR
12Service providerscontracts are in place with your host and services, and US providers have been checkedArt. 28, 44 et seq. GDPR

How to check the mandatory information (points 1 to 3)

1. Legal notice. It must be “easily recognisable, directly accessible and permanently available” (§ 5(1) DDG), in practice via a link in the footer of every page, also on mobile. Mandatory details include your name and address, for companies the legal form and authorised representatives, an email address and a fast means of contact and, where applicable, the register entry. You can create a complete legal notice with the legal notice generator.

2. Privacy policy reachable. The information must be “easily accessible” (Art. 12(1) GDPR), from the time the data is collected (Art. 13 GDPR), which for a website means from the first page view. Check: is the link there on every page, even while the banner is open? In our measurement, no privacy policy could be found on 5.7% of websites, not even via the legal notice.

3. Privacy policy fits the website. The most common error in content: the policy dates from the time the website went online. Put the list of services from point 4 next to your policy. Each service needs its purpose, legal basis, recipients, any transfer to third countries and the storage period (Art. 13(1) and (2) GDPR). Services you no longer use have to go. The guide How to create a privacy policy explains the structure.

What happens before the first click (points 4 to 7)

This part matters most, because you cannot see it. All you need is your browser:

  1. 1Open your website in a private browser window.
  2. 2Open the developer tools (F12, on a Mac Option + Command + I) and go to the “Network” tab.
  3. 3Reload the page and do not click anything in the banner.
  4. 4Look at the list: every address that does not belong to your own domain is a third-party server.
  5. 5Repeat this on the subpages where more is typically embedded: contact, directions, careers, shop.

4. Quiet before the click. Every connection to a third-party server transmits the visitor’s IP address and needs a legal basis. In our measurement, 68% of websites contacted third-party servers before anyone could click anything; only 32.2% were completely quiet before the first click. Not every connection is unlawful; a payment service in the checkout, for example, can be justified. But every one has to be justifiable and listed in the privacy policy.

5. Fonts and icons from your own server. The most common reason for unrequested connections is not tracking: 21% of all websites reported the visit to Google solely because of fonts, maps or the reCAPTCHA spam protection. The Regional Court of Munich I awarded a visitor €100 in damages because a website loaded Google Fonts from Google’s servers without consent, although a local alternative existed (judgment of 20 January 2022, 3 O 17493/20). Serve fonts, icon fonts and script libraries from your own server.

6. Maps, videos and spam protection only on click. An embedded map or video that loads with the page connects to the provider immediately; youtube.com alone was contacted by 392 websites before the first click. The solution is a preview image that only loads the service after a click, because from that moment on the retrieval has been explicitly requested. For spam protection, there are methods without third-party contact. If all websites simply embedded Google Fonts, Google Maps and reCAPTCHA locally or on click, an additional 9.1% would be completely quiet before the first click. Without everything that can be avoided without losing any function, it would be 47.2% instead of 32.2%.

7. Analytics and advertising only after consent. Google Analytics, the Google Tag Manager or the advertising pixels of social networks are not necessary for operating your website and may only load after consent. On 15.0% of websites, a recognisable advertising or analytics tool ran before any consent; the Google Analytics cookie `_ga` was already set before the first click on 6.1%. What applies to analytics “without cookies” is explained in the guide Cookie banner: when is it required?

Technology and service providers (points 11 and 12)

11. Secure transmission and lean forms. Every page should run over HTTPS, and requests with “http://” should be redirected automatically. The law does not mention HTTPS by name, but § 19(4) TDDDG requires providers of digital services offered on a commercial basis to take safeguards in line with the state of the art, “in particular” an encryption method recognised as secure, and Art. 32 GDPR names encryption as a measure. A contact form without HTTPS can therefore hardly be justified. On top of that come security rules that the server passes on to the browser. They are not individually prescribed, but they only take a few lines of configuration; 65% of websites lacked them to such an extent that they received our lowest security rating.

For forms: only make the fields you need for processing the request mandatory (Art. 5(1)(c) and Art. 25(2) GDPR), and link to the privacy policy at the form. For a newsletter, you need demonstrable consent (Art. 7(1) GDPR), usually via a confirmation email (double opt-in).

12. Service providers and third countries. Your host and your form, newsletter, appointment booking or chat services process data on your behalf. You need a data processing agreement with each of them (Art. 28 GDPR); with large providers, you can usually conclude it in your customer account. The guide on the data processing agreement shows how to check it quickly. 47.9% of websites contacted at least one US provider before the first click. Transfers to third countries are only permitted under the conditions of Art. 44 et seq. GDPR. For US companies certified under the EU-US Data Privacy Framework, an adequacy decision of the European Commission has applied since 10 July 2023; the official participant list at dataprivacyframework.gov shows the certification. Otherwise, you need other safeguards such as the European Commission’s standard contractual clauses.

What an automated website check can and cannot do

A good scanner takes the most tedious work off your hands: recording what loads and when. The legal assessment remains with you.

QuestionA good scannerOnly you
Which third-party servers load before consent?yespossible via the Network tab, but tedious
Does “Reject” work?only if it also measures after a click on “Reject”yes, with the test from point 9
Which cookies are set?yesyes, in the developer tools
Does HTTPS work, are security rules set?yesto a limited extent
Is a privacy policy linked, are services missing from it?yes, as a comparisoncontent, purposes and legal bases
Is a service “strictly necessary”?nocase-by-case assessment
Is there a contract with the provider, is it certified?at most as a hintyes
Subpages, forms, areas behind a loginmostly only the home pageyes

A scanner establishes what a website does technically, not legal violations. That is also how we handle it in the methodology of our Data Protection Report. Whether a connection is justified in an individual case cannot be measured. So be careful with tools that certify a “GDPR-compliant” website after an automated run.

Website builder, agency, theme: who is responsible

The settings that make the difference are often not made by anyone consciously: the theme brings Google Fonts with it, the shop extension records where visitors come from by default. The result cannot be predicted. In our measurement, sector, federal state, company size and software together explain only 3.4% of the differences. Of the WordPress websites, 35% were completely quiet before the first click, while 14% scored 20 out of 100 points or less.

With hosted website builders, there is less room for manoeuvre: on one widely used hosted website builder, only 1.7% of websites in our measurement had no contact with third-party servers before the first click, because the builder itself loads from the provider’s network. These connections are part of the product and belong in the contract with the provider and in your privacy policy.

None of this changes your responsibility. What you can do:

  • Agency: Put in writing what you expect, for example fonts hosted locally, maps and videos on click, a properly connected banner. If the agency looks after the website on an ongoing basis, it is usually a processor and needs a contract.
  • Website builder: Check which settings the provider allows, conclude its data processing agreement and list the connections in your policy.
  • Theme and plugins: After every installation and every major update, use the test from point 4 to check what has been added.

What goes beyond the website

The self-check covers your website, not all of your data protection. These points apply to every company, regardless of the website:

  • Record of processing activities under Art. 30 GDPR, see Record of processing activities and deletion concept.
  • Technical and organisational measures under Art. 32 GDPR, see TOM.
  • Contracts with all service providers, not only those for the website.
  • Procedures for requests from data subjects, such as access requests, which you generally have to answer within one month (Art. 12(3) GDPR).
  • Procedures for data breaches, which may have to be reported within 72 hours (Art. 33 GDPR).
  • Data protection officer, generally mandatory if at least 20 people are regularly engaged in the automated processing of personal data (§ 38(1) BDSG, German Federal Data Protection Act).
  • AI chatbot on the website: since 2 August 2026, it has to disclose that it is an AI (Art. 50(1) AI Act). What applies is explained by Klaus in the article on AI labelling requirements.

What happens if your website is not compliant?

The supervisory authorities can order you to remedy an infringement and impose fines: under Art. 83 GDPR and, for cookies without consent, up to €300,000 under § 28 TDDDG. In our observation, enforcement against small websites rarely takes the form of fines and more often that of orders and cease-and-desist letters (Abmahnungen).

Visitors can claim damages (Art. 82 GDPR), usually small amounts: in the Munich Google Fonts case it was €100, and the Federal Court of Justice (BGH) considered around €100 reasonable in a case of mere loss of control over one’s own data (judgment of 18 November 2024, VI ZR 10/24). Anyone who deliberately provokes infringements with automated visits gets nothing; the Regional Court of Munich I held mass Google Fonts claims to be an abuse of rights (judgment of 30 March 2023, 4 O 13063/22). Competitors can pursue data protection infringements under competition law (Federal Court of Justice, judgments of 27 March 2025, I ZR 222/19 and I ZR 223/19). A dispute usually costs more time than the twelve points.

The most common mistakes

  • Checking once and never again. Every new plugin, theme update or embedded video can change the result. Check after every change and otherwise at least every six months.
  • Only checking the home page. The map is on the directions page, the video under “About us”, the form on the contact page.
  • Buying a banner instead of cleaning up. If you host fonts locally and load maps on click, you often do not need one at all.
  • Relying on your agency or website builder. You remain responsible.
  • Generating the privacy policy once and forgetting it. The policy has to match what is embedded today.
  • Adding an “I agree to the privacy policy” checkbox to the contact form. The policy informs; it does not need consent. As a rule, answering an enquiry does not require consent either.
  • Mistaking a scanner’s green result for a legal opinion. It measures technology, not lawfulness.
  • Forgetting contracts. A host or newsletter service without a data processing agreement is a classic.

Checking your website with Dieter

For points 2 to 7 and 11 and part of points 8 and 12, you do not have to record anything yourself. The free website scanner in the GDPR check-up checks your website without login in under 60 seconds: 13 checks in one report, including pre-consent (what loads before consent), tracking, third parties, hints on data processing and third-country transfers, and security headers. It compares the findings with your privacy policy, assesses the risk of your cookie banner and prioritises everything by urgency. It covers what loads when your home page is opened. You check subpages and whether “Reject” works (point 9) yourself with the Network tab test.

After that, the guided GDPR check-up goes beyond the website: it clarifies processes, processing activities, service providers and documentation with easy-to-understand questions and turns them into a prioritised roadmap. The privacy policy generator detects embedded services via a scan, knows over 1,000 of them and keeps your policy up to date via live embedding. If a data processing agreement with a service provider is missing, you can create it with Dieter under Data processing agreement.

Conclusion

Whether your website is GDPR compliant is decided at a few points that are easy to check: mandatory information that can be reached and is correct, nothing that requires consent before the first click, a banner that works, secure transmission and contracts with your service providers. Most shortcomings are not intentional, but default settings that nobody ever touched. If you host fonts locally, load maps and videos on click and remove old tools, you will have done most of the work in an afternoon. Use the scanner for the technology; the assessment stays with you, and because every website changes, the check becomes a routine.

Author

Sebastian Schenk

Co-Founder & CEO

Lawyer and data protection officer. Drives product vision at simply Legal and ensures Dieter is sound legally and in practice.

Sources and further reading

Frequently asked questions

How can I check my website for GDPR compliance for free?

With your browser and a little time: open your website in a private window, look in the developer tools under the “Network” tab to see which third-party servers load before the first click, and compare them with your privacy policy. It is quicker with a free scanner such as the one in Dieter’s GDPR check-up. You will always have to check contracts with service providers and the legal assessment yourself.

Is an automated GDPR check enough for my website?

For the technology yes, for the legal assessment no. A scanner reliably shows which services load and when, which cookies are set and whether HTTPS works. It cannot establish whether a service is strictly necessary, whether a data processing agreement is in place or whether a US provider is certified. Use the scan as a finding and check the open points yourself.

Does every website need a privacy policy?

Practically every business website does. As soon as a page is opened, your server processes the visitor’s IP address, and you have to provide information about that (Art. 13 GDPR). The policy must be easy to reach from every page, usually via a link in the footer. In our measurement, no privacy policy could be found on 5.7% of websites.

Is HTTPS mandatory for a website?

No law mentions HTTPS by name. However, § 19(4) TDDDG requires safeguards in line with the state of the art and expressly names an encryption method recognised as secure, and Art. 32 GDPR names encryption as a measure. At the latest when your website has a form or a login, HTTPS is therefore mandatory. Many hosts include a certificate at no extra cost.

Is a WordPress website automatically GDPR compliant?

No. Whether a WordPress website is privacy-friendly depends on the theme, the plugins and their default settings, not on WordPress itself. In our measurement, 35% of WordPress websites were completely quiet before the first click, while 14% scored 20 out of 100 points or less. Check what newly loads after every installation and every update.

Who is liable if my agency set up the website incorrectly?

Towards visitors and authorities, you are liable as the operator, because you are the controller for your website (Art. 4(7) GDPR). Whether you can recover the damage from the agency depends on your contract. So put in writing what the agency is to implement, and conclude a data processing agreement if it looks after the website on an ongoing basis.

How often should I check my website for data protection?

After every change that embeds something new: a plugin, a theme update, a map, a video, a new form. Without such changes, checking every six months makes sense, because providers also change their services and default settings on their own. A scanner turns the repetition into a matter of one minute.

This article reflects the position at the date of publication. We update our content when the law changes.

Related articles

Dieter helps you avoid fines

Ready to go

Dieter takes care of your data protection.

Get started without a demo call and set up your data protection in a few steps.

Get started