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 a public shared layout
- 1Find the Blade layout used by your public website pages, commonly resources/views/layouts/app.blade.php.
- 2Add the correct snippet within the document head.
- 3Review and deploy through your existing source-control process.
- 4Refresh relevant caches and verify a published page.
Only views that inherit that layout receive the snippet. Do not install it on private dashboards or admin pages. A sitemap should list intended public URLs; it does not give AnswerMetrix access to pages behind authentication.
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.
