Category

Troubleshooting Guide: Fix Live Chat Widget Loading Issues

Updated:

If your live chat widget isn’t loading properly, the issue might be related to your website’s Referrer Policy, especially when the Trusted Domains setting is enabled. This guide explains what the Referrer Policy is, how to check it, and how to update it to ensure your widget functions correctly.

Why the Widget Might Fail to Load

When Trusted Domains is enabled for your live chat widget, the widget uses the Referrer header to verify that it’s being accessed from an allowed domain. If your website’s Referrer Policy restricts or hides this information, the widget won’t be able to validate the source — causing it to fail loading.

If Trusted Domains is disabled, this check is skipped, and the widget can load on any domain. In that case, no changes to the Referrer Policy are necessary.

What is the Referrer Policy?

The Referrer Policy is a browser security feature that controls how much information is sent in the Referer header during navigation. This header usually contains the URL of the page that made the request.

Different policies can:

  • Send the full URL
  • Send only the domain (origin)
  • Send nothing at all

An overly strict policy can prevent the live chat widget from knowing which domain is loading it — leading to validation failure if Trusted Domains is enabled.

How to Check If Trusted Domains is Enabled

  1. Go to Admin > Chat > Live Chat in your BoldDesk dashboard.
  2. On the live chat widget used on your website, click on the more option and choose the edit option.

    Live Chat Widget.png

  3. Scroll to the Preference tab and locate Trusted Domains under Security section.

    Trusted Domains.png

  4. Make sure:
    • It’s enabled
    • Your website’s domain is listed

If it’s disabled, you don’t need to change the Referrer Policy.

How to Check Your Website’s Referrer Policy

  1. Open your website in a browser.
  2. Launch Developer Tools:
    • Windows/Linux: Ctrl + Shift + I or F12
    • Mac: Cmd + Option + I
  3. Open the Network tab.
  4. Refresh the page and search for chatwidget.
  5. Click the chat widget ID in the Name column.
  6. Under Headers > General, check the Referrer Policy value.

Common Referrer Policy Types

Policy Behavior
no-referrer Sends no referrer data
no-referrer-when-downgrade Sends full URL on secure connections (HTTPS ➜ HTTPS)
origin Sends only the domain
origin-when-cross-origin Sends full URL for same-site; domain only for cross-site
same-origin Sends full URL only for same-site requests
strict-origin Sends only the domain, blocks downgrade (HTTPS ➜ HTTP)
strict-origin-when-cross-origin Best balance: full URL on same-site, domain only on cross-site
unsafe-url Sends full URL always — not recommended for privacy reasons

Recommended Referrer Policy Settings

To ensure compatibility while maintaining security, use one of the following:

<meta name="referrer" content="strict-origin-when-cross-origin">

or 

<meta name="referrer" content="no-referrer-when-downgrade">

These settings allow enough referrer data for widget validation when Trusted Domains is enabled.

How to Update the Referrer Policy

  1. In your website’s HTML, find the <head> section.
  2. Add or update the following meta tag:
<meta name="referrer" content="strict-origin-when-cross-origin">
  1. Save and publish your website.

Once applied, the widget should start loading correctly.

Frequently Asked Questions (FAQs)

Q1: Why does my widget load on some pages but not others?
Some pages may override global Referrer Policy settings with page‑specific <meta> tags.

Q2: Do I need Trusted Domains for security?
Trusted Domains prevent unauthorized embedding and are recommended for preventing misuse.

Q3: Can I add wildcard domains?
Yes. BoldDesk supports patterns like *.example.com.

Q4: Will this affect SEO or analytics tools?
Standard recommended policies (strict-origin-when-cross-origin) generally do not affect SEO or analytics.

Related Article

  1. Troubleshooting Guide: Overcoming CSP Restrictions Affecting Live Chat Widget
  2. Troubleshooting: Error 429 (Too Many Requests) Guide
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied
Access denied
Access denied

No articles or sections found
No articles or sections found