Verify Your FoxChat Installation

The Verify Installation button is the fastest way to confirm your install actually works — it does what you would do manually, just headlessly and with a structured report at the end.

You will find the button on the Install tab of your FoxChat dashboard. Click it and enter the URL of any page on your site that should have FoxChat installed. The check runs in about ten seconds and tells you exactly which assertions passed and which failed.

What the check does

Verify Installation runs a headless browser session against the URL you enter. The session goes through these steps:

1. Fetch the page. The browser loads the URL with a normal desktop user agent. We log the HTTP status code (must be 200).
2. Parse the HTML. We look for a <script> tag whose src attribute is https://getfoxchat.com/widget.js or one of the versioned widget URLs. We also look for a window.foxchatConfig declaration with a non-empty siteId.
3. Wait for the widget to load. The browser executes JavaScript and waits up to 8 seconds for the widget to render. We then look for the FoxChat host element on the page (a custom element named foxchat-shadow-host).
4. Confirm the site ID matches an account. The site ID embedded in the page must match a site that exists in your FoxChat account. (This catches typos and stale snippets from old accounts.)
5. Open the widget once. The check programmatically clicks the bubble to confirm the panel opens and renders content. We log the panel's announced state.
6. Send a test message. Optionally, the check sends a test message and confirms a response comes back from the FoxChat backend.

The report at the end lists each step with a green checkmark or a red x, and for failed steps, a specific actionable next step.

Common verification errors and what they mean

"No FoxChat script tag found"

The HTML you served at the URL we tested did not contain a script tag pointing to getfoxchat.com/widget.js. Causes:

• You haven't deployed the snippet yet, or you deployed it to a different page.
• You deployed the snippet, but a CDN cache layer is still serving the old HTML. Purge the cache.
• You're testing a URL that's behind authentication; the headless check can't sign in. Test with a public URL instead.

"Site ID is missing or empty"

The script tag is on the page, but window.foxchatConfig.siteId is empty or set to the placeholder string YOUR_SITE_ID. Replace the placeholder with the real UUID from your dashboard. The dashboard's install page has a one-click copy button that pre-fills your real ID.

"Site ID does not match any FoxChat account"

The site ID in the snippet is well-formed but doesn't correspond to any site in your FoxChat account. Causes:

• You signed up for a fresh account but pasted the snippet from an older account's dashboard.
• You deleted the site from the dashboard but the snippet on the page still references its UUID.
• Typo — one character off.

Fix: copy the snippet again from the dashboard of the account you actually intend to use.

"Widget script returned 4xx or 5xx"

The browser tried to load widget.js but received an error response. This is rarely on our side — the widget URL has been stable since launch — but the cause is usually:

• An ad-blocker or filter on the headless test runner. Re-run the check; we use multiple test runners and the second usually succeeds.
• A regional CDN edge being slow. Wait 30 seconds and re-run.
• You're behind a corporate proxy that blocks the FoxChat domain. The check is running from outside your network so this only matters if your real visitors are in the same network restriction.

"Content-Security-Policy blocks the widget"

Your site sends a CSP header whose script-src directive does not include https://getfoxchat.com. The widget's script tag refused to load. Fix: add https://getfoxchat.com to your script-src and https://*.getfoxchat.com https://*.supabase.co to your connect-src. See script tag install for the full directives.

"Widget loaded but did not render"

The script loaded successfully but the FoxChat custom element did not appear in the DOM after 8 seconds. Causes:

• JavaScript error elsewhere on your page caused the page's main script to crash before the widget initialized. Open browser dev tools, reload, and look at the Console tab.
• The widget config's hideOnPages setting matched the URL you tested. Test a URL not in the hide list.

When all checks pass

The dashboard shows a single green banner: Installation verified. You can stop worrying about the widget and move on to setting up your knowledge base, recording walkthroughs, or configuring proactive triggers.