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-09-15 3 min read

Use this guide to connect public pages you own or manage. You can run a diagnostic and read saved reports before installing anything. Install the embed when you are ready to set up supported delivery for the changes you choose.

Before you begin

  • Use the site key and current snippet from the correct website in your AnswerMetrix dashboard.
  • Confirm access, platform-plan requirements and any Content Security Policy restrictions.
  • Keep a recovery copy of the configuration or a reviewed source-control change.
  • Review existing SEO, consent and analytics integrations to avoid duplicate behaviour.

Choose the maintained integration point

  • Ghost: use the Site Header area in Code Injection where supported by your plan and permissions.
  • Craft CMS: use your public shared Twig layout or the project’s maintained script registration.
  • Drupal: use a supported theme/library integration managed by the project maintainer; avoid editing an upstream theme that an update will replace.

Publish and verify

  1. 1Back up the relevant configuration or use a version-controlled change.
  2. 2Add the dashboard-provided snippet once to the intended public pages.
  3. 3Deploy or publish and clear relevant caches.
  4. 4Verify the live domain and inspect a representative content page.

The embed acts on rendered pages. It does not automatically rewrite editorial CMS entries or make every recommendation deliverable.

Verify installation and delivery separately

After publishing, verify installation in AnswerMetrix and check representative pages on the live domain. Then deliver one eligible change and inspect both its delivery record and its live verification. Expand the batch when that first path works as expected.

Review the proposed change, confirm its facts and check delivery support for your website. After authorising an eligible fix, inspect the delivery record and the separate live-page check. Use your CMS or developer for work the connection cannot deliver.

Work from existing evidence

Start from the findings you already have. Run a fresh scan when the site has changed or the evidence is too old for your decision, and check your plan allowances first. Saved reports remain available without starting another analysis.

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.