Trackum

Website GDPR compliance check: what you can test yourself

With browser developer tools, you can check in about 20 minutes which services and cookies your site loads. Here is what you can clarify yourself and what you cannot.

Guide · · 5 min read · Written with AI, AI-assisted review on

Website GDPR compliance check: what you can test yourself
📷 Georg Bommeli · Unsplash

What is a website GDPR compliance check?

A website GDPR compliance check examines which services, cookies and data transfers arise when the site is visited and whether that fits consent and the privacy policy. You can check the technical part yourself, with a browser and about 20 minutes. The legal assessment can be made only by a lawyer or a data protection officer. This article is not legal advice.

The General Data Protection Regulation (GDPR) governs how you process personal data. For cookies and similar access to visitors’ devices, Section 25 of the German Telecommunications Digital Services Data Protection Act (TDDDG) also applies in Germany. Under it, storing and reading information on a device generally requires consent, unless it is technically strictly necessary for a service the user has expressly requested. A check must therefore separate two questions: what happens technically on the site? And is that legally in order?

What can you check yourself, and what only a specialist?

Everything that becomes visible in the browser, you can observe yourself. You can assess it only with legal knowledge. The table shows the split.

Check points at a glance
Check pointWhat you see yourselfWhat a specialist assesses
Services before consentWhich requests to Google, Meta or other providers already run before the click in the bannerWhether a service may run without consent at all
CookiesName, domain and lifetime of every cookie setWhether a cookie is technically strictly necessary
Cookie bannerWhether Reject is on the first layer and designed just like AcceptWhether design and texts meet the requirements
Privacy policyWhether every service found is named thereWhether legal bases, retention periods and recipients are described correctly
Contracts and third countriesWhich domains receive requestsData processing agreements and data transfers to countries outside the EU

→ Cookie banner with Consent Mode v2: compliant, with no monthly licence

This question is the most important part of the check. Open a new incognito window in Chrome so that no old consent is stored. Then go to your home page without clicking anything in the banner. This is how to proceed:

  • Open Chrome DevTools (Cmd+Option+J on a Mac, Ctrl+Shift+J on Windows) and select the Network tab before you load the page. Chrome logs only while DevTools are open.
  • Reload the page and do not click anything in the banner yet.
  • Look in the list for requests to analytics and advertising services, for example to google-analytics.com, doubleclick.net or facebook.com. With the filter box and the input domain:facebook.com, you hide everything else.
  • Open Application, then Storage, then Cookies. Select your domain there. Note all cookies that are already present before the click in the banner.
  • Click Reject, reload and repeat both observations. Then do the same with Accept and compare the three results.

Google Tag Manager itself often loads before consent. What matters is whether requests to analytics or advertising services follow. Whether that is permissible in an individual case, for example with Google Consent Mode, is for a specialist to clarify. After Reject, no cookies from analytics and advertising services should be present in any case. Also check subpages such as the contact page or the checkout, because some services are attached only there.

Check whether the first layer of the banner contains a Reject all option that is just as visible as Accept all, that is, in size, colour and position. The cookie banner taskforce of the European Data Protection Board (EDPB) reported in January 2023 that, in the view of the large majority of the supervisory authorities involved, a banner without a reject option on the first layer is not compatible with valid consent, and pre-ticked boxes do not lead to valid consent. Individual authorities saw it differently, and the report is not binding. So it shows how supervisory authorities interpret the rules and is not a verdict on your site.

  • Reject all is on the first layer and is just as easy to find as Accept all.
  • There are no pre-ticked boxes for analytics and advertising.
  • Rejecting is not possible only via a detour through the settings.
  • Consent can later be withdrawn just as easily, for example through a link in the footer (Art. 7(3) GDPR).

→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant

Does the privacy policy name all services?

Compile a list of all services found in the previous steps and read the privacy policy alongside it. Under the information obligations in Art. 13 GDPR, every service that processes data should appear there with provider, purpose and recipient. Typical gaps arise with services that came later: a Meta Pixel for a campaign, an embedded video, a map or a chat widget. Conversely, a service that was removed long ago often still stands in the text. That is a finding too.

Example: a painting and decorating business with a contact form

A painting and decorating business has a page with a contact form, Google Maps and a Meta Pixel that an agency built directly into the theme a year ago. In an incognito window, the Network panel shows requests to facebook.com on the very first load, before anyone clicks the banner. After Reject they remain, because the pixel is hard-coded in the theme and the banner does not control it. The privacy policy also lacks Google Maps. The business notes three findings, passes them to its data protection officer and has the pixel moved into Google Tag Manager, where it is tied to consent.

What can an automatic check do?

Online scanners load your site in a browser and list cookies and requests. That saves time when taking stock, especially across several subpages. But they see only what happens on loading. Services that start only after an input or in the checkout often go undetected. No scanner answers legal questions. Trackum’s free check opens your home page three times in a real browser, without answering the banner, after Reject and after Accept, plus two subpages. The check shows which tags and cookies load in the process. It does not fill in forms or trigger purchases.

When does a finding belong with a specialist?

As soon as your list contains points that need an assessment: services before consent, data with providers outside the EU, an unclear legal basis or missing contracts. Give the specialist the list with service, domain, time (before or after consent) and a screenshot. Then the consultation takes less time. Repeat the check after every relaunch, plugin update or new advertising service, because the situation changes with every integration.

Frequently asked questions

Can I check my website for GDPR for free?

The technical part, yes: with browser developer tools, you see which services and cookies load. Free online scanners help too. The legal assessment of the findings remains a task for a lawyer or a data protection officer.

Is an online checker tool enough for the GDPR?

A scanner shows what happens when the page loads. That saves a lot of time when taking stock. But it does not assess legal bases or contracts, and it does not see services that start only after an input or in the checkout.

Is my website automatically GDPR compliant if it has a cookie banner?

No. A banner is only one part. What matters is whether analytics and advertising services really load only after consent, whether rejecting is equally possible and whether the privacy policy matches the services.

How often should I check my website for data protection?

Check after every relaunch, every plugin update and every new advertising or analytics service. A fixed date can also help, for example once a quarter, because integrations in Tag Manager and in plugins change unnoticed.

Sources

  1. Gesetze im Internet: Section 25 TDDDG gesetze-im-internet.de
  2. Data Protection Conference (DSK): guidance for providers of digital services datenschutzkonferenz-online.de
  3. European Data Protection Board: report of the cookie banner taskforce (2023) edpb.europa.eu
  4. Chrome for Developers: View cookies in DevTools developer.chrome.com
  5. Chrome for Developers: Network panel in DevTools developer.chrome.com
Help