Troubleshooting – Fonts not appearing on frontend

Google Fonts or Custom Fonts (for Pro users) may not display correctly on the frontend of your website, even though they appear as expected in the Elementor Editor.

Possible causes

This issue generally stems from two common problems, which can occur independently or together:

• CORS policy violations – When the browser blocks a request to load fonts from a different origin (see MDN – CORS).
• Mixed content – When a secure HTTPS page tries to load resources (like fonts) over an insecure HTTP connection (see MDN – Mixed Content).

Below are the most common scenarios that lead to these issues:

After Migrating Your Website (CORS)

When migrating from a local or staging site, your WordPress and Site URLs usually change. However, Elementor may still reference old URLs for your fonts in its generated CSS files via the @font-face rule. If these font URLs point to your previous domain, the browser will block them due to CORS policy restrictions.

After Installing an SSL Certificate (Mixed Content)

If your site was originally set up without HTTPS, Elementor may have saved font URLs using the insecure http:// protocol. After installing an SSL certificate, your site loads via https://, but those older http:// links remain in place. This causes mixed content issues, and modern browsers will block those insecure font files.

After Changing Your Site URL (CORS)

Changing your domain, adding a subdomain or subdirectory, or switching from HTTP to HTTPS can all result in outdated font URLs being stored in Elementor’s CSS files. These outdated references may be blocked due to CORS violations.

WordPress Settings Still Use HTTP (Mixed Content)

If your Site Address (URL) and WordPress Address (URL) in the WordPress Settings page still use http://, Elementor will also use that protocol when generating font URLs. This creates mixed content errors once the site is accessed via HTTPS.

Logged In via HTTP (Mixed Content)

If you access the WordPress Admin Dashboard via http://, WordPress returns the unsecure protocol for all internal URLs during your session. Elementor will store those insecure URLs in its CSS files, even if your site is actually served over https://.

Solutions

1. Always log in using a secure connection.
   
   Note

   If your site uses the HTTP protocol, go to step 3.
   
   
   Make sure that when you’re accessing WP Admin using https:// and not http://. If possible, ask your hosting provider to redirect all http:// requests to https://.
2. Update Your Site URL to Use HTTPS.
   • From WP Admin, navigate to Settings>General.
     
     The general settings appear in the right pane.
     
   • Verify that both the WordPress Address (URL) and Site Address (URL) begin with https://.
     
   • If they do not begin with https://, edit them and click Save Changes at the bottom of the screen.
3. Use the Replace URL tool and then regenerate the CSS and data. For details, see Use the Replace tool.
4. (Optional) Reset the Google fonts load.
   
   Note

   This step is optional but can help signal cache layers to regenerate updated font references.
   
   Elementor includes a setting that allows you to define the font-display property for Google Fonts. Changing and resetting this option can sometimes help trigger automatic cache clearing, especially when using optimization or CDN tools.
   To reset the Google fonts load:
   • Go to WP Admin.
     
   • Navigate to Elementor>Settings.
     
   • Click the Advanced tab.
     
   • Locate the Google Fonts Load option and use the dropdown menu to change its value.
     
   • Click Save Changes.
   • After the page reloads, change the setting back to its original value.
   • Click Save Changes.
5. Clear the relevant caches.
   To see the updated fonts, you should clear various types of caches.
   To clear these caches:
   • Server cache: This is usually managed via your hosting control panel. Contact your hosting company for details about clearing the server cache.
   • Site cache – This is often handled by caching plugins.
   • CDN cache – Clear through your site, directly on CDN or using the hosting panel.
   • Browser cache – Clear after all other caches have been purged. For details, see your browser’s documentation.