Configure the primary website and allowed widget domains, then diagnose a missing or blocked widget.

What you’ll accomplish

Set the project’s canonical website, confirm authority, and list every hostname where visitors can load the widget.

Enter the website and domains in the right formUse bare domains and list every unrelated host explicitly.
Enter your-company.example, not a protocol, www. prefix, or path. The dashboard can normalize a full URL, but validation asks for a bare domain. An allowed domain covers that exact host and subdomains—your-company.example covers shop.your-company.example, not unrelated hosts. Use wildcards only when your security requirements explicitly call for them.
Clear all readiness checksThe project needs a website, authority confirmation, and at least one allowed domain.
Use the settings link in the readiness panel for any incomplete item.
Validate where visitors actually load itA dashboard indicator is helpful, but the published page is the final proof.
Load the actual published page on an allowed host and send a test message. Do not rely on Verify installation alone.

Diagnose common issues

Symptom	Check	Resolution
Widget does not render	The exact generated snippet is on the published page	Restore the complete snippet and place it at the platform-specific location.
Widget renders on a preview but not production	The visitor host is allowed	Add the production host to allowed domains and publish the site.
Installation view shows warnings	Primary website, authority confirmation, and allowed domains	Complete all three in project settings.
Answers are weak after successful install	Knowledge source status and assistant selection	Wait for processing, assign the correct source, and retest.
Appearance is unexpected	Saved assistant widget settings	Save the intended mode and branding, then refresh the live page.

Last updated on

Authorize domains and troubleshoot installation