Skip to main content
Ghost

Install AnswerMetrix on Ghost, Craft or Drupal

Install a supported AnswerMetrix route on Ghost, Craft CMS and Drupal, then verify coverage and an eligible change.

Published 2026-07-01Reviewed 2026-10-03 4 min read

Ghost offers a code-injection setting; Craft and Drupal usually need a maintained template or theme integration. Use the route for your installed CMS version and public website.

Installation scope

These steps use the setup supplied in your current account. A platform’s ability to accept custom code does not establish support for every AnswerMetrix fix. Browser, native and server-side delivery have separate requirements.

Before you begin

  • Use the installation supplied for the correct website in your current AnswerMetrix account. If the route or download is unavailable, ask the team to confirm support before changing the site.
  • Confirm platform version, account role, code access and CSP/consent requirements with the site maintainer.
  • Keep a recovery copy or reviewed source-control change, and identify existing SEO scripts/plugins that manage the same fields.

Ghost

  1. 1Confirm your plan and role allow site-wide Code Injection. Copy the correct website’s snippet from AnswerMetrix.
  2. 2In Ghost settings, open Code Injection and add it once in Site Header. Save and test the live home and post pages.
  3. 3If the setting is unavailable, have the site maintainer confirm the supported theme route before installing.

Craft CMS

  1. 1Find the shared Twig layout used by the public site, often a template extended by the page templates.
  2. 2Add the supplied snippet once within its head, or use the project’s maintained script registration.
  3. 3Review and deploy the change, refresh relevant caches and check an entry page as well as the homepage.

Drupal

  1. 1Have the site maintainer define the external script in a library in the maintained custom theme or module, preserving the supplied URL and attributes.
  2. 2Attach that library to the intended public pages using the project’s supported theme/module approach. Do not edit an upstream theme directly.
  3. 3Deploy, rebuild relevant caches and confirm the library loads on representative public pages.

Craft and Drupal need a version-specific integration review; a generic template name is not a complete installation recipe. The browser embed does not automatically rewrite editorial CMS records. If the supplied release instructions do not cover your version, ask for a supported route.

Check installation before delivering a change

  1. 1Open the published domain and representative public pages. Confirm the intended snippet request or plugin connection succeeds, with the correct site selected.
  2. 2Check for duplicate scripts, blocked requests, stale caches and console errors. For client navigation, check a second page without a full reload.
  3. 3Review one eligible, factually correct proposal and its route requirements. Authorize it only through the current account’s supported controls.
  4. 4Inspect the delivery record and the separate live-page result. For crawler-dependent changes, inspect raw HTML or the supported server-rendered response; a browser DOM change is different evidence.

A loaded script or plugin check-in establishes connection evidence. It does not prove that a fix was delivered, indexed or cited. If the exact expected live signal is unavailable, keep the result unverified and resolve it before expanding the batch.

If the setup does not work

  • Check the published domain and page coverage, rather than only the editor or preview.
  • Check role/plan access, the site identifier and the browser network request. Preserve the observed error for support.
  • Check cache, CSP and consent behavior; ask the maintainer to authorize the required configuration instead of disabling controls globally.
  • Avoid duplicate installs or repeated scans while diagnosing the same connection problem.

Remove or recover the installation

Remove only the Ghost Site Header entry, or revert the maintained Craft/Drupal integration and deploy it. Refresh caches and verify removal on the live pages. Recover any separately published changes through their own route.

Official platform guidance

Platform documentation reviewed on 3 October 2026. Menu names and access can change; follow the documentation for your installed version.

https://docs.ghost.org/themes/structure/

https://craftcms.com/docs/5.x/development/templates.html

https://www.drupal.org/docs/develop/theming-drupal/adding-assets-css-js-to-a-drupal-theme-via-librariesyml

Ready to put this into practice?

Start with a free scan. Review the website findings and available AI response evidence, then choose a useful next step.

No credit card required. Ongoing delivery needs an eligible plan and a supported connection.