Earlier this year, you might have heard that a German court ruled that embedding Google Fonts on your website without the user’s consent could be against the law. This is because the user’s IP is passed directly to Google when the file is downloaded. The European Union’s General Data Protection Regulation, also known as GDPR, classifies user IPs as personally identifiable information (PII). So the website operator must obtain the user’s explicit consent.
But don’t worry, there are solutions how to handle this issue:
- Embed the fonts locally
- Use another source without IP tracking
How to find Google Fonts
Now that we’ve learned how to change websites so that they no longer use Google servers to load fonts, there’s still the big unknown of where.
Especially as an agency, it’s hard to get an overview of all projects, websites, and subpages and know where Google Fonts might be integrated. To help you with this, the 360 Monitoring Team has extended the Full Site Check and now also checks whether a website still embeds the fonts directly from the Google CDN:
Integrating a Google Fonts check was a step forward, but we’re not done yet.
Let us know in the comments what checks we should introduce in the future to help you be more productive.