Installation, identity and privacy

Why is a chat widget not showing on your website?

When a chat widget is missing, check whether the embed script loaded, whether it uses the correct site key, and whether the current origin is allowed. Then inspect browser console and network errors, privacy extensions, and layout conflicts. Test on the actual published page rather than assuming a preview behaves identically.

Is the script present and loading?

Inspect the page source or browser network panel for the widget script. Confirm that the site builder published the code to the intended pages. If a request is blocked or returns an error, diagnose that response before repeatedly pasting the same snippet into additional locations.

Does the configuration match this website?

Compare the site key and the full origin, including scheme and any port used for local testing. Production, staging, and preview hostnames are different origins. A configuration that intentionally allows one does not establish that another should work.

Could the browser or layout hide the interface?

Compare a normal session with a clean browser profile to identify extension-related blocking. Check whether another fixed-position control covers the launcher, especially on mobile. If a security policy blocks a connection, adjust only the necessary documented permission rather than disabling the entire policy.

Practical checklist

  • Verify the published page includes one embed.
  • Check script and connection responses in the network panel.
  • Match the site key and allowed origin.
  • Test mobile layout and a clean browser profile.

Worked example

The widget loads on localhost but disappears on a staging subdomain. The script and key are unchanged; the allowed-origin list includes localhost and production but not staging. Add the intended staging origin and retest the full conversation.

How Fire Away fits

Fire Away’s install guide covers the current embed and allowed-origin configuration. The widget uses a shadow root, but surrounding page overlays and browser policies can still affect whether a visitor can reach it.

Troubleshoot installation →