Install AnswerMetrix on React, Next.js or Vue

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.

Choose the framework’s supported script entry

• Vite: index.html is normally at the project root, not public/index.html. See https://vite.dev/config/shared-options.
• Next.js: use the supported Script component or document/layout integration for your router version. Avoid adding multiple copies during client navigation.
• Vue and Nuxt: use the framework’s head or script configuration, or the root HTML for a plain client app.

Check discovery and rendering

Provide public sitemap URLs and crawlable links for important routes. A Search Console connection may provide additional context but does not reveal every possible URL. SSR and static output can make essential content available to crawlers that do not run JavaScript.

Test more than the initial page

1. 1Deploy the snippet through the shared public layout.
2. 2Verify a direct request to an important route.
3. 3Navigate to another route without a full reload and inspect its metadata.
4. 4Check that the application’s own head manager does not overwrite or duplicate the intended change.

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.