Currently a lot of legal warning take place in Germany and Austria on website owners who dynamically load Google fonts from Google’s sites.
As a common solution, one can locally host the according font and avoid the calls to Google.
While in the Hubspot Starter package this approach works for the Website pages by adapting the underlying template, one can only use the Landing Page templates that are provided by default (Basic, Stellar, Rally etc.).
The problem with these Started LP templates is that while you can change the default font, the resulting LP still loads the default font from Google.
E.g. changing the Vibrant LP to use only Verdana font, the LP still loads the default Rubik font from Google (see https://www.scalerion.com/temp8😞
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Rubik:regular&display=swap">
Potential options from our understanding:
a) Hubspot Landing Pages must not include Google calls if no Google font is used on that LP
b) Make it possible for Starter customers to edit the Landing Pages’ template code (as for Website pages)
c) Provide a clear LP template not using a Google font (and not including any calls to Google sites)
While I would assume that a) might be serious change to the technical approach of LPs and b) might not be the favorite solution for Hubspot’s sales teams, I would consider c) to be a pragmatic, easy to implement approach.
Again, please let me re-emphasize that this is a legal issue, making it impossible for Starter customers of Hubspot to use Landing pages in a lawful way.
Thanks, best
Sebastian