How to install AnswerMetrix on Webflow

For a manual Webflow browser embed, use site-wide Head code. Custom-code access requires an active Site plan or an eligible Workspace, plus the appropriate site role. The separate native Webflow connection has its own setup.

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.

Install through site-wide Head code

1. 1Confirm that you are a Site manager or Designer and have an active Site plan or a Core, Growth, Agency or Freelancer Workspace.
2. 2Copy the snippet for the correct website from AnswerMetrix.
3. 3Open Webflow Site settings → Custom code. Add the snippet once to Head code; do not wrap it in another html, head or body element.
4. 4Save changes, then publish to the domain registered in AnswerMetrix.
5. 5Check a static page and a CMS item on the published domain. Preview alone does not establish that the code is live.

If you use the native Webflow connection offered in AnswerMetrix, follow that account’s authorization and site-selection steps. Do not install the same script again manually. Native/CMS publication and Registered Scripts are distinct from a manual browser embed; confirm support for the exact change.

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 AnswerMetrix snippet from Head code, save and republish. For a native connection or registered script, use its own removal or rollback workflow and check the resulting public page.

Official platform guidance

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

https://help.webflow.com/hc/en-us/articles/33961357265299-Custom-code-in-head-and-body-tags