Use Framer’s Project Settings to add the current account-provided snippet to the intended public pages. Placement and execution frequency are separate settings.
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.
Add a named custom script
- 1Confirm your account and site plan expose the required Custom Code controls. Copy the snippet for the correct website in AnswerMetrix.
- 2Open Framer Project Settings → Custom Code. Select Add Script or the + icon and give it a recognizable name.
- 3Use the head placement required by the supplied snippet and select the intended public pages.
- 4Choose Once or Run on every page visit according to the release’s snippet instructions. Do not assume repeated script execution is safe.
- 5Publish and check the live domain, including a CMS detail page and a client-side page transition.
If the supplied setup does not specify an execution setting, ask the team to confirm it for your release. Script loading and page-specific mutation must both work before extending delivery across the site.
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
Remove the named script from Custom Code and republish, then inspect the live pages. Removing the browser script does not establish rollback of a separate native or edge change.
Official platform guidance
Platform documentation reviewed on 3 October 2026. Menu names and access can change; follow the documentation for your installed version.
https://www.framer.com/help/articles/how-to-add-custom-code/
