Documentation
The widget doesn't show
Find out why the allyWay button doesn't show on your website – account, settings, code, address, cache or a blocked script – and bring it back.
Updated October 28, 2026
When the allyWay button doesn't appear, nothing on your website breaks – the widget just isn't there. Most often it's a cache or the wrong code. If it worked before, something changed – for example a theme update removed the code, or a new plugin blocks it.
Start in a private window
Open your website in a private (incognito) window and look in your chosen corner – bottom right by default. A private window skips old caches, your own saved widget settings and most browser extensions.
- The button shows there: it's hidden only in your normal browser, for example with Hide toolbar (for this visit, 24 hours or one week). Clearing your website's stored browser data brings it back.
- Ad blockers and privacy extensions can block the widget for that one visitor – also by blocking a tag manager that adds it.
allyWay is off for your account
allyWay works only with an active plan or a running free trial, and only for websites that are part of your plan. Log in to the dashboard: a dialog says what's wrong, for example "Your trial has ended" or "Your payment failed" – see Why your account is locked. Paused on Websites means the website isn't part of your plan – see Paused websites. Once it's fixed, the widget is back on the next page load.
A setting hides the button
The dashboard has no on/off switch for the widget, but two settings hide its button:
- Modules: with every module off, there's no button. Switch on at least one module.
- Design › Widget position: Hide on Desktop, Hide on Tablet and Hide on Mobile each hide the button on that kind of device.
allyWay's AI fixes keep working in both cases.
The code isn't on the page
Right-click the page, choose View page source, press Ctrl+F (Cmd+F on a Mac) and search for "loader.js". Not there? The change isn't published yet, or a cache serves the old page. Code added with a tag manager doesn't show here – that's fine.
- Only on some pages: the code is on one page or in a template only some pages use. Move it to your site-wide footer or main template. Landing, checkout or error pages may need it too.
- The code shows as text: it went into a normal text field. Paste it into a field for HTML or code instead – see Install allyWay.
Wrong code or wrong address
- Wrong code: every website has its own code. Select the website in the website switcher, open Installation and compare its ID with the one in your page's code. Different? Click Copy, replace the code, publish and clear your cache. A website you removed and added again has a new code.
- Wrong address: the widget appears only on the address you added (with or without www) and its subdomains – not on other domains, a builder's own or preview address (like "myshopify.com" or "webflow.io"), or
localhost. See Websites, domains and subdomains. - Missing with or without www: that version serves different pages – an older cached copy, another server or a redirect. Clear all caches, and ideally let one version redirect to the other.
A cache serves the old page
Clear your caching plugin (for example Clear cache in WP Rocket or Purge All in LiteSpeed Cache), your hosting's cache and your CDN – in Cloudflare, Caching › Configuration › Purge Everything. Then reload in a private window.
Something holds the script back
- Delay or combine JavaScript: delayed, the widget appears only after a visitor scrolls, clicks or types – too late for many people who need it. Combined, it can stop working. Add
allywayto your optimization plugin's exclusions for "Delay JavaScript" (and "Combine" or "Minify"). - Cloudflare Rocket Loader: turn it off, or add
data-cfasync="false"to the allyWay script tag, beforesrc. - Cookie banner: see Cookie banners and consent tools.
- Content-Security-Policy: it must allow allyWay's addresses – see Your visitors' privacy.
Let your developer look
In the browser's developer tools (F12), the Network tab shows whether loader.js, widget.js and the settings file config.json loaded. If config.json answers "enabled": false, its "reason" says why:
| Reason | What it means |
|---|---|
subscription_expired |
No running trial or active plan. |
website_deactivated |
The website is paused. |
domain_mismatch |
The page isn't on the website's address or a subdomain. |
domain_inactive |
Switched off on our side – contact support. |
| "not found" (404) | Unknown website ID. Copy the current code from Installation. |
In the Console, "Refused to load the script" means a Content-Security-Policy blocks allyWay. To send your developer the code and guide, see Send the installation code to your developer.
Check that it works
Open your website in a private window and look for the button in its corner. Still missing? Get help from our team.
A tool is missing from the menu. Why?
Usually it's switched off in Modules. Big cursor and Text magnifier are also hidden on touch-only phones and tablets. See Choose which tools the widget offers.
Why doesn't Ctrl + . open the menu?
Keyboard shortcuts are off by default for new websites. Turn on Enable keyboard shortcuts in Modules and click Save changes. On a Mac, use ⌘ + . instead.