Verifying the Widget Is Live

After you paste the Pinpoint widget into your site and deploy it, you'll want to confirm it actually loaded before inviting anyone to leave feedback. Verifying checks that your project's widget script is present on the page you point it at, so you know reviewers can drop pins the moment they arrive.

Running a Verification Check

From your project's widget setup area, use the verify option to test a page. Pinpoint fetches that page and looks for this project's widget tag.

1.Open your project and go to the widget setup section.

2.Confirm the URL to check. By default this is your project's configured site URL, but you can enter a specific page or a preview deployment link instead.

3.Run the check and wait for the result.

4.A successful check confirms the widget is live and ready to collect feedback on that page.

Only publicly reachable URLs can be verified this way. A page running on localhost or behind a login your visitors can't reach won't be seen by the check — deploy to a staging or production URL first.

If verification reports that the widget isn't present, it usually means the page Pinpoint fetched doesn't include your project's script. Work through these in order:

•The change hasn't deployed yet. If you just merged or published, give the deployment time to go live, then check again.

•The snippet is on a different page. Verify the exact URL where you pasted the code, not just the homepage.

•The snippet belongs to another project. Each project has its own widget tag — make sure you installed the one from this project.

•The URL isn't reachable from outside. Preview deployments protected by a password or IP allowlist can't be fetched — test a publicly accessible version.

After the widget verifies successfully, open the page yourself and drop a test pin. Seeing the pin appear in your feedback board is the final confirmation that everything is wired up end to end.

Verifying from an AI Coding Agent

If you fix and install widgets through an AI coding agent connected over MCP, the agent can run the same verification for you. After the change that adds the widget is merged and deployed, ask it to verify the widget on the deployed URL. The agent reports back whether the script tag was found, so it can confirm the install worked before telling you it's done. As with the manual check, the agent can only reach public URLs — localhost checks require the local pinpoint-mcp server.

Related topics: Widget Setup, Dropping Your First Pin, MCP for AI Agents.