{"id":9040,"date":"2021-12-09T11:17:07","date_gmt":"2021-12-09T10:17:07","guid":{"rendered":"https:\/\/www.myagileprivacy.com\/how-to-install-google-fonts-in-compliance-with-gdpr\/"},"modified":"2026-01-02T15:09:11","modified_gmt":"2026-01-02T14:09:11","slug":"how-to-install-google-fonts-in-compliance-with-gdpr","status":"publish","type":"post","link":"https:\/\/www.myagileprivacy.com\/en\/how-to-install-google-fonts-in-compliance-with-gdpr\/","title":{"rendered":"How to install Google Fonts in compliance with GDPR"},"content":{"rendered":"<p>Utilize Google Fonts to enhance your website\u2019s appearance with a wide selection of fonts hosted on Google\u2019s servers. To ensure GDPR compliance and prevent data transmission without explicit consent, it\u2019s crucial to install Google Fonts in a privacy-friendly way. Let\u2019s see how to achieve this using My Agile Privacy<sup>\u00ae<\/sup>.<\/p>\n<p>If you use a page builder that automatically includes Google Fonts, you\u2019ll find guidance at the end of this article on how to embed and serve fonts locally for GDPR compliance.<\/p>\n<h2>Solution 1 \u2013 Automatic Scan<\/h2>\n<p>You can use the advanced \"Cookie Shield\" feature, which can automatically detect Google Fonts.<br \/>\nSimply set the Shield to \"Learning\" mode and browse your site\u2019s pages\u2014the plugin will scan and prepare your configuration automatically.<br \/>\n<strong>However, for optimal graphic rendering and better control, manual configuration is recommended for Google Fonts.<\/strong><\/p>\n<h2>Solution 2 \u2013 Manual Configuration<\/h2>\n<h3>Part 1 \u2013 Identifying the Google Fonts Code<\/h3>\n<p>First, locate the code for the Google Fonts you wish to use.<br \/>\nDepending on your selection, the embed code will look like this:<br \/>\n<img decoding=\"async\" class=\"alignnone size-full wp-image-4765\" src=\"https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/google-fonts-1.png\" alt=\"\" width=\"1920\" height=\"342\" srcset=\"https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/google-fonts-1.png 1920w, https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/google-fonts-1-300x53.png 300w, https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/google-fonts-1-1024x182.png 1024w, https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/google-fonts-1-768x137.png 768w, https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/google-fonts-1-1536x274.png 1536w\" sizes=\"(max-width: 1920px) 100vw, 1920px\" \/><\/p>\n<h3>Part 2 \u2013 Adding the Google Fonts Cookie in My Agile Privacy<sup>\u00ae<\/sup><\/h3>\n<p>In your WordPress admin, go to <em>My Agile Privacy<sup>\u00ae<\/sup> \u2192 Cookie List<\/em> from the left menu.<br \/>\nYou\u2019ll see a list of cookies imported during plugin installation, all initially set to draft.<br \/>\nPublish only the cookies relevant to your website.<br \/>\n<img decoding=\"async\" class=\"aligncenter size-full wp-image-9467\" src=\"https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/11\/cookielist-en.jpg\" alt=\"\" width=\"1000\" height=\"303\" srcset=\"https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/11\/cookielist-en.jpg 1000w, https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/11\/cookielist-en-300x91.jpg 300w, https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/11\/cookielist-en-768x233.jpg 768w\" sizes=\"(max-width: 1000px) 100vw, 1000px\" \/><br \/>\nOn this screen, you will see several columns:<\/p>\n<ul>\n<li><em>Cookie Name<\/em>: the name of the cookie.<\/li>\n<li><em>Is Necessary<\/em>: indicates if the cookie is essential for your site\u2019s operation. If the site breaks without it, it will be marked as essential (this is pre-filled for you).<\/li>\n<li><em>Auto Update<\/em>: determines if the reference text for the cookie is kept automatically up-to-date for GDPR compliance. If set to \"yes,\" the plugin manages updates.<\/li>\n<li><em>Installation Type<\/em>: the method used for including the cookie. This varies according to your setup and is detailed in the guides.<\/li>\n<\/ul>\n<p>To add Google Fonts, search for \"Google Fonts (Google Inc.)\" in the list and click on it.<br \/>\nThe detail page includes pre-filled informational text and two blank fields for code input. This pre-filled text appears in your cookie policy and remains up-to-date if \"Allow Automatic Update\" is enabled.<br \/>\nBelow, select \"Installation Type\" (Javascript and Noscript, or Raw). Select \"Raw Code\" to reveal the \"raw html code\" field.<\/p>\n<h3>Part 3 \u2013 Adding the Google Fonts Embed Code<\/h3>\n<p>Paste the Google Fonts embed code directly into the \"Html Raw Code\" field.<br \/>\n<img decoding=\"async\" class=\"aligncenter size-full wp-image-9495\" src=\"https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/cookie-raw-code2-en.jpg\" alt=\"\" width=\"1000\" height=\"304\" srcset=\"https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/cookie-raw-code2-en.jpg 1000w, https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/cookie-raw-code2-en-300x91.jpg 300w, https:\/\/www.myagileprivacy.com\/wp-content\/uploads\/2021\/12\/cookie-raw-code2-en-768x233.jpg 768w\" sizes=\"(max-width: 1000px) 100vw, 1000px\" \/><br \/>\nRemember to save and publish the cookie by clicking the blue \"Publish\" button in the upper right corner.<\/p>\n<h2>Final Step \u2013 Verifying Operation<\/h2>\n<p>Now, verify that Google Fonts loads properly on your website.<br \/>\nYou\u2019ll notice that your chosen fonts are not loaded (the browser\u2019s default font will be used instead) until explicit consent to use Google Fonts is given\u2014either by clicking \"I agree\" on the cookie consent bar, or by going to \"Customize\" and activating the corresponding cookie.<\/p>\n<h2>Bonus \u2013 What if You Use a Page Builder or Plugin That Incorporates Google Fonts?<\/h2>\n<p>Many page builders, such as Elementor and Visual Composer, and dedicated plugins, can automatically embed Google Fonts while offering rich font customization. However, this often does not guarantee GDPR compliance.<br \/>\nTo address this issue, consider using the <a href=\"https:\/\/wordpress.org\/plugins\/embed-google-fonts\/\" target=\"_blank\" rel=\"noopener\">Embed Google Fonts plugin<\/a>.<br \/>\nThis plug-and-play solution allows you to automatically download your selected Google Fonts and host them locally on your server.<br \/>\nYou simply identify the fonts used by your themes or plugins, download them to your website, and update your setup to use these locally hosted files instead of fetching them from Google\u2019s servers.<br \/>\nWith this approach, your website remains GDPR compliant without sacrificing flexible font customization options.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Utilize Google Fonts to enhance your website\u2019s appearance with a wide selection of fonts hosted on Google\u2019s servers. To ensure GDPR compliance and prevent data transmission without explicit consent, it\u2019s crucial to install Google Fonts in a privacy-friendly way. Let\u2019s see how to achieve this using My Agile Privacy\u00ae. If you use a page builder [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":8712,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[33],"tags":[35],"class_list":["post-9040","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cookies","tag-free"],"acf":{"visibilita_box_autore":false,"autore_associato":null,"elenco_faq_articolo":null,"url_esterno":"","titolo":"Google Fonts"},"_links":{"self":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9040","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/comments?post=9040"}],"version-history":[{"count":7,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9040\/revisions"}],"predecessor-version":[{"id":15165,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9040\/revisions\/15165"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/media\/8712"}],"wp:attachment":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/media?parent=9040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/categories?post=9040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/tags?post=9040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}