After installing Yaplet, spend two minutes confirming it's working before you send it to production. This article walks through a quick browser check and covers the most common reasons the widget doesn't appear.
Quick visual check
Open the page where you installed Yaplet. Look for the launcher button in the bottom-right corner. Click it — the widget should open and show the home screen, inbox, or help center, depending on how your widget is configured.
If you see the launcher and the widget opens, installation is complete. Skip to Identify your logged-in users as the next step.
Dev tools check
If the launcher doesn't appear, open your browser's developer tools (press F12 or right-click → Inspect) and check each of the following:
Network tab — confirm the script loaded
- Go to the Network tab.
- Reload the page.
- Filter by the search term
yaplet. - You should see a request to
yaplet.com/api/sdk/loaderwith a status of 200 or 302. If the request is missing entirely, the snippet was not added to the page.
Console tab — check for errors
Switch to the Console tab and look for any red error messages mentioning yaplet, embed.yaplet.com, or Content Security Policy. Common errors and their fixes are listed below.
Elements tab — confirm the snippet is in the page
Press Ctrl+F (or Cmd+F on Mac) in the Elements panel and search for Yaplet.initialize. If nothing is found, the snippet was not injected into the page HTML.
Common problems and fixes
The loader request returns 404
Your Widget ID is invalid or the widget has been deleted. In your Yaplet dashboard, click Widgets in the sidebar, click your widget, and confirm the ID shown at the top matches the one in your snippet.
No network request to yaplet.com at all
The snippet is not on the page. Go back to your platform's installation guide and verify the script was saved correctly:
Content Security Policy (CSP) error
Your site's CSP is blocking the Yaplet scripts. Add the following domains to your CSP's script-src and frame-src directives:
script-src 'self' https://yaplet.com https://sdk.yaplet.com;
frame-src 'self' https://embed.yaplet.com;Widget loads but shows a blank or broken screen
This usually means a network request to the widget frame is being blocked. Check the Network tab for failed requests to embed.yaplet.com and confirm those domains are reachable from the user's browser.
Widget appears in development but not in production
Some deployment pipelines strip custom scripts or enforce stricter CSP in production. Check your CDN, reverse proxy, or meta-tag CSP headers in the production environment.
Launcher is hidden
If the widget loaded successfully but the launcher isn't visible, it may have been hidden programmatically. Check if Yaplet.hide() is being called anywhere in your code. You can show it again with Yaplet.showFeedbackButton(true) (pass true to show, false to hide).
Still not working?
If none of the above resolves the issue, start a conversation with the Yaplet support team directly from the widget on this page. Include the URL where the widget should appear and any console errors you see.