Connect WordPress through the site-specific AnswerMetrix plugin when it is offered in your account. This route serves supported head changes from WordPress; a browser embed is a separate option.
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 the site-specific plugin
- 1Select the correct WordPress website in AnswerMetrix and open its WordPress connection setup. Download the plugin ZIP offered for that site.
- 2In WordPress admin, open Plugins → Add New → Upload Plugin. Choose the ZIP, select Install Now, then Activate.
- 3Open Settings → AnswerMetrix and select Test connection. The downloaded plugin has its site key preconfigured; check that the site and API URL match the supplied setup.
- 4Return to AnswerMetrix and check the plugin connection and its last-seen time. If it has not checked in, troubleshoot the connection before delivering changes.
If your account does not offer the plugin, ask the team to confirm the supported route for your release. For a manual browser installation, add the account-provided snippet once through a maintained head-code integration. Optional WordPress REST publishing is a separate connection, not a prerequisite for installing the plugin.
Avoid duplicate titles, descriptions and schema from the theme or another SEO plugin. Check public posts, pages and WooCommerce products where applicable; each separately managed site needs its own setup.
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
To stop plugin injection, deactivate the AnswerMetrix Connector and clear page/CDN caches, then inspect a fresh public response. To stop a manual embed, remove that snippet from its original integration. Neither action establishes rollback of a separate native or edge publication.
Official platform guidance
Platform documentation reviewed on 3 October 2026. Menu names and access can change; follow the documentation for your installed version.
