WooCommerce, BigCommerce & Magento Setup

Use the installation route for your storefront engine and store view. Installing a script is separate from verifying accurate product information and supported delivery.

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.

WooCommerce

• Follow the WordPress guide for the site-specific plugin or the supplied browser embed: https://answermetrix.com/resources/guides/installing-on-wordpress
• Check the theme and existing SEO/product plugins before adding schema. Test product, category and variant pages.

BigCommerce storefront

1. 1Confirm the storefront uses Stencil or a supported headless route; legacy Blueprint does not support Script Manager rendering.
2. 2Open the subject storefront’s channel settings and Script Manager. Copy the correct website’s snippet from AnswerMetrix.
3. 3Create a named script using Head placement and storefront scope, retaining the supplied code and an appropriate consent category.
4. 4Save and allow the storefront cache to refresh, then inspect the published channel. A local Stencil CLI preview does not render API-managed scripts.

Magento / Adobe Commerce

1. 1In Admin, open Content → Design → Configuration and edit the intended store view.
2. 2Expand HTML Head and add the supplied snippet in Scripts and Style Sheets, preserving existing entries.
3. 3Save the configuration, refresh relevant caches and test that store view’s public pages. Confirm CSP allows the script; do not weaken the policy globally.

Review canonical URL, currency, price, stock and variant details on representative catalogue pages. Headless storefronts need their actual framework integration. A scan covers discovered pages within its allowance; it is not proof that every SKU was checked.

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

For WooCommerce, follow the WordPress route’s removal steps. In BigCommerce, remove the named storefront script. In Magento, remove only the added entry for that store view and refresh caches. Check the live output and recover separate delivery changes independently.

Official platform guidance

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

https://docs.bigcommerce.com/developer/docs/integrations/scripts

https://experienceleague.adobe.com/en/docs/commerce-admin/content-design/design/page-setup