Skip to content

Troubleshooting

Check each of these in order:

  1. Is window.pageclerkConfig.chatbotId set? Open the browser console. If you see PageClerk: pageclerkConfig object or chatbotId not defined, the config object is missing or misspelled, or it loads after widget.js.

  2. Does the config come before the script? The inline window.pageclerkConfig block must appear before <script src="https://pageclerk.com/api/widget.js" defer></script>.

  3. Is your domain allowed? If domain security is enabled, add your site’s domain under Allowed domains. An unlisted domain blocks the widget from loading.

  4. Is a script blocker interfering? Ad and privacy blockers occasionally block third-party scripts. Test in a private window with extensions disabled.

  5. Did you publish? On Webflow and similar hosts, changes to Custom Code only go live after you publish the site.

Appearance is fetched by the widget on load. Reload the page (hard refresh to bypass cache). If it still looks stale, confirm you saved the change in the dashboard’s Appearance tab.

Open the Training status view for your chatbot. Sources that failed to process are listed individually — common causes are pages behind a login, blocked crawlers, or unsupported file types. Remove or replace the failing source and retrain.

Email support@pageclerk.com with your chatbot ID, the page URL where you embedded the widget, and any console errors.