Install the supplied snippet in the Blade layout or component used by your public website. The file name depends on your application; an authenticated dashboard layout is not the right default.
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.
Find and update the public layout
- 1Copy the correct website’s snippet from AnswerMetrix.
- 2Identify the Blade layout or component that outputs the public head, such as resources/views/layouts/app.blade.php or the application’s layout component.
- 3Add the complete snippet once inside that head. Keep a reviewed source-control change and preserve existing template sections.
- 4Deploy through your normal process and refresh any compiled-view/page caches required by the application.
- 5Inspect a public homepage and an interior page that use the layout. Confirm the script loads and CSP permits the supplied requests.
Only views that use the layout receive the snippet. Livewire, Inertia or another client-navigation layer needs direct-load and page-transition checks. Keep private dashboards and administration pages outside this installation; public sitemaps do not grant access to authenticated pages.
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
Revert the Blade change, deploy it and refresh the relevant caches. Verify removal on the same public pages and separately recover changes made through another delivery route.
Official platform guidance
Platform documentation reviewed on 3 October 2026. Menu names and access can change; follow the documentation for your installed version.
