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?
Besides the practical tool, it is also very easy to check in the browser console the domain connections established in the Network tab.
Simply open your browser’s developer console (via the menu or right-click -> Inspect).
After reloading the page (or even when scrolling), you can see which domains connections are being established to - these may include Google Fonts requests, for example (fonts.googleapis.com).
Current wave of Google Fonts warning letters (in Austria) - how should you respond?
Many website operators are currently receiving warning letters, first on a large scale in Austria, and now also in Germany due to the use of Google Fonts.
How should you respond now?
First of all: Stay calm and carefully review your own website or that of the affected client, or have it reviewed - embed the fonts locally and, if possible, remedy all other GDPR violations as well.
The integration of as many external resources as possible should be handled via a cookie banner (Complianz, Borlabs Cookie, Real Cookie Banner, or similar).
My personal recommendation is not to respond in any way to the mass warning letter for the time being; however, I expressly do not provide legal advice here.
It can be assumed that websites were systematically visited here by a bot. According to wbs-law, this could violate the principle of good faith. The general recommendation is: embed fonts locally, fix GDPR issues, and file it under P 🗑️
Google Fonts und Cookie Check - from €59
We’d be happy to take care of the work for you, embed Google Fonts locally, and technically implement all GDPR requirements for you.
Google Fonts only: €39 incl. VAT
Google Fonts incl. cookie banner / content blocker setup/configuration: €65 - €97 net
Host fonts locally in WordPress
Option 1: Webfonts Helper download of the fonts - integration of the .woff, .woff2 files via the theme CSS (Customizer or child theme style.css) and deactivation of the externally loaded fonts in the theme.
Option 2: Plugins for local hosting: OMGF, Local Google Fonts, Borlabs Font Blocker.
Font plugins often work, but not always - dynamic local hosting is the most sensible strategy when using multiple fonts in many variants.
Beyond the theme, the plugins must also be considered (page builders of all kinds, Revolution Slider, etc.) - these are sometimes not covered by font plugins.
YouTube, Google Maps, ReCaptcha and other data protection violations
Consent for all third-party services must be obtained from the user in advance. Instead of Google's ReCaptcha, form honeypots, local captchas, time locks, or better server-side validation of form entries are recommended.
For externally loaded content 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.
