# Google Fonts check: Find external fonts on your website

> Run a Google Fonts check on your website: find external font requests in browser developer tools, identify the source and verify the correction.

- Quelle: https://bezahlbare-webseite.de/en/ratgeber/google-fonts-check/
- Datum: 2026-11-21
- Sprache: en
- Thema: Recht & Datenschutz

A Google Fonts check shows whether your website downloads fonts directly from Google servers. You can verify this without programming skills in the browser: actual network requests to fonts.googleapis.com or fonts.gstatic.com matter more than a setting shown by a theme or plugin.

## What does a Google Fonts check test?

With dynamic integration, the browser usually loads a CSS file from fonts.googleapis.com and then font files from fonts.gstatic.com. Google documents this process for the Fonts CSS API. Source: Google Fonts Developer Documentation, accessed 21 November 2026.

The test must therefore examine the traffic generated during a page visit. A font may have a different name in the source code, be stored locally or be added later by a form, page builder or embedded service. Seeing a Google font family in the design does not by itself prove that the browser contacts Google.

In Germany, dynamic loading became particularly relevant after the Munich Regional Court I judgment of 20 January 2022, case 3 O 17493/20. In that specific case, the court regarded the transfer of the visitor's IP address to Google without the required legal basis as an infringement. This guide is not legal advice; it provides a technical test procedure.

## How can I check a website for Google Fonts?

Open the website in Chrome, Edge or Firefox and launch the developer tools. In Chrome and Edge, press F12 or use More tools → Developer tools. Select Network, enable Preserve log and reload the page.

Enter font in the filter and then search separately for googleapis and gstatic. Open suspicious entries and inspect the complete Request URL under Headers. A request to fonts.googleapis.com or fonts.gstatic.com confirms external loading in that test scenario.

If the list is empty, repeat the test in a private window. Browser extensions, cached files and a previously stored consent choice can change the result. Disable the cache in the Network panel while testing if the browser offers that option.

- open the page in a private browser window
- launch developer tools and the Network panel
- preserve the log and disable cache for the test
- reload the complete page
- filter for font, googleapis and gstatic
- inspect the full destination URL

## What can an online Google Fonts checker miss?

An online scanner is useful for an initial indication, but it is not complete evidence. Many checkers load only one URL in one fixed state. Fonts may appear only after a visitor opens a contact form, map, video, appointment module or makes a cookie choice.

Test several page types: homepage, service page, contact page, article and, where relevant, booking journey or shop. Test before choosing anything in the consent banner, after Reject and separately after Accept. External fonts should not start unnoticed before the intended consent step.

Record the URL, date, browser state and a screenshot of the network request. This makes it possible to repeat the same scenario after the correction. A green result on one subpage is not a complete website check.

## How do I identify the source of external Google Fonts?

For the suspicious network request, open the Initiator view. It often shows which CSS file or script triggered the request. The file path may point to a theme, plugin, page builder or embedded provider. Save the path before changing settings.

On WordPress, common sources include theme options, global typography settings, optimisation plugins, form plugins and page builders. Even if the theme loads fonts locally, one widget may still request an external variant. Do not disable plugins randomly on the live site; inspect the specific initiator in a staging environment.

With maps, videos or booking systems, the font may be part of third-party content. Hosting your own site fonts locally will not fix that request. Check whether the service can be held back behind a two-click activation, replaced or configured in a more privacy-conscious way.

## How can I recognise locally hosted Google Fonts?

Locally hosted means that the required WOFF2 or WOFF files are stored on your own domain or controlled hosting and that the CSS rules refer to those files. The Network panel should therefore show the font coming from your domain, not fonts.gstatic.com.

Inspect the CSS file as well. A local font file does not help if the stylesheet is still loaded from fonts.googleapis.com. Conversely, an old Google URL may remain in an unused CSS file without creating an active request. Active network traffic is decisive; source-code inspection adds context.

After a migration, clear website, CDN and optimisation caches and repeat the test in a private window. Check bold, italic and translated pages as they may request additional font weights or character sets.

## What should I do after finding an external request?

First save a screenshot and the initiating file path. The operator or agency should then host the font locally, remove the external CSS reference and refresh all caches. Third-party content may instead require blocking until consent or replacing the service.

Repeat the same Google Fonts check afterwards: same URL, same consent state, plus the main subpages and interactive elements. The technical finding is resolved for these scenarios only when no request to fonts.googleapis.com or fonts.gstatic.com remains. Privacy notices and the consent setup may require separate professional review.

With a managed website subscription, technical maintenance and recurring checks can be organised together. Our plans cost €79, €149 or €299 gross per month. Whatever the service model, verify the result in the browser rather than relying on a changed setting.

## Frequently asked questions about Google Fonts checks

### Are Google Fonts prohibited?

No. The concern is uncontrolled external transfer of personal data. Locally hosted font files avoid a direct font request to Google; obtain legal advice for the specific legal assessment if required.

### Is a free online checker enough?

It is a useful quick test but may miss delayed loading, subpages, embeds and different consent states. Add a manual browser Network check.

### Which domains should I search for?

The common active destinations are fonts.googleapis.com for stylesheets and fonts.gstatic.com for font files. Always inspect the complete request URL.

### Why does a checker find nothing although WordPress mentions Google Fonts?

The font may already be local, exist only in an inactive setting or be blocked by cache and consent rules. The deciding factor is whether the browser makes an external request during the test.

### Do I need to test every page?

Not necessarily every URL, but all important templates and functions. Cover at least the homepage, service pages, contact, articles and any booking or shop flow.

---
Veröffentlicht von bezahlbare-webseite.de — Website im Abo ab 79 €/Monat. https://bezahlbare-webseite.de/