Wix and Squarespace use different code settings. Follow the sequence for your site and confirm the account allows it before installing a browser embed.
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.
Wix: published site with a connected domain
- 1Confirm the site is published and has its domain connected. Copy the correct website’s snippet from AnswerMetrix.
- 2In the Wix dashboard, open Settings → Custom Code under Development & integrations, then Add Custom Code.
- 3Paste the supplied snippet and give it a recognizable name. Select the intended public pages and Head placement.
- 4Choose the execution setting required by your supplied snippet, apply it and test both a direct page load and navigation to another page.
Wix associates snippets with a domain; assigning a different domain can remove them. Current Wix frontend security can also block third-party code. If loading or page changes fail, ask AnswerMetrix to confirm compatibility instead of installing duplicate copies.
Squarespace: an eligible Code Injection plan
- 1Confirm Code Injection is available: Core, Plus, Advanced or an eligible legacy plan. Basic does not include this route.
- 2Copy the correct website’s snippet from AnswerMetrix and open the site-wide Code Injection panel.
- 3Add the snippet once in Header, then save. Test the live site outside the editor.
- 4Check a normal page and a product or blog page. Checkout pages do not support Code Injection.
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
In Wix, disable or remove the named custom-code entry. In Squarespace, remove only the added Header snippet and save. Retest the public pages; other delivery routes require their own recovery.
Official platform guidance
Platform documentation reviewed on 3 October 2026. Menu names and access can change; follow the documentation for your installed version.
https://support.wix.com/en/article/embedding-custom-code-on-your-site
