The widget does not appear

The widget draws nothing until it loads the project configuration. Check these steps in order. Change one thing at a time.

The dashboard detects a successful configuration fetch as installed. Sightings are batched, so allow up to two minutes before selecting Check again.

1. Check the script tag

Find the tag in the deployed page’s source:

<script
  src="https://cdn.gutternote.com/v1/widget.js"
  data-gutternote-key="pk_live_..."
  defer
></script>

The tag is on the page, and a build step did not remove it.
data-gutternote-key is the right project’s key. Without it, the page must call Gutternote.init({ key }).
The tag does not have data-gutternote-enabled="false", and the site is not set to Production under Configure → Site mode. If either is, press Alt+Shift+G on the page or open it with ?gutternote-enabled=remember. See Disabled by default.

2. Check the script loaded

In the Network panel, reload and filter for widget.js.

Blocked: look for a CSP error in the console. See CSP.
404: fix the script URL.
No request: the tag is not on the page.

3. Read the console

Console message	Check
`[gutternote] no project key`	Add `data-gutternote-key`, or pass `key` to `init()`.
`[gutternote] failed to initialise`	Open the failed configuration or sign-in request in the Network panel.

4. Check the configuration request

Filter the Network panel for /v1/config.

Result	Next step
`200`	Look for the Gutternote host element in the page.
`401 unknown_key`	Copy the key from the right project.
`403 origin_not_allowed`	Add the page’s exact origin under Sites that can use the widget. See Access.
CSP error	See CSP.
Wrong API host	Fix `data-gutternote-api` or `apiUrl`.

5. Check the host element

The widget renders in a shadow root inside its host element. If the element is there but unstyled, the CSP may block its inline styles. If the toolbar is off screen, look for transforms or clipping on html and body.

See Widget API for the install options.