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.
Use the site’s custom-code settings
- 1Confirm that your active site plan and role allow custom code.
- 2Open the project’s site settings and the custom-code area.
- 3Add the dashboard-provided snippet to the head of the intended public pages.
- 4Publish and verify the production domain.
Check custom-code availability in the active site plan before setup. Framer’s guide explains the options: https://www.framer.com/dictionary/custom-code.
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.
