Skip to content
Troubleshooting

Flidu Widget Is Not Appearing On My Website

You installed the script, but the launcher is not showing on your site — or it shows for you and not for visitors. This is a common installation issue — the checks below cover several frequent causes.

Applies to Website Widgets and AI Chatbot
Quick Checks First
0 of 4 checked

Tick these off as you go — they cover the frequent causes first.

Step-By-Step Troubleshooting

Work top to bottom — each step ends with what you should see before moving on.

Confirm The Widget Is Published

In the dashboard, open the website and check the widget’s status. A Draft widget never renders, and neither does any widget on a website whose Site Status is switched off — no matter how correct the script is.

Expected result: the widget shows Published and the website shows Active in the dashboard.

Confirm The Script Is On The Live Site

Open your live website (not a preview or draft), view the page source, and search for /widget.js. Also confirm the data-widget key matches the widget you expect — a snippet copied from a different widget is a frequent cause. When in doubt, re-copy the exact snippet from that widget’s Install tab. A snippet from first-time setup uses data-site instead and loads the website’s default widget. If it is missing, the script was added to a draft, a different environment, or a page the site does not actually serve.

Expected result: the script tag appears once in the page source, near the closing body tag.

Hard-Refresh And Rule Out Caching

Cached pages and site-optimization plugins can serve an old copy of your page without the script. Hard-refresh, and if your platform has a cache, clear it and republish.

Expected result: the freshly loaded page contains the script and the launcher appears.

Check Targeting And Visibility Rules

Targeting decides which pages, devices, countries, dates, and hours show the widget. If a published rule excludes the page you are viewing — or a Days & Hours or date schedule is outside its set times — a Contact-only widget correctly stays hidden. A widget that also carries Ask AI still shows its launcher and opens Ask AI.

Before you change rules: saved targeting changes stay as drafts until you publish them, and published rules apply to visitors from their next page load. Review the rules first and change only what you can explain.
Expected result: the page you are testing is inside the widget’s rules, and the launcher shows there.

Rule Out Blockers And Script Conflicts

Content blockers in your own browser can hide widgets while visitors see them fine — test in a private window with extensions off. Aggressive script-optimization settings on some platforms can also defer or exclude third-party scripts; if yours does, exempt the Flidu script.

Expected result: the launcher appears in a clean private window on desktop and mobile.

Common Causes At A Glance

Widget saved as draftPublish the widget — drafts never render on the site.
Script on the wrong environmentAdded to staging or a draft theme — add it to the live site and republish.
Cached page without the scriptClear platform cache and hard-refresh.
Targeting excludes the pageThe page, device, country, date, or hours fall outside the widget’s rules.
Wrong widget keyThe snippet belongs to a different widget — re-copy it from the intended widget’s Install tab.
Inactive website entryThe website is inactive in your workspace — check its status with your workspace Owner or Admin.
Plan or usage statePast your plan’s monthly visitor allowance, premium channels can show as temporarily unavailable while the launcher and core channels keep working — check Website Widgets usage in Billing.
Your own content blockerTest in a private window — visitors likely see the widget already.
Still Not Working?

Send the team three things: your workspace name, the website URL, and which of the five steps above you already tried.

Flidu

Accounts are not open yet

You can't create an account or sign in to Flidu yet. If you have a question, the Contact page reaches us.