> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/troubleshooting/widget-not-showing.md).

# The widget is not showing

Work through this in order.

Work through these in order — they are arranged by how often they are the cause.

## 1. Test in a private window

Open your site in a private/incognito window.

A normal window may serve a cached page, or remember that you dismissed the widget earlier. This alone resolves a large share of reports.

## 2. Wait a few seconds

The widget loads after your page content, deliberately, so it does not delay your page. Give it two or three seconds.

## 3. Confirm the snippet is on the page

View the page source and search for `limecall`.

**Not there** — the snippet is not installed on this page. This is the most common cause: it was added to the homepage only, rather than to a shared template. See [Install with JavaScript](/callback/install-with-javascript.md).

**There** — continue.

## 4. Clear every cache

Caching is the second most common cause. Purge all of them:

* your caching plugin (WP Rocket, W3 Total Cache, LiteSpeed, WP Super Cache),
* your host's server-side cache,
* Cloudflare or any other CDN.

Then retest in a private window.

## 5. Check display rules

Open **Widget → Display rules**. A rule may be excluding this page.

Remember rules are evaluated in order and the first match wins — an early broad rule can override a later specific one. Also check the device rules, if you are testing on mobile. See [Display rules](/callback/display-rules.md).

## 6. Check business hours

If the widget is configured to hide outside business hours, it will be absent when you are closed.

Check the time zone on your business hours — hours set in the wrong zone are a frequent cause of a widget missing during the actual working day. See [Hours](/callback/hours.md).

## 7. Open the browser console

Press F12 and look at the Console tab.

**`Content Security Policy` errors** — your CSP is blocking the script. Allow the widget origins; see [Install with JavaScript](/callback/install-with-javascript.md).

**`404` on the widget script** — the snippet is malformed. Recopy it from **Widget → Embed**.

**`Blocked by client`** — an ad blocker or privacy extension is blocking it. Test with extensions disabled. Some visitors will block it too; that is unavoidable.

**No errors at all** — the script is probably not on the page. Return to step 3.

## 8. Check optimisation plugins

Plugins that combine, defer or minify JavaScript frequently break third-party widgets. Add `limecall` to the exclusion list. See [Install on WordPress](/callback/install-on-wordpress.md).

## 9. If you used Google Tag Manager

Confirm you clicked **Submit** and **Publish**. Changes visible in GTM Preview are not live until published — a very common oversight. See [Install with Google Tag Manager](/callback/install-with-google-tag-manager.md).

## Still nothing

Contact support with the page URL, the browser and device, a screenshot of the console, and confirmation of the steps above.