This guide shows how to add an ai chat widget for WordPress in about a minute, with no plugin: you paste one snippet into a footer widget area, because it's a floating bubble, so it only needs to exist once per page and should load last. No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.
The AI chat widget adds a small chat bubble that answers visitors' questions using the content of the page they're on. It's useful for long pages such as pricing, FAQs, documentation or product details, where visitors would otherwise scroll around looking for one answer. It's powered by a large language model and grounded in your page text, so it works best on pages that actually contain the answers.
On WordPress, the right spot is a footer widget area. It's a floating bubble, so it only needs to load once per page, at the end of the body. Try it on your longest page first and ask it the questions your customers usually email you about. If the answers are thin, the page probably is too.
WordPress.org sites you host yourself can use every method on this page. On WordPress.com, adding scripts with a Custom HTML block or a header plugin needs a plan that allows plugins and custom code (the Business plan or above at the time of writing), because lower WordPress.com plans strip script tags. If you're not sure which you have, check whether your dashboard has a Plugins menu.
WP Rocket, W3 Total Cache, LiteSpeed Cache and your host's edge cache all serve a stored copy of your HTML. Until you purge, you'll be looking at the version from before you pasted and assuming the widget is broken. The widget's own data is fetched client-side on every load, so page caching never makes the numbers go stale — it only hides a freshly-added snippet.
Optimisation plugins that concatenate or defer every script can break an async third-party tag by moving it out of order. If the widget renders nothing after a purge, add the script URL to your plugin's JS exclusion list — in WP Rocket that's File Optimization → Excluded JavaScript Files. Nothing else needs changing.
WordPress sanitises script tags typed into a paragraph or the Visual editor tab, silently. The Custom HTML block, the Classic editor's Text tab, and Elementor's HTML widget all pass markup through untouched. If your snippet vanished on save, that's why.
Like any AI assistant it can get things wrong, especially on short pages or questions the page doesn't cover. Don't use it for anything where a wrong answer could cause harm, such as medical, legal or safety advice.
No plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs. Installing a plugin for this would mean another dependency and update cycle just to show one widget.
A footer widget area, because it's a floating bubble, so it only needs to exist once per page and should load last.
It adds one small script, loaded asynchronously, so it doesn't block your page from rendering. Any third-party script has some cost, so check your page speed before and after adding it. Your caching and optimisation plugins keep working exactly as before — the only thing to remember is to purge the cache after you paste, otherwise you'll be looking at the stored copy of your old HTML.
Elementor: drag in the HTML widget and paste there. Divi: use a Code module. Beaver Builder: use the HTML module. WPBakery: use the Raw HTML element. Any builder with a raw-HTML or code block will render it.
It can. It's grounded in your page content, which reduces this, but it isn't guaranteed. Test it with real questions and keep important details, such as prices and policies, clearly written on the page.