This guide shows how to add a Ghost heatmap in about a minute, with no integration: you paste one snippet into Settings → Code injection → Site Header, because it has to load on every page before your clicks happen, and it renders nothing visible. 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.
A click heatmap records where visitors click on each page and draws those clicks as a colour overlay, so the hot spots stand out at a glance. It answers practical questions quickly: do people click the main button, do they try to click things that aren't links, and which parts of a long page get clicked at all? It records clicks only. It doesn't record sessions or keystrokes, and it doesn't show anything to your visitors.
On Ghost, the right spot is Settings → Code injection → Site Header. Because it has to see every click, the heatmap loads once in the head of every page and renders nothing visible. Give it a week or two of normal traffic before drawing conclusions, and look at your most important pages first: the home page, your best-selling product or your main sign-up page.
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.
A heatmap shows what people did, not why. It can't replace talking to customers or a proper A/B test, and on pages with only a handful of visits the patterns are mostly noise.
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 Header, because it has to load on every page before your clicks happen, and it renders nothing visible.
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.
No. It records click positions on the page, not session videos, form input or keystrokes, and it isn't shown to your visitors.