Add the account-provided embed to the maintained template that generates your public HTML pages. Editing one generated page may not cover the rest of the site or survive the next build.
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.
Install in the public base template
- 1Select the correct website in AnswerMetrix and copy the complete snippet it supplies.
- 2Identify the source template that outputs the public document head. Keep a version-controlled change or recovery copy.
- 3Paste the snippet once before the closing </head>, preserving its URL, site identifier and attributes.
- 4Use the site’s normal build and deployment process. Check the deployed HTML for the homepage and an interior page.
- 5Load both pages in a browser and inspect whether the script request succeeds. Confirm CSP and consent settings allow the intended behavior.
Sites with separate landing-page templates may need a maintained shared include. Keep private account and administration pages outside the installation. For single-page applications, use the framework guide and test navigation without a full reload.
Check installation before delivering a change
- 1Open the published domain and representative public pages. Confirm the intended snippet request or plugin connection succeeds, with the correct site selected.
- 2Check for duplicate scripts, blocked requests, stale caches and console errors. For client navigation, check a second page without a full reload.
- 3Review one eligible, factually correct proposal and its route requirements. Authorize it only through the current account’s supported controls.
- 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
Revert the template change through the normal deployment process and refresh caches. Confirm the snippet is absent on the deployed pages; removal is separate from rolling back changes through another 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://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/script
