If the widget doesn't show up after you install it, it's almost always one of three things: the snippet isn't on the live page, the page is cached, or a Content Security Policy is blocking the script.
Confirm the snippet is live
Open your published site, view the page source, and search for accessibird. If it's not there, the change either wasn't saved or wasn't deployed. Republish from your CMS, or push your code change again.
Bypass the cache
Browsers and CDNs cache HTML and scripts aggressively. Hard-refresh with Ctrl+Shift+R (or Cmd+Shift+R on Mac), and if you use a CDN like Cloudflare, purge the cache for the page.
Check Content Security Policy
If your site sends a strict Content-Security-Policy header, you may need to allow accessibird.com in script-src and connect-src. Open the browser console; a blocked script is reported clearly, and the fix is to extend the policy.
Verify with the test page
The widget test page in your dashboard loads the widget in a clean environment. If it works there but not on your site, the issue is on the site, not with Accessibird.
Load it from your own website
The widget's requests must come straight from your own website. Localhost and preview addresses don't count towards the "active" or "verified" status, so check on your live site.