Google Fonts Checker - test your site for Google Webfonts
With our Google Fonts Checker, you can test your website for the presence of Google fonts in just a few seconds.
Free GDPR quick check
How can you detect the use of Google Fonts?
In addition to the practical tool, it is also very easy to check the established domain connections in the browser console under the Network tab.
Simply open your browser's developer console (via the menu or right-click - > Inspect).
After reloading the page (or while scrolling), you will see which domains connections are being established to - for example, these can also be Google Fonts requests (fonts.googleapis.com).
Current Google Fonts warning wave (in Austria) - how should you respond?
At the moment, many website operators are receiving a legal warning for using Google Fonts, first on a large scale in Austria, and now also in Germany .
How should you respond now?
First of all: stay calm and carefully check your own website or that of the affected client, or have it checked - embed the fonts locally and, if possible, fix all other GDPR violations as well.
Whenever possible, the integration of all external resources should be handled via a cookie banner (Complianz, Borlabs Cookie, Real Cookie Banner or similar).
I personally recommend not responding to the mass cease-and-desist letter in any way at first, but I am expressly not providing legal advice here.
It can be assumed that websites were systematically visited by a bot. According to wbs-law, that could violate the principle of good faith. The general recommendation is: host fonts locally, fix GDPR issues, and file it under P 🗑️
Google Fonts and cookie check - from 59 €
We'd be happy to take the work off your hands, embed Google Fonts locally, and implement all GDPR requirements technically for you.
Google Fonts only: 39 € incl. VAT
Google Fonts incl. cookie banner / content blocker setup/configuration: 65 - 97 € net
Embed fonts locally in WordPress
Option 1: Download the fonts with Webfonts Helper - integrate the .woff, .woff2 files via the theme CSS (Customizer or child theme style.css) and disable the fonts loaded afterward in the theme.
Option 2: Plugins for local integration: OMGF, Local Google Fonts, Borlabs Font Blocker.
Font plugins often work, but not always - dynamic local integration is the most sensible strategy when using multiple fonts in many variants.
Beyond the theme, the plugins must also be considered (page builders in all variations, Revolution Slider, etc.) - these are only partially covered by font plugins.
YouTube, Google Maps, ReCaptcha and other GDPR violations
Consent for all third-party services must be obtained from the user in advance. Instead of Google's ReCaptcha, we recommend form honeypots, local captchas, time locks, or better server-side validation of form input.
For content loaded later such as Google Maps and videos, iframes, widgets, and tracking scripts, a cookie consent plugin is required.
Complianz, Borlabs Cookie, and Real Cookie Banner are well suited.
