This guide shows how to add an ai chat widget for Ghost in about a minute, with no integration: you paste one snippet into Settings → Code injection → Site Footer, because it's a floating bubble, so it only needs to exist once per page and should load last. No integration to configure. Ghost renders raw HTML and script tags from Code injection and from an HTML card, so there is nothing to install and no third party in the loop.
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 Ghost, the right spot is Settings → Code injection → Site Footer. 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.
Code injection is available on every Ghost(Pro) plan and on self-hosted Ghost, both sitewide (Settings → Code injection) and per post. HTML cards are available in the editor on all plans too. The main limit is on Ghost(Pro)'s entry plan, which doesn't allow custom themes, so use code injection or HTML cards rather than editing theme files.
Ghost's whole appeal is speed. Putting a script in Site Header makes the browser deal with it before painting your post; Site Footer runs it after. Our snippet is async either way, so use the Footer box unless the widget must exist before first paint (the heatmap and the speed badge are the only two that benefit).
An HTML card displays the raw code while you're writing and only renders on the published page. That's by design, not a failed paste. Publish (or use the preview link) and check the live URL — and remember post-level code injection doesn't run in preview at all on some versions.
If you paste the snippet into a `.hbs` file, the next theme update or theme switch silently removes it. Code injection is stored in your Ghost settings, not in the theme, so it survives both. On Ghost(Pro) you can't edit theme files directly anyway — Code injection and HTML cards are the whole surface.
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 integration to configure. Ghost renders raw HTML and script tags from Code injection and from an HTML card, so there is nothing to install and no third party in the loop. Installing an integration for this would mean another dependency and update cycle just to show one widget.
Settings → Code injection → Site Footer, 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. Ghost is already the fastest mainstream publishing platform and the point is to keep it that way: the snippet is one async tag, so it never blocks your post from rendering. Site Footer is the right injection slot for script tags — Site Header is for things that must run before paint.
Ghost admin: Settings → Code injection → Site Footer. Ghost editor: insert an HTML card. Post settings: per-post Code injection fields. Self-hosted themes: edit default.hbs above {{ghost_head}}. 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.