Add an AI Chatbot to Your Ghost Site

What connecting Ghost gets you

A publication gets a narrower set of questions than a shop, and they arrive at worse hours. What's included in the paid tier. Whether a post is behind the paywall or just hasn't sent yet. Whether the newsletter goes out weekly. How to cancel. These are answered somewhere in your archive or your FAQ page, and a reader still emails you, because finding the answer is more work than asking.

Connect Evoriqa and an AI agent answers those from what you've already published, on every post and page, at the hour the reader is actually reading. It's one snippet in Code Injection, so nothing about your theme changes and there's no plugin layer to maintain.

Where the snippet goes

Ghost has a built-in place for this, so no theme file is involved. Go to Settings → Code Injection in Ghost admin. There are two fields, Site Header and Site Footer. The Evoriqa snippet goes in Site Footer, which Ghost outputs before the closing </body> tag.

That distinction matters more than it looks. Code in either field is injected onto every page of your site, and both are added _after_ the styles and scripts your theme already loads — so the widget initialises once your page is otherwise built, rather than competing with it.

Before you start

You'll need admin access to Ghost and your embed snippet from the Install tab, which arrives with your chatbot id already filled in. If you don't have a workspace yet, create one free at app.evoriqa.com — no credit card needed. The one-line install is the same snippet you'd use on any site; Ghost just gives it a tidier home than most.

What it can answer, and what it hands to you

The agent answers from the content you give it — your about page, your FAQ, your pricing page, your archive. That covers most of what readers ask.

What it does not have is your Ghost member database. It cannot see who is logged in, which tier someone is on, or when their card expires. So an account-specific question — "did my payment go through", "please cancel my subscription" — is not something it should answer from an article, and it doesn't try. It explains where the reader can manage their own account and hands the conversation to you with the full transcript when a person is genuinely needed.

That boundary is worth setting deliberately. A publication's trust is the product, and a confident wrong answer about someone's billing costs more than the email it saved.

Confirming it's live

Save the Code Injection field, then open your site in a private window and look for the chat bubble in the bottom-right. Click it and ask something you know is covered in your archive. Because Ghost injects site-wide, checking one post is enough — you don't need to test each page.

If it doesn't appear, view the page source and search for the script tag. Present means the snippet shipped and the problem is configuration; absent means the field didn't save.

Common questions

Site Header or Site Footer? Site Footer. It outputs before the closing </body> tag, which is where the widget is designed to load.

Does it apply to every post? Yes. Site-level Code Injection runs on every page of the site. Ghost also offers per-post injection from the editor sidebar, but you don't need it here — a single site-level paste covers everything you publish from now on.

Will it slow the site down? The snippet loads asynchronously and the widget is isolated in a shadow DOM, so your theme's CSS and the widget's never touch each other.

Do I need to re-add it when I change themes? No. Code Injection is a site setting, not part of your theme, so it survives a theme swap.

Ghost-specific limits

Newsletters are not covered. Ghost is two products in one: a website and an email newsletter. Code Injection applies to the site. Email clients don't run JavaScript, so the widget cannot appear inside a sent newsletter — if you want readers to reach the agent from an issue, link them to a page on your site.

Headless setups skip it. If you're using Ghost purely as a content API with your own front end, Code Injection doesn't apply, because Ghost isn't rendering your pages. Use the custom-site snippet in your own template instead.