Free · no signup · instant result

Google Fonts checker: loaded externally or locally?

Enter a URL and see right away whether the page references Google Fonts servers. You get the actual spots it found, not a panic traffic light.

The query string and fragment are stripped before the fetch. No e-mail, no lead storage. Please do not enter private, internal or access-protected URLs.

Transparent, not alarmist

What the checker actually sees

A deliberately bounded technical snapshot, with the gaps spelled out.

HTML of the target page

Links, preloads, preconnects, inline CSS and direct references to fonts.googleapis.com or fonts.gstatic.com.

Up to 20 stylesheets

Linked CSS files are read as well, including ones on a CDN or another domain. Internal and private addresses stay blocked.

Where it sits, and the fix

The report names the host, the mechanism and the source file. It deliberately never claims a whole website is legally safe.

Your input

The check needs no signup

The scanner fetches the website you enter without your cookies or credentials. The URL and the result are neither stored as a lead nor sent by e-mail, and they are not in the anonymous usage statistics either. Cloudflare Turnstile protects the public check against abuse.

Site measurement starts without a cookie banner, and an earlier stored objection is respected. Providers, data types and contact options are listed in the privacy notice.

Conversion tracking

Measurable, without passing on the domain you checked

Starting and finishing the check are recorded as product events inside site measurement. The marketing event carries only the tool name and the result status, never the URL or domain you entered. A consultation counts as a primary conversion only once the booking is confirmed, not when someone clicks the button.

FAQ

Common questions about the Google Fonts checker

What does the Google Fonts checker look at?

The checker fetches the public page you enter from the server side and scans its HTML plus up to 20 stylesheets linked from it for references to fonts.googleapis.com and fonts.gstatic.com. Stylesheets on other hosts, such as a CDN, are read too. It shows you where each reference sits and, where the URL makes it readable, the font family name.

Is a green result a complete privacy review?

No. The result is a technical snapshot of this one URL. Content loaded by JavaScript, iframes, other subpages, logged-in areas and states after a cookie choice can stay hidden. A legal assessment needs a review of how the fonts are actually used on top of this.

Do locally hosted Google Fonts need cookie consent?

With local hosting the font files come from your own web server, so the visitor browser never opens a connection to Google Fonts for them. Whether other technologies on the page need consent is a separate question.

Can a cookie banner fix external Google Fonts?

Only if the external font is reliably blocked until valid consent arrives. That often produces a visible font swap when someone declines, and it breaks easily. Local hosting is the more robust default.

What happens to the URL I enter?

The query string and fragment are stripped before the fetch. The checker does not store the target URL or the result as a lead and does not e-mail them anywhere. Short-lived technical server and abuse-protection data follow the privacy policy.

Found Google Fonts, and the tracking looks murky too?

I check the actual requests before and after the cookie choice, set up local fonts, and document Consent Mode and the conversion tags so you can follow every step.

Free & no obligation Reply within 24h You talk to me directly