Free SEO tool
Google Fonts Checker
Checks in seconds whether a website loads Google Fonts from Google's servers. Under the GDPR, this embed transfers visitor IP addresses without consent.
No sign-up, the result appears right here on this page. The request runs through our data centre in Frankfurt (AWS); URLs and results are not stored. Privacy policy
Note: this tool performs a purely technical check and is not legal advice.
How to fix it
- Download the fonts from
fonts.googleapis.com - Host the font files on your own server (for example in
/fonts/) - Update your CSS:
@font-facewith local paths instead of Google URLs - Remove all
<link>tags and@importrules pointing to Google Fonts - Remove preconnect hints to
fonts.googleapis.comandfonts.gstatic.com - Clear your cache and run the check again
Why external Google Fonts are a problem
In January 2022 the Regional Court of Munich ruled that embedding Google Fonts dynamically without consent violates the GDPR (case 3 O 17493/20). On every page view, the visitor's IP address is transferred to Google, and an IP address is personal data. The ruling triggered thousands of cease-and-desist letters in Germany with demands between 100 € and 250 €. The underlying GDPR logic applies across the whole EU.
The fix is technically simple: download the font files as WOFF2 (for example with the Google Webfonts Helper), host them on your own server and embed them via @font-face. External <link> tags, @import rules and preconnect or dns-prefetch hints for fonts.googleapis.com and fonts.gstatic.com have to go. After that, no data leaves your own domain, and the page usually loads faster because one external connection disappears.
On WordPress, many themes, plugins and page builders such as Elementor or Divi load Google Fonts through their own mechanisms, even after installing plugins like "OMGF". Hidden fonts in child themes, inline styles or lazily loaded scripts are the most common reason the checker still reports findings after a migration. The checker detects all common embed paths:
<link>tag to fonts.googleapis.com in the<head>- CSS
@importin external stylesheets - Preconnect to Google servers without visible font usage
- Fonts loaded dynamically via JavaScript or page builders
Frequently asked questions
What exactly is the problem with Google Fonts?
When a website embeds Google Fonts via fonts.googleapis.com, the visitor's browser opens a direct connection to Google's servers. This transfers the IP address, which counts as personal data under the GDPR. Without prior consent, that can be a compliance problem. For legal questions, talk to a data protection officer or a specialised lawyer.
What fines or claims are possible?
In 2022 the Regional Court of Munich awarded a claimant 100 € in damages (case 3 O 17493/20). A wave of cease-and-desist letters followed in Germany, often demanding 100 € to 250 €. The legal situation can change, so get up-to-date advice from a lawyer if you are affected.
Is a cookie banner enough?
In theory you could load Google Fonts only after consent. In practice this is a poor solution: the fonts appear only after the cookie opt-in, which causes layout shifts (CLS) and hurts the user experience. The clean fix is self-hosting the fonts. Then no consent is needed at all.
Is the Google Fonts Checker free?
Yes, the tool is completely free and requires no sign-up. You can check up to 10 URLs per minute. Feel free to link to the checker or recommend it.
Do you store my data?
The URL you enter is fetched through our server (AWS, Frankfurt data centre) so the analysis also works on sites with CORS restrictions. The evaluation itself then runs in your browser. We store neither URLs nor results.
My site runs on WordPress - can I fix this myself?
Plugins like "OMGF" or "Local Google Fonts" help. However, many themes, plugins and page builders load Google Fonts through their own mechanisms, so external requests can remain even after installing a plugin. Run the checker again after the change to be sure.