What the check does
When you click Verify installation, Accessora:
- Opens the address saved for this site in a headless browser.
- Waits until the page stops loading, for up to 30 seconds.
- Looks for a script whose file name contains
autoloadand reads itsdomainId. - Compares that ID with this site’s ID.
When both the script and the ID are right, all three rows on the Installation page turn green and the site shows as installed.
You can run the check again two minutes after the last one.
What each message means
| Message | What happened | What to do |
|---|---|---|
| Widget installation verified. | The script is on the page with this site’s domain ID. | Nothing. Open your site and look for the launcher. |
| Accessora widget not detected on the page. | No script with autoload in its address was found. | Check the tag is on the page and published. Purge any page cache. |
| Widget found but configured with a different domain ID. | The script is there, but its domainId belongs to another site. | Copy the tag again from this site’s Installation page. |
| Verification could not complete, followed by the error | The page did not load in 30 seconds, or the browser hit an error. | Make sure the address is public. Password pages, bot challenges and very slow pages all stop the check. |
| Verification timed out. Try again. | The check took longer than the dashboard waits for an answer. | Try again in two minutes. If it keeps happening, the page is probably too slow to load. |
Check it yourself
You don’t need the dashboard to see whether the widget is live. Open your site, then your browser’s developer tools.
Elements. Search the page for autoload.js. You should find your tag and the widget’s own elements: <accessora-skip-links> at the very start of <body>, and <accessora-toggle> and <accessora-widget> near the end.
Network. Reload and filter for accessora. A working install makes these requests, all with status 200:
cdn.accessora.io/embeds/js/latest/autoload.js?domainId=…
cdn.accessora.io/embeds/js/latest/accessora.browser.js
dash.accessora.io/api/widget-config?domainId=…
dash.accessora.io/api/analytics?domainId=…A 404 on widget-config means the domain ID doesn’t match any site, often because the site was deleted or the ID was mistyped. A request that never leaves the browser points to a blocker or a Content Security Policy. See troubleshooting.
Console. The widget logs problems with an Accessora: prefix, such as Accessora: Missing domainId parameter in script tag.
Settings reach your site within about a minute. Reload the page to see them.