A wordpress ai chatbot not showing on your site is frustrating, especially when you have already connected it, saved the settings, and expected visitors to see a small chat button in the corner of the page. The problem is rarely a single broken feature. In most cases, the chatbot is installed but not fully deployed, blocked by a cache layer, hidden by a display rule, or stopped by a conflict with another plugin or theme. This guide walks through those causes in a sensible order, from the simplest checks to the deeper conflicts, so you can find the fault without changing settings at random.
This guide fixes a wordpress ai chatbot not showing on your site, starting with the quickest checks and moving to the deeper causes.
Confirm Deployment First
The most common reason for a chatbot widget missing wordpress visitors expect to see is that the chatbot was never fully turned on for the live site. Many tools have more than one step between setup and display. You may have created the chatbot, added your business details, and tested it inside a preview window, but the live widget may still be switched off, unpublished, or connected to a different site.
A wordpress ai chatbot not showing is often just an unpublished bot, so confirm the chatbot is live before you touch any settings.
Start inside your chatbot tool or plugin settings. Look for a publish, enable, or go live control. Some tools keep a chatbot in draft mode until you publish it. Others ask you to choose where it should appear, such as all pages, the home page only, or specific pages. If no pages are selected, nothing will appear. Check that the widget is enabled and that at least one page rule includes the page you are testing.
Next, confirm that the chatbot is connected to the correct WordPress site. If you manage more than one site, it is easy to paste a code snippet or connect an account on the wrong one. Check the site address shown in the chatbot tool and compare it with the live site you are viewing. If you use a plugin, confirm that the plugin is activated, not only installed. An installed but inactive plugin does nothing. Also confirm that you have saved the settings after entering any key, ID, or connection detail. Some settings pages need a clear save action, and leaving the page without saving will discard the change.
If your chatbot uses a code snippet, check that it is present on the live page. View the page source in your browser and search for the provider name or part of the script. If the snippet is missing, it may have been added to a staging site or a header area the current theme does not use. Also check the account status, since some tools pause the widget when a trial ends or a connection breaks.
Check Browser and Cache
If deployment looks correct, the next likely cause is the browser or a cache layer showing you an older version of the page. Caching is useful for speed, but it can hide a new chatbot script for hours if the cached page was saved before the chatbot was added. This is one of the most common reasons a site owner sees no chatbot while a fresh visitor does, or the other way around.
If a wordpress ai chatbot not showing affects only you, a hard refresh or a different browser usually reveals a caching problem.
Start with a simple browser test. Open the site in a private or incognito window and check whether the chatbot appears. Then try a different browser. If it appears in one browser but not another, the problem is likely local to the first browser, such as an old cache, a stored cookie, or an extension that blocks scripts. Clear the cache and cookies for the site in the affected browser, then reload the page. Also try a hard refresh, which asks the browser to fetch fresh files instead of using stored copies.
Next, check browser extensions. Ad blockers, privacy tools, and script blockers can hide chat widgets, especially if the chatbot script comes from a third-party domain. Temporarily disable extensions that block trackers or scripts, then reload the page. If the chatbot appears, you have found the cause. You do not need to remove the extension permanently, but you should know that some visitors who use similar tools may also see no chatbot. That is a normal limitation of third-party widgets, and it is worth noting in your support notes so you do not keep chasing a site fault that is actually a visitor-side block.
WordPress AI Chatbot Not Showing? Check Display Rules and Visibility Settings
Display rules decide where, when, and to whom the chatbot appears. They are easy to misconfigure, and they cause many cases where a chatbot works on one page but not another. A chatbot widget missing wordpress on a single page is often a display rule, not a broken plugin.
Open the display or targeting settings and read each rule carefully. Common options include showing the widget on all pages, only on selected pages, or everywhere except selected pages. Check whether the home page, blog posts, or shop pages are included. Also check rules based on visitor type, device, location, or time. A rule that limits the chatbot to desktop visitors will hide it on mobile. A rule that limits it to a certain country or language may hide it for your test location. A rule that shows it only during business hours will hide it in the evening.
Check the trigger setting as well. Some chatbots open automatically after a delay, some show only a small button, and some appear only when a visitor scrolls to a certain point. If the trigger is set to show after 30 seconds, you will not see it in a quick test. Set the trigger to show immediately while you are testing, then restore your preferred delay after you confirm the widget loads. Also check whether the widget is set to start minimised or hidden behind a button. A small circular button in the corner can be easy to miss, especially if its colour blends into your site design.
Display rules are the usual suspect — see how to show a WordPress chatbot on selected pages to understand how targeting works.
Isolate Theme and Plugin Conflicts
A chatbot plugin conflict happens when another plugin or theme changes how scripts load, blocks a script, or replaces part of the page where the chatbot should appear. Conflicts are common on WordPress sites with many plugins, especially when two tools try to load a chat widget, a pop-up, or a script optimisation feature. The goal here is to isolate the conflict safely, not to delete plugins at random.
When a wordpress ai chatbot not showing follows a theme or plugin update, disable the newest change first and test again.
Before you start, make a backup or confirm that your host takes regular backups. Do not test on a live shop during a busy period if you can avoid it. If you have a staging site, test there first. If you do not, choose a quiet time, keep the tests short, and restore each plugin as soon as you have checked it.
The standard isolation test works like this. First, clear the cache and confirm the chatbot is still missing. Then temporarily switch to a default WordPress theme, such as Twenty Twenty-Four or another default theme provided with WordPress. Test the chatbot. If it appears with the default theme, the problem is likely in your current theme. Check the theme settings for script options, footer settings, or a custom code area that may be removing the chatbot code. If the chatbot still does not appear with the default theme, switch back to your normal theme and move on to plugins.
Next, deactivate plugins in small groups, starting with the most likely causes. Likely causes include other chat tools, pop-up tools, caching and optimisation plugins, security plugins, cookie consent tools, and any plugin that changes how JavaScript loads. Deactivate one plugin at a time if you have the time, or deactivate in small groups if the site has many plugins. After each change, clear the cache and test the page in a private window. When the chatbot appears, you have found the conflicting plugin or group. Reactivate the other plugins one by one to narrow it down to a single plugin. Also check for duplicates. If you added both a plugin and a manual snippet for the same chatbot, remove one copy and keep a single install method. Check the browser console for script errors as well. Note any error that names the chatbot domain or a blocked script, since that note helps support staff. Keep API keys private, use the least privilege needed, and rotate a key if you think it was exposed.
Quick Diagnosis Table
| Symptom | Most likely cause | First check |
|---|---|---|
| Shows in preview only | Not published or no page rule | Publish control and page selection |
| Shows in one browser only | Browser cache or blocker | Private window and extension test |
| Shows when logged in only | Cache bypass or role rule | Clear all caches and check role rules |
| Desktop fine, mobile blank | Mobile toggle or overlap | Mobile setting and button position |
| Missing after a new plugin | Plugin or theme conflict | Default theme and plugin isolation |
If a theme conflict is the cause, the WordPress developer documentation explains how themes load scripts and where conflicts come from.
Check Mobile Behaviour
Mobile problems deserve their own check because a chatbot can work perfectly on desktop and still be blank on a phone. The cause may be a device rule, a theme layout, a pop-up covering the button, or a script that is delayed on mobile for performance reasons.
A wordpress ai chatbot not showing on phones but visible on desktop usually means a mobile display rule is hiding the widget.
Test on a real phone if you can, not only in a browser resize window. Open the site in the phone browser, wait a few seconds, and look in both bottom corners. If you use a private browsing mode on the phone, you will avoid cached pages. Also test with Wi-Fi and mobile data if possible, because a network-level block can affect one connection but not the other.
If the widget appears but looks wrong on mobile, our guide to customizing a WordPress chatbot widget covers position and size.
Troubleshooting Checklist
Use this checklist in order. Tick each step only after you have tested it, not just read it.
- Confirm the chatbot is published, enabled, and set to show on the page you are testing.
- Confirm the plugin is active and the connection or key is correct.
- Test in a private window and a second browser.
- Clear the WordPress cache, server cache, and content delivery network cache.
- Disable browser extensions that block scripts, then test again.
- Check display rules for pages, devices, roles, location, and time.
- Check for a cookie consent block and test after accepting cookies.
- Check for overlap with pop-ups, sticky bars, and cookie banners.
- Switch to a default theme briefly and test.
- Deactivate plugins in small groups and test after each change.
- Remove any duplicate chatbot install.
- Check the browser console and note any blocked domain.
- Test on a real phone as well as desktop.
- Restore test changes that did not help.
Work through the list in order when a wordpress ai chatbot not showing has no obvious cause — each step rules out one common culprit.
When to Contact Support
If you have worked through deployment, cache, display rules, and conflicts and the chatbot still does not appear, contact the chatbot provider or the plugin author. Before you write, gather the facts they will need: the WordPress version, the theme name, the plugin name and version, the page address where the chatbot should appear, the steps you already tried, and any console error message. Do not include your API key or password. A clear report gets a faster answer than a short message that only says the chatbot is not showing. If the problem affects a live shop or a support channel customers rely on, add a temporary fallback while you wait. Put a clear contact link, email address, or help page link where visitors can see it, so they can still reach you while the chatbot is down. Tell your support team the chatbot is unavailable so they can watch for extra email or form messages.
If a wordpress ai chatbot not showing survives every check here, contact the plugin’s support team with your WordPress version and theme name.
Before you pay for help, search the WordPress support forums — many chatbot display problems have already been solved there.
Frequently Asked Questions
Why does it show only when logged in?
A wordpress ai chatbot not showing to guests but appearing when you are logged in usually points to a display rule, a cache difference, or a plugin that treats logged-in users differently. Many caching plugins bypass the cache for logged-in users, so you see a fresh page while guests see an older cached page without the chatbot. Clear all cache layers and test in a private window while logged out.
Another common cause is a role or visibility rule in the chatbot settings. Check whether the widget is set to show only to logged-in users or to certain roles. Change it to show to all visitors while testing. Also check whether a security or membership plugin hides the chatbot for guests. For most support chatbots, guests should be able to see the widget, because they may need help before they create an account or log in.
What if mobile is blank?
If the chatbot works on desktop but the phone screen is blank, start with the mobile display setting in the chatbot tool. Check whether mobile is switched off, or whether a separate mobile position or trigger is set. Turn mobile display on, set the trigger to show immediately for testing, and reload the page on a real phone.
Next, check for overlap. A cookie banner, sticky footer, mobile menu, or pop-up can cover the bottom corners on a small screen. Close those elements and look again. Try moving the chatbot button to the opposite corner. If it appears after moving, the problem was overlap.
Conclusion
A missing WordPress AI chatbot is usually a deployment step, a stale cache, a display rule, or a conflict, not a sign that the chatbot itself is broken. Work through the checks in order, test as a logged-out visitor in a private window, and change one setting at a time. Keep a short log, restore test changes that did not help, and add a simple contact fallback while you troubleshoot. If the problem remains after the full checklist, contact the provider with your test notes and any console error. That clear record will help you get a fix faster, and it will make the same problem easier to solve if it appears again.
For a related setup walkthrough, see Add an AI Chatbot to WordPress and How to Build a No-Code AI Customer Support Agent.